Expose the per-task patch state value so users can determine which tasks
are holding up completion of a patching operation.
Signed-off-by: Josh Poimboeuf
Reviewed-by: Petr Mladek
Reviewed-by: Miroslav Benes
---
Documentation/filesystems/proc.txt | 18 ++
fs/proc/base.c
Hi,
In the block layer, we abuse sysfs to export some per-device debugging
information. I was looking into moving this to debugfs, but I realized
that debugfs doesn't have a mechanism to ensure that a file associated
with a device is safe to use when the device is removed.
At a quick glance, HID
Change livepatch to use a basic per-task consistency model. This is the
foundation which will eventually enable us to patch those ~10% of
security patches which change function or data semantics. This is the
biggest remaining piece needed to make livepatch more generally useful.
This code stems
Small glitch/degraded performance in Crusader is improved with SAS
drives by removing unnecessary spinlocks while clearing scsi command
in drivers internal lookup table.
Signed-off-by: Chaitra P B
Suganath Prabu
---
drivers/scsi/mpt3sas/mpt3sas_base.c |1 +
drivers/scsi/mpt3
On 01/19/2017 12:48 PM, Josef Gajdusek wrote:
> ASUS Zenbooks need several special ACPI calls to enable the ALS peripheral.
> Otherwise, reads just return 0.
>
> Signed-off-by: Josef Gajdusek
> ---
> drivers/iio/light/acpi-als.c | 17 +
> 1 file changed, 17 insertions(+)
>
> dif
Here is the change list:
Posting 4 patches for mpt3sas driver enhancement and defect fixes.
* Handle cable event for notifying degraded speed.
* Performance improvement for Crusader.
* Fix Firmware fault state 0x2100 during heavy 4K RR
FIO stress test.
* Updated driver version to 15.100
Signed-off-by: Chaitra P B
Suganath Prabu
---
drivers/scsi/mpt3sas/mpt3sas_base.h |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/scsi/mpt3sas/mpt3sas_base.h
b/drivers/scsi/mpt3sas/mpt3sas_base.h
index 83cfa16..4ab634f 100644
--- a/drivers/s
Driver processes the event MPI26_EVENT_ACTIVE_CABLE_DEGRADED
when a cable is present and is running at a degraded speed
(below the SAS3 12 Gb/s rate). Prints added
to inform the user that the cable is not running at
optimal speed.
Signed-off-by: Chaitra P B
Suganath Prabu
---
dri
Due existence of loop in the IO path our HBA will receive heavy IOs and
also as driver is not updating the Reply Post Host Index frequently, So
there will be a high chance that our Firmware unable to find any free entry
in the Reply Post Descriptor Queue (i.e. Queue overflow occurs) and can
observe
Hi,
On 19/01/17 14:53, Russell King - ARM Linux wrote:
> On Thu, Jan 19, 2017 at 02:37:56PM +, Juri Lelli wrote:
> > +extern unsigned long
> > +arch_scale_cpu_capacity(struct sched_domain *sd, int cpu);
> > +extern void set_capacity_scale(unsigned int cpu, unsigned long capacity);
>
> These s
The sysfs enabled value is a boolean, so kstrtobool() is a better fit
for parsing the input string since it does the range checking for us.
Suggested-by: Petr Mladek
Signed-off-by: Josh Poimboeuf
Acked-by: Miroslav Benes
Reviewed-by: Petr Mladek
---
kernel/livepatch/core.c | 13 +
For the consistency model we'll need to know the sizes of the old and
new functions to determine if they're on the stacks of any tasks.
Signed-off-by: Josh Poimboeuf
Acked-by: Miroslav Benes
Reviewed-by: Petr Mladek
Reviewed-by: Kamalesh Babulal
---
include/linux/livepatch.h | 3 +++
kernel/
klp_patch_object()'s callers already ensure that the object is loaded,
so its call to klp_is_object_loaded() is unnecessary.
This will also make it possible to move the patching code into a
separate file.
Signed-off-by: Josh Poimboeuf
Acked-by: Miroslav Benes
Reviewed-by: Petr Mladek
Reviewed-
Move functions related to the actual patching of functions and objects
into a new patch.c file.
Signed-off-by: Josh Poimboeuf
Acked-by: Miroslav Benes
Reviewed-by: Petr Mladek
Reviewed-by: Kamalesh Babulal
---
kernel/livepatch/Makefile | 2 +-
kernel/livepatch/core.c | 202 +--
Create temporary stubs for klp_update_patch_state() so we can add
TIF_PATCH_PENDING to different architectures in separate patches without
breaking build bisectability.
Signed-off-by: Josh Poimboeuf
Reviewed-by: Petr Mladek
---
include/linux/livepatch.h | 5 -
kernel/livepatch/core.c | 3
Add the TIF_PATCH_PENDING thread flag to enable the new livepatch
per-task consistency model for x86_64. The bit getting set indicates
the thread has a pending patch which needs to be applied when the thread
exits the kernel.
The bit is placed in the _TIF_ALLWORK_MASK macro, which results in
exit
From: Jiri Slaby
Group the TIF thread flag bits by their inclusion in the _TIF_WORK and
_TIF_TRACE macros.
Signed-off-by: Jiri Slaby
Signed-off-by: Josh Poimboeuf
Reviewed-by: Miroslav Benes
---
arch/s390/include/asm/thread_info.h | 22 ++
1 file changed, 14 insertions(+)
The _TIF_ALLWORK_MASK macro automatically includes the least-significant
16 bits of the thread_info flags, which is less than obvious and tends
to create confusion and surprises when reading or modifying the code.
Define the flags explicitly.
Signed-off-by: Josh Poimboeuf
Reviewed-by: Petr Mlade
On Thu, Jan 19, 2017 at 07:48:41AM -0800, Omar Sandoval wrote:
> Hi,
>
> In the block layer, we abuse sysfs to export some per-device debugging
> information. I was looking into moving this to debugfs, but I realized
> that debugfs doesn't have a mechanism to ensure that a file associated
> with a
Intel 200-series chipsets have the same errata as 100-series, the ACS
capability doesn't follow the PCIe spec, the capability and control
registers are dwords rather than words. Add PCIe root port device IDs
to existing quirk.
Signed-off-by: Alex Williamson
---
drivers/pci/quirks.c | 28 +
On 2017-01-18 13:46, Mark Brown wrote:
> On Wed, Jan 18, 2017 at 10:33:07AM +0100, Jan Kiszka wrote:
>> On 2017-01-18 09:21, Robert Jarzmik wrote:
>
>> +while (1) {
>
> This bit worries me a bit, as this can be either :
> - hogging the SoC's CPU, endlessly running
> - or
On Thu, 19 Jan 2017, Greg Kroah-Hartman wrote:
> > In the block layer, we abuse sysfs to export some per-device debugging
> > information. I was looking into moving this to debugfs, but I realized
> > that debugfs doesn't have a mechanism to ensure that a file associated
> > with a device is safe
On Thu, 2017-01-19 at 21:19 +0530, Chaitra P B wrote:
> diff --git a/drivers/scsi/mpt3sas/mpt3sas_scsih.c
> b/drivers/scsi/mpt3sas/mpt3sas_scsih.c
> index 5ffbfb1..b3f9f7a 100644
> --- a/drivers/scsi/mpt3sas/mpt3sas_scsih.c
> +++ b/drivers/scsi/mpt3sas/mpt3sas_scsih.c
> @@ -1096,6 +1096,27 @@ _scs
Le 19/01/2017 à 08:56, Andrei Pistirica a écrit :
> This patch does the following:
> - MACB/GEM-PTP interface
> - registers and bitfields for TSU
> - capability flags to enable PTP per platform basis
>
> Signed-off-by: Andrei Pistirica
Acked-by: Nicolas Ferre
Thanks, regards,
> ---
> Patch hi
On 19/01/17 14:37, Juri Lelli wrote:
> arm and arm64 share lot of code relative to parsing CPU capacity
> information from DT, using that information for appropriate scaling and
> exposing a sysfs interface for chaging such values at runtime.
>
> Factorize such code in a common place (driver/base/
On Thu, 2017-01-19 at 15:49 +0100, Clemens Gruber wrote:
> On Thu, Jan 19, 2017 at 02:34:39PM +0200, Andy Shevchenko wrote:
> > On Wed, 2017-01-18 at 15:25 +0100, Clemens Gruber wrote:
> > > Yes, that's what this patch tries to solve by verifying that the
> > > external setting (the prescale regist
On Thu, Jan 19, 2017 at 02:40:08PM +, Russell King - ARM Linux wrote:
> On Wed, Jan 11, 2017 at 04:31:57PM -0600, Andy Gross wrote:
> > diff --git a/include/linux/arm-smccc.h b/include/linux/arm-smccc.h
> > index b5abfda..3e28d08 100644
> > --- a/include/linux/arm-smccc.h
> > +++ b/include/linu
On Wed, Jan 18, 2017 at 01:08:14AM +0800, Icenowy Zheng wrote:
>
>
> 17.01.2017, 17:05, "Maxime Ripard" :
> > Hi,
> >
> > On Tue, Jan 17, 2017 at 02:01:14AM +0800, Icenowy Zheng wrote:
> >> V3s has a similar but cut-down CCU to H3.
> >>
> >> Add support for it.
> >>
> >> Signed-off-by: Icenowy
On Thu, Jan 19, 2017 at 05:08:25PM +0100, Luis R. Rodriguez wrote:
> On Thu, Jan 19, 2017 at 12:31:11PM +0100, Greg KH wrote:
> > On Thu, Jan 12, 2017 at 06:42:50AM -0800, Luis R. Rodriguez wrote:
> > > +Invalid users of the custom fallback mechanism can be policed using::
> >
> > Ick, no, why? W
On Thu, Jan 19, 2017 at 05:36:36PM +0300, Aleksey Makarov wrote:
> It is the time we have the real 16-bit Stream ID user, which is the
> ThunderX. Its IO topology uses 1:1 map for Requester ID to Stream ID
> translation for each root complex which allows to get full 16-bit
> Stream ID. Firmware as
On Thu, 2017-01-19 at 14:23 +0100, Greg KH wrote:
> On Fri, Jan 13, 2017 at 09:07:57PM +0100, Manuel Schölling wrote:
> > Add a scrollback buffers for each VGA console. The benefit is that
> > the scrollback history is not flushed when switching between
> > consoles
> > but is persistent.
> > The b
On Thu, Jan 19, 2017 at 11:51:14PM +0900, Jinbum Park wrote:
> This patch adds arch-independent testcases for RODATA.
> Both x86 and x86_64 already have testcases for RODATA,
> But they are arch-specific because using inline assembly directly.
>
> and cacheflush.h is not suitable location for roda
From: Kefeng Wang
Date: Thu, 19 Jan 2017 16:26:21 +0800
> Just like commit 4acd4945cd1e ("ipv6: addrconf: Avoid calling
> netdevice notifiers with RCU read-side lock"), it is unnecessary
> to make addrconf_disable_change() use RCU iteration over the
> netdev list, since it already holds the RTNL
January 19 2017 4:49 PM, "Marek Vasut" wrote:
> On 01/19/2017 12:48 PM, Josef Gajdusek wrote:
>
>> ASUS Zenbooks need several special ACPI calls to enable the ALS peripheral.
>> Otherwise, reads just return 0.
>>
>> Signed-off-by: Josef Gajdusek
>> ---
>> drivers/iio/light/acpi-als.c | 17 +
On Thu, Jan 19, 2017 at 02:48:38PM +0100, Greg KH wrote:
From: Greg Kroah-Hartman
Might as well just mark it as such now, to head off the constant
questions. Yes, 4.9 is the next longterm supported kernel version.
Signed-off-by: Greg Kroah-Hartman
diff --git a/content/releases.rst b/content
On Wed, Jan 18, 2017 at 06:48:35PM +0100, Ondřej Jirman wrote:
> Dne 18.1.2017 v 17:56 Maxime Ripard napsal(a):
> >>> What's your current plan to fix that? I guess the easiest (and most
> >>> likely to be reusable) would be to allow for clock tables, instead of
> >>> using the generic approach. We
On Wed, Jan 18, 2017 at 01:02:03AM +0800, Icenowy Zheng wrote:
>
> 2017年1月17日 17:04于 Maxime Ripard 写道：
> >
> > Hi,
> >
> > On Tue, Jan 17, 2017 at 02:01:14AM +0800, Icenowy Zheng wrote:
> > > V3s has a similar but cut-down CCU to H3.
> > >
> > > Add support for it.
> > >
> > > Signed-off-by:
On Mon, Jan 16, 2017 at 08:16:07AM +0100, Tomasz Nowicki wrote:
> The goal of erratum #27704 workaround was to make sure that ASIDs and VMIDs
> are unique across all SMMU instances on affected Cavium systems.
>
> Currently, the workaround code partitions ASIDs and VMIDs by increasing
> global cavi
On Thu, Jan 19, 2017 at 12:38:57PM +0100, Greg KH wrote:
> On Thu, Jan 12, 2017 at 07:02:44AM -0800, Luis R. Rodriguez wrote:
> > The Coccinelle sysdata patches were used to help with
> > this transition. The changes have been carefully manually
> > vetted for. With the conversion we modify the cas
On 2017-01-19 07:36, Lorenzo Pieralisi wrote:
On Wed, Jan 18, 2017 at 09:45:56PM +0200, Andy Shevchenko wrote:
[...]
> +/**
> + * acpi_irq_get - Look for the ACPI IRQ resource with the given index and
> + *use it to initialize the given Linux IRQ resource.
> + * @handle ACPI de
On Thu, Jan 19, 2017 at 01:03:21PM +0100, Greg KH wrote:
> On Tue, Jan 17, 2017 at 04:29:19PM +0100, Greg KH wrote:
> > On Tue, Jan 17, 2017 at 10:19:11AM -0500, J. Bruce Fields wrote:
> > > On Tue, Jan 17, 2017 at 08:13:47AM +0100, Greg KH wrote:
> > > > On Mon, Jan 16, 2017 at 04:25:55PM -0500, J
On Mon, Jan 16, 2017 at 04:54:31PM -0600, Rob Herring wrote:
> This is needed to work with the client operations which uses const ptrs.
>
> Really, the flags pointer could be const, too, but this would be a tree
> wide fix.
>
> Signed-off-by: Rob Herring
> Reviewed-by: Andy Shevchenko
> Reviewe
On Thu, Jan 19, 2017 at 03:53:15PM +0100, Andrew Lunn wrote:
> > > > struct dsa_platform_data {
> > > > /*
> > > > * Reference to a Linux network interface that connects
> > > > * to the root switch chip of the tree.
> > > > */
> > > > struct device *net
Running my likely/unlikely profiler for 3 weeks on two production
machines, I discovered that the unlikely() test in
__rt_mutex_slowlock() checking if state is TASK_INTERRUPTIBLE is hit
100% of the time, making it a very likely case.
The reason is, on a vanilla kernel, the majority case of calling
From: Arnd Bergmann
Date: Thu, 19 Jan 2017 10:45:31 +0100
> The new ARP support has pushed the stack size over the edge on ARM,
> as there are two large objects on the stack in this function (mask
> and tb) and both have now grown a bit more:
>
> net/sched/cls_flower.c: In function 'fl_change':
On Thu, Jan 19, 2017 at 10:16:58AM -0600, Andy Gross wrote:
> On Thu, Jan 19, 2017 at 03:48:18PM +, Russell King - ARM Linux wrote:
> > Please add that detail to the kerneldoc comments for the structure
> > concerning state.a6. It's important that such information is not
> > lost in the depths
On Thu, Jan 19, 2017 at 11:21:05AM -0500, Konstantin Ryabitsev wrote:
> On Thu, Jan 19, 2017 at 02:48:38PM +0100, Greg KH wrote:
> > From: Greg Kroah-Hartman
> >
> > Might as well just mark it as such now, to head off the constant
> > questions. Yes, 4.9 is the next longterm supported kernel ver
From: Vineeth Remanan Pillai
During an OOM scenario, request slots could not be created as skb
allocation fails. So the netback cannot pass in packets and netfront
wrongly assumes that there is no more work to be done and it disables
polling. This causes Rx to stall.
The issue is with the retry
From: Augusto Mecking Caringi
Date: Thu, 19 Jan 2017 11:00:12 +
> When CONFIG_ATM_CLIP is set and CONFIG_PROC_FS is not set, the building
> was failing whith the error:
>
> net/atm/clip.c: In function ‘atm_clip_exit’:
> net/atm/clip.c:933:27: error: ‘atm_proc_root’ undeclared (first use in
>
Hello, everyone:
This is a small patchset intended to add PCI-subsystem bits necessary
for enabling PCI support on i.MX7. This patchset is not
self-sufficient and depends on three other patchsets:
- Changes to anatop regulator driver
- Chagnes to i.MX device tree code pertaining to anatop reg
Some designs implement reset GPIO via a GPIO expander connected to a
peripheral bus. One such example would be i.MX7 Sabre board where said
GPIO is provided by SPI shift register connected to a bitbanged SPI
bus. In order to support such designs allow reset GPIO request to defer
probing of the driv
Cc: yurov...@gmail.com
Cc: Richard Zhu
Cc: Lucas Stach
Cc: Bjorn Helgaas
Cc: Fabio Estevam
Cc: Shawn Guo
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Andrey Smirnov
---
drivers/pci/host/pci-imx6.c | 3 +--
1 file changed, 1 insertion(+), 2 deletion
On Thu, Jan 19, 2017 at 05:30:13PM +0100, Greg KH wrote:
> On Thu, Jan 19, 2017 at 03:53:15PM +0100, Andrew Lunn wrote:
> > > > > struct dsa_platform_data {
> > > > > /*
> > > > > * Reference to a Linux network interface that connects
> > > > > * to the root switch chip of
Add various bits of code needed to support i.MX7D variant of the IP.
Cc: yurov...@gmail.com
Cc: Richard Zhu
Cc: Lucas Stach
Cc: Bjorn Helgaas
Cc: Fabio Estevam
Cc: Shawn Guo
Cc: Rob Herring
Cc: Mark Rutland
Cc: Lee Jones
Cc: linux-arm-ker...@lists.infradead.org
Cc: devicet...@vger.kernel.o
On Thu, Jan 19, 2017 at 03:48:18PM +, Russell King - ARM Linux wrote:
> On Thu, Jan 19, 2017 at 09:45:06AM -0600, Andy Gross wrote:
> > On Thu, Jan 19, 2017 at 02:40:08PM +, Russell King - ARM Linux wrote:
> > > On Wed, Jan 11, 2017 at 04:31:57PM -0600, Andy Gross wrote:
> > > > diff --git
Convert driver to use managed resources.
This eliminates error path boilerplate and makes code neat.
Signed-off-by: Andy Shevchenko
---
drivers/platform/x86/intel_mid_powerbtn.c | 29 +
1 file changed, 9 insertions(+), 20 deletions(-)
diff --git a/drivers/platform/x8
On Mon, 16 Jan 2017, bugzilla-dae...@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=189291
>
> Zhang Rui changed:
>
>What|Removed |Added
>
>Assig
The snail address is subject to change. This already happened once.
Remove the address completely from the file to avoid potential noise
when update.
While here, adjust copyright years and list authors.
Signed-off-by: Andy Shevchenko
---
drivers/platform/x86/intel_mid_powerbtn.c | 9 -
Sort header inclusion block in alphabetical order.
Signed-off-by: Andy Shevchenko
---
drivers/platform/x86/intel_mid_powerbtn.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/platform/x86/intel_mid_powerbtn.c
b/drivers/platform/x86/intel_mid_powerbtn.c
index
This is preparatory patch to extend the driver in order to support other
Intel MID platform.
Here the new driver data structure is introduced with split of
->pbstat() callback.
Signed-off-by: Andy Shevchenko
---
drivers/platform/x86/intel_mid_powerbtn.c | 62 ---
1 f
On Thu, Jan 19, 2017 at 12:39 AM, Stephen Rothwell
wrote:
> Hi all,
>
> Changes since 20170118:
>
> The audit tree gained a conflict against Linus' tree.
>
> The tip tree gained a conflict against the security tree.
>
> The rcu tree gained a semantic conflict against the net-next tree for
> which
If process forks some children when it has is_child_subreaper
flag enabled they will inherit has_child_subreaper flag - first
group, when is_child_subreaper is disabled forked children will
not inherit it - second group. So child-subreaper does not reparent
all his descendants when their parents di
On Thu, Jan 19, 2017 at 05:12:15PM +0100, Manuel Schölling wrote:
> On Thu, 2017-01-19 at 14:23 +0100, Greg KH wrote:
> > On Fri, Jan 13, 2017 at 09:07:57PM +0100, Manuel Schölling wrote:
> > > Add a scrollback buffers for each VGA console. The benefit is that
> > > the scrollback history is not fl
On Thu, Jan 19, 2017 at 12:31:11PM +0100, Greg KH wrote:
> On Thu, Jan 12, 2017 at 06:42:50AM -0800, Luis R. Rodriguez wrote:
> > +Invalid users of the custom fallback mechanism can be policed using::
>
> Ick, no, why? Why not just add a checkpatch rule instead?
If its easy to do, how would we d
The reason why p exists in perf_header__adds_write(), even though it is
initialized to point the same address as feat_sec points, is that p is
increamented in do_write_feat() while feat_sec is not.
Note:(*p)++ in do_write_feat() is equivalent to p++ in
perf_header__adds_write().
However for this
Hi Hans and Jose,
On Thursday 19 Jan 2017 16:30:57 Hans Verkuil wrote:
> On 01/19/17 16:21, Jose Abreu wrote:
> > On 18-01-2017 20:49, Laurent Pinchart wrote:
> >> Ideally the bridge mode set operation should be extended to take format
> >> and colorspace information (or another bridge operation s
Hi Peter,
These here two patches deal with rescheduling on active contexts. The common
idea is that we shouldn't reschedule groups of higher priority than the ones
that are being added or scheduled in. 1/1 takes on the scheduling path, where
we don't want to touch cpu flexible groups if the schedu
Am Donnerstag, den 19.01.2017, 08:36 -0800 schrieb Andrey Smirnov:
> Some designs implement reset GPIO via a GPIO expander connected to a
> peripheral bus. One such example would be i.MX7 Sabre board where said
> GPIO is provided by SPI shift register connected to a bitbanged SPI
> bus. In order to
On 01/19/2017 05:19 PM, a...@atx.name wrote:
> January 19 2017 4:49 PM, "Marek Vasut" wrote:
>> On 01/19/2017 12:48 PM, Josef Gajdusek wrote:
>>
>>> ASUS Zenbooks need several special ACPI calls to enable the ALS peripheral.
>>> Otherwise, reads just return 0.
>>>
>>> Signed-off-by: Josef Gajdusek
Hi Arnd,
This is the old v13 patch set you're commenting, but it doesn't matter
it's essentially identical to v14 in this patch.
On Wed, Jan 18, 2017 at 09:19:25PM +0100, Arnd Bergmann wrote:
> On Friday, November 18, 2016 3:51:37 PM CET Jens Wiklander wrote:
> > Initial patch for generic TEE sub
Replace all occurrences of mfld by mid to emphasize that driver is used
for Intel MID platforms.
Signed-off-by: Andy Shevchenko
---
drivers/platform/x86/intel_mid_powerbtn.c | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/drivers/platform/x86/intel_mi
Enable this driver to handle events from Basin Cove PMIC, which is
installed on Intel Merrifield platform.
Signed-off-by: Andy Shevchenko
---
drivers/platform/x86/intel_mid_powerbtn.c | 56 +++
1 file changed, 56 insertions(+)
diff --git a/drivers/platform/x86/intel_
On Wed, Jan 18, 2017 at 06:05:46PM +, Mark Rutland wrote:
> On Wed, Jan 18, 2017 at 04:17:18PM +, Punit Agrawal wrote:
> > Mark Rutland writes:
> >
> > > On Wed, Jan 18, 2017 at 02:51:31PM +, Punit Agrawal wrote:
> > >> I should've clarified in my reply that I wasn't looking to suppor
Hello,
I've noticed an inconsistency between how physical ethernet and veth handles
mtu.
If I setup two physical interfaces (directly connected) with different mtu:s,
only the size of the outgoing packets are limited by the mtu. But with veth a
packet is dropped if the mtu of the receiving int
From: Arnd Bergmann
Date: Thu, 19 Jan 2017 10:33:29 +0100
> A cleanup removed the only user of this variable
>
> mlx5/core/en_ethtool.c: In function 'mlx5e_set_channels':
> mlx5/core/en_ethtool.c:546:6: error: unused variable 'ncv'
> [-Werror=unused-variable]
>
> Let's remove the declaration a
The series contains 3 groups of patches
- fix of the driver regarding interrupt flags
- several clean ups
- enhancement to enable on Intel Merrifield (Intel Edison board)
The driver has been tested on Intel Medfield tablet and Intel Edison board.
Andy Shevchenko (10):
platform/x86: intel_mid_po
On Tue, Jan 17, 2017 at 07:34:34PM +, Mark Brown wrote:
> On Wed, Jan 11, 2017 at 04:03:13PM +0100, Nicholas Mc Guire wrote:
> > As the overall delay is in range of seconds and the wait granularity
> > is 10ms msleep() seems more reasonable than to put load on the highres
> > timer subsystem.
>
Move Intel Medfield specific code to another callback, which will be
used later.
Signed-off-by: Andy Shevchenko
---
drivers/platform/x86/intel_mid_powerbtn.c | 29 ++---
1 file changed, 18 insertions(+), 11 deletions(-)
diff --git a/drivers/platform/x86/intel_mid_powerbt
On Wed, Jan 18, 2017 at 03:28:57PM -0500, Cathy Avery wrote:
> The patch provides a means to offer a lightweight option to the
> current FC transport class. The new option is selected by a
> driver when it indicates it wants the lightweight
> transport via fc_function_template.
This need some real
On 01/19/17 16:21, Jose Abreu wrote:
Hi Laurent,
On 18-01-2017 20:49, Laurent Pinchart wrote:
Ideally the bridge mode set operation should be extended to take format and
colorspace information (or another bridge operation should be created for that
purpose, I'm still undecided). As that's qui
On Thu, Jan 19, 2017 at 06:10:08PM +0200, Andy Shevchenko wrote:
> Combining with your proposal I would see the best approach is to set
> pca->period_ns accordingly to current prescaler value if you want to.
Yes, I agree.
> In your patch I see no benefit, since it's quite unlikely user will want
On Thu, 19 Jan 2017 17:42:52 +0100
Peter Zijlstra wrote:
> On Thu, Jan 19, 2017 at 08:54:41AM -0500, Steven Rostedt (VMware) wrote:
> > I added a comment stating that the branch should be unlikely, but due
> > to the intel drm logic, it currently isn't. Then if drm changes in the
> > future, we c
On Thu, Jan 19, 2017 at 04:49:35PM +, KY Srinivasan wrote:
>
>
> > -Original Message-
> > From: Greg KH [mailto:gre...@linuxfoundation.org]
> > Sent: Thursday, January 19, 2017 4:59 AM
> > To: KY Srinivasan
> > Cc: linux-kernel@vger.kernel.org; de...@linuxdriverproject.org;
> > o...@
(This is mainly for Greg's benefit to help him understand the issue.)
I think the diagram you gave initially made this confusing, as it
talks about a CPU(sic) producing the "RGMII" and "MII-MGMT".
Let's instead show a better representation that hopefully helps Greg
understand networking. :)
C
From: Markus Elfring
Date: Thu, 19 Jan 2017 17:41:23 +0100
Some update suggestions were taken into account
from static source code analysis.
Markus Elfring (8):
Return directly after a failed parameter validation in dev_nvram_write()
Return directly after a failed kmalloc() in dev_nvram_writ
>
> [jolsa@krava perf]$ git branch -r | grep xed-
> ak/perf/xed-3
> ak/perf/xed-4
Pushed.
-Andi
When new events are added to an active context, we go and reschedule
all cpu groups and all task groups in order to preserve the priority
(cpu pinned, task pinned, cpu flexible, task flexible), but in
reality we only need to reschedule groups of the same priority as
that of the events being added,
In the sched-in path, we first remove cpu's flexible events in order to
give priority to task's pinned events. However, this step can be safely
skipped if the task doesn't have its own pinned events.
This patch implements this skipping.
Signed-off-by: Alexander Shishkin
Reported-by: Adrian Hunte
On Thu, Jan 19, 2017 at 12:36:52PM +0100, Greg KH wrote:
> On Thu, Jan 12, 2017 at 07:02:42AM -0800, Luis R. Rodriguez wrote:
>
> I think this changelog novel is longer than the documentation you added
> to the kernel :(
Heh, OK will work on that.
> > --- /dev/null
> > +++ b/Documentation/driver
On 19 January 2017 at 12:02, Ard Biesheuvel wrote:
> The modversion symbol CRCs are emitted as ELF symbols, which allows us to
> easily populate the kcrctab sections by relying on the linker to associate
> each kcrctab slot with the correct value.
>
> This has a couple of downsides:
> - On archite
From: Markus Elfring
Date: Thu, 19 Jan 2017 15:44:03 +0100
Return directly after a call of the function "kmalloc" failed here.
Signed-off-by: Markus Elfring
---
arch/powerpc/kernel/nvram_64.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/arch/powerpc/kernel/nvram_64.c
On Wed, 18 Jan 2017, Andy Shevchenko wrote:
> +#include
> +
> +#include
> +#include
> +#include
> +#include
> +#include
> +
> +static int __init mrfld_legacy_rtc_alloc_irq(void)
> +{
> + struct irq_alloc_info info;
> + int ret;
> +
> + if (!x86_platform.legacy.rtc)
> +
On Tue, Jan 17, 2017 at 07:33:02PM +, Mark Brown wrote:
> On Wed, Jan 11, 2017 at 04:03:51PM +0100, Nicholas Mc Guire wrote:
> > The delay here does not seem to be critical with respect to longer
> > delays than 10ms as this delay is to ensure that the write took
> > effect before the next soc_
From: Markus Elfring
Date: Thu, 19 Jan 2017 16:12:48 +0100
* Return directly after an inappropriate input parameter was detected.
* Delete an initialisation for the variable "tmp" at the beginning
which became unnecessary with this refactoring.
Signed-off-by: Markus Elfring
---
arch/powerpc
From: Markus Elfring
Date: Thu, 19 Jan 2017 15:22:56 +0100
* Return directly after an inappropriate input parameter was detected.
* Delete an initialisation for the variable "tmp" at the beginning
and an assignment for the variable "ret" which became unnecessary
with this refactoring.
Signe
* Peter Zijlstra wrote:
> On Thu, Jan 19, 2017 at 11:19:24AM +0100, Peter Zijlstra wrote:
>
> > I'll go have a prod. Thanks!
>
> This seems to cure it for me.
>
> ---
> Subject: sched/clock: Fix hotplug issue
JFYI:
arch/x86/kernel/cpu/centaur.c: In function ‘early_init_centaur’:
arch/x86/
On Thu, Jan 19, 2017 at 6:52 PM, Clemens Gruber
wrote:
> On Thu, Jan 19, 2017 at 06:10:08PM +0200, Andy Shevchenko wrote:
>> So, summarize, I prefer (in order of preference from high to low):
>> - enforce default prescaler value based on default period (it's just one
>> line to write a register)
From: Markus Elfring
Date: Thu, 19 Jan 2017 16:56:46 +0100
The script "checkpatch.pl" pointed information out like the following.
WARNING: Possible unnecessary 'out of memory' message
Thus fix affected source code places.
Signed-off-by: Markus Elfring
---
arch/powerpc/kernel/nvram_64.c | 12
From: Ard Biesheuvel
> Sent: 18 January 2017 13:53
..
> It turns out that this odd treatment of absolute symbols (i.e.,
> symbols having section number SHN_ABS) is a known issue in GNU ld
>
> https://sourceware.org/ml/binutils/2012-05/msg00019.html
...
Jeepers - that is truly f*cked.
I've even
On 19 January 2017 at 16:55, Ard Biesheuvel wrote:
> On 19 January 2017 at 12:02, Ard Biesheuvel wrote:
>> The modversion symbol CRCs are emitted as ELF symbols, which allows us to
>> easily populate the kcrctab sections by relying on the linker to associate
>> each kcrctab slot with the correct
401 - 500 of 929 matches
Mail list logo
