Hi Greg,
On Wed, 28 Sep 2016 08:25:01 +0200 Greg KH wrote:
>
> Looks good to me, one of these days we will get lustre out of staging to
> make this easier...
I look forward to it :-)
--
Cheers,
Stephen Rothwell
On Tue, 27 Sep 2016 12:13:18 -0700
Colin King wrote:
> From: Colin Ian King
>
> Trival fix, dev_err messages are missing a \n, so add it.
>
> Signed-off-by: Colin Ian King
> ---
> drivers/s390/block/dasd_erp.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Applied, thanks.
--
On Tue, 27 Sep 2016 12:57:01 -0700
Colin King wrote:
> From: Colin Ian King
>
> There is a trailing white space at the end of a dev_err
> message that does nothing useful - remove it.
>
> Signed-off-by: Colin Ian King
Applied, thanks.
--
blue skies,
Martin.
"Reality continues to ruin m
Le 27/09/2016 à 18:16, Joe Perches a écrit :
> Use the more common logging mechanism.
>
> Miscellanea:
>
> o Realign multiline statements
> o Coalesce format
>
> Signed-off-by: Joe Perches
> ---
> drivers/usb/gadget/function/rndis.c | 9 -
> drivers/usb/gadget/function/u_serial.c
Hello Rui, Javi, Lukasz and Eduardo
> -Original Message-
> From: Zhang Rui [mailto:rui.zh...@intel.com]
> Sent: Wednesday, September 28, 2016 10:31 AM
> To: Eduardo Valentin; Lukasz Luba
> Cc: Inhyuk Kang; linux...@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] of: th
On 27.09.2016 14:04, Ralf Baechle wrote:
On Mon, Aug 29, 2016 at 11:30:07AM +0200, Marcin Nowakowski wrote:
Depending on the kernel configuration, up to 3 syscall tables can be
used in parallel - so set the number properly to ensure syscall tracing
is set up properly.
Signed-off-by: Marcin Now
On Tue, Sep 27, 2016 at 05:22:13PM -0700, Vineet Gupta wrote:
> > Yeah, Sparc64 might be a better example, it more closely matches your
> > hardware. See
> > arch/sparc/include/asm/irqflags_64.h:arch_local_irq_save().
>
> So I finally got around to doing this and as expected has turned out to be
Yes true, patch from Ville
https://lists.freedesktop.org/archives/dri-devel/2016-September/118631.html";
already fix patches sent by Baoyou.
Vincent
On 09/27/2016 09:07 PM, Benjamin Gaignard wrote:
> I think that create conflicts with what is already in Vincent pull
> request where we have fix th
This makes the code ugly.
regards,
dan carpenter
- Original Message -
> From: "Herbert Xu"
> To: "Marcelo Cerri"
> Cc: "Jan Stancek" , "rui y wang" ,
> mhce...@linux.vnet.ibm.com,
> leosi...@linux.vnet.ibm.com, pfsmor...@linux.vnet.ibm.com,
> linux-cry...@vger.kernel.org,
> linuxppc-...@lists.ozlabs.org, linux-kernel@vger.kernel.o
On Tue, Sep 27, 2016 at 02:52:49PM -0300, Martin Alonso wrote:
> Change the type and uses of rx_rate.
>
> Signed-off-by: Martin Alonso
> ---
> drivers/staging/vt6656/dpc.c | 9 +
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/staging/vt6656/dpc.c b/drivers/st
On Wed, 2016-09-28 at 11:28 +0800, Chen Yu wrote:
> So first try is to use pm_request_resume() instead, to make the
> runtime
> resume process asynchronously. Unfortunately the asynchronous runtime
> resume relies on pm_wq, which is freezed at early stage. So we choose
> another method, that is to
Use the descriptor-based interface to manipulate GPIOs, instead of
the legacy integer-based interface.
In the meanwhile, remove unneeded vbus_pin_active_low[...] member.
Signed-off-by: Wenyou Yang
---
drivers/usb/host/ohci-at91.c | 120 ++-
1 file change
Use the descriptor-based interface to manipulate GPIOs, instead of
the legacy integer-based interface.
In the meanwhile, remove unneeded vbus_pin_active_low[...] member.
Signed-off-by: Wenyou Yang
---
drivers/usb/host/ohci-at91.c | 120 ++-
1 file change
Use the descriptor-based interface to manipulate GPIOs, instead of
the legacy integer-based interface.
In the meanwhile, remove unneeded vbus_pin_active_low[...] member.
Signed-off-by: Wenyou Yang
---
drivers/usb/host/ohci-at91.c | 120 ++-
1 file change
From: "R. Parameswaran"
Date: Tue, 27 Sep 2016 12:17:21 -0700 (PDT)
> Later, in vxlan_dev_configure(), called from vxlan_dev_create(), it gets
> adjusted to account for the headers:
>
> vxlan_dev_configure():
> ...
> if (!conf->mtu)
> dev->mtu = lowerdev->mtu - (use_ipv
This patchset contains the following commits:
Bastian Hecht (1):
drivers: dma-coherent: Move spinlock in dma_alloc_from_coherent()
George G. Davis (1):
drivers: dma-coherent: Fix DMA coherent size for less than page
drivers/base/dma-coherent.c |8 +---
1 file changed, 5 insertions(+
From: "George G. Davis"
We fix a bug in dma_mmap_from_coherent() that appears when we map non page
aligned DMA memory. It cuts off the non aligned part (this is different to
dma_alloc_coherent() that always rounds up to full pages). So for mappings
of less than a page we get -ENXIO as dma_mmap_fr
From: Bastian Hecht
We don't need to hold the spinlock while zeroing the allocated memory.
In case we handle big buffers this is a severe issue as other CPUs might
be spinning half a second or longer.
Signed-off-by: Bastian Hecht
Signed-off-by: George G. Davis
Signed-off-by: Mark Craske
---
Hi,
On 12/09/16 14:38, Roger Quadros wrote:
> Hi Santosh & Russell,
>
> On 19/08/16 19:38, Santosh Shilimkar wrote:
>>
>> On 8/19/2016 12:30 AM, Roger Quadros wrote:
>>> Hi Santosh,
>>>
>>
> So I'm 99.9% convinced that the proposed change is correct.
>
I will got with that then :-) a
On 2016/9/28 13:52, Joonsoo Kim wrote:
> On Mon, Sep 26, 2016 at 01:02:31PM +0200, Michal Hocko wrote:
>> On Mon 26-09-16 18:17:50, Xishi Qiu wrote:
>>> On 2016/9/26 17:43, Michal Hocko wrote:
>>>
On Mon 26-09-16 17:16:54, Xishi Qiu wrote:
> On 2016/9/26 16:58, Michal Hocko wrote:
>
>
On 09/27/2016 03:34 PM, Wolfgang Wiedmeyer wrote:
>
> Krzysztof Kozlowski writes:
>
>> On Tue, Sep 27, 2016 at 01:31:10AM +0200, Wolfgang Wiedmeyer wrote:
>>> This patch adds a listener for extcon cable events and enables
>>> charging if an USB cable is connected. It recognizes SDP and DCP cable
Hi Oliver,
On Wed, Sep 28, 2016 at 09:42:54AM +0200, Oliver Neukum wrote:
> On Wed, 2016-09-28 at 11:28 +0800, Chen Yu wrote:
> > So first try is to use pm_request_resume() instead, to make the
> > runtime
> > resume process asynchronously. Unfortunately the asynchronous runtime
> > resume relies o
On 09/27/2016 07:51 PM, Wolfgang Wiedmeyer wrote:
>
> Mark Brown writes:
>
>> On Tue, Sep 27, 2016 at 03:50:42PM +0200, Wolfgang Wiedmeyer wrote:
>>
>>> When charging is disabled (e.g. by removing the USB cable) the charge
>>> current is not reset to zero. So if I expose the current by the
>>> CU
Also do not override any other configuration in this register.
Signed-off-by: Benjamin Tissoires
---
no changes in v3
new in v2
---
drivers/i2c/busses/i2c-i801.c | 11 ---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/drivers/i2c/busses/i2c-i801.c b/drivers/i2c/busses/
Hi,
this is mostly a resend of the series.
The only change is in patch 9/10, where I removed the dev_warn that could
be an issue on some laggish operations on Synaptics RMI4 devices (when
retrieving the heatmap). It also appeared that these warning were sent quite
regularly with the Elantech touc
There is a chance we get called while Host Notify is not available (yet),
so we need to clear the Host Notify bit in those rare case.
Signed-off-by: Benjamin Tissoires
---
changes in v3:
- renamed from "i2c: i801: warn on i2c_handle_smbus_host_notify() errors"
- removed the warnings and just ke
schedule_work() returns a boolean (true on success, false if the work
was already queued).
This doesn't match the "negative number on error" return model that the
function exports.
Given that schedule_work() will always return true (we have an internal
.pending check protected by a spinlock), just
i801 mixes hexadecimal and decimal values for defining bits. However,
we have a nice BIT() macro for this exact purpose.
No functional changes, cleanup only.
Reviewed-by: Jean Delvare
Signed-off-by: Benjamin Tissoires
---
no changes in v3
no changes in v2
---
drivers/i2c/busses/i2c-i801.c |
struct host_notify contains its own workqueue, so there is a race when
the adapter gets removed:
- the adapter schedules a notification
- the notification is on hold
- the adapter gets removed and all its children too
- the worker fires and access illegal memory
Add an API to actually kill the wor
On the platform tested, reading SMBNTFDDAT always returns 0 (using 1 read
of a word or 2 of 2 bytes). Given that we are not sure why and that we
don't need to rely on the data parameter in the current users of Host
Notify, remove this part of the code.
If someone wants to re-enable it, just revert
we can skip one test when calling i801_enable_host_notify(). Given
that we call it all the time, it's better to consider the fact that
the adapter doesn't support Host Notify as not an error.
Reviewed-by: Jean Delvare
Signed-off-by: Benjamin Tissoires
---
no changes in v3
no changes in v2
---
No functional changes, just typos and remove unused #define.
Reviewed-by: Jean Delvare
Signed-off-by: Benjamin Tissoires
---
no changes in v3
no changes in v2
---
drivers/i2c/busses/i2c-i801.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/i2c/busses/i2c-i8
no functional changes
Signed-off-by: Benjamin Tissoires
---
no changes in v3
new in v2
---
drivers/i2c/busses/i2c-i801.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/i2c/busses/i2c-i801.c b/drivers/i2c/busses/i2c-i801.c
index 05ce265..55fa6e1 10
i2c_handle_smbus_host_notify() returns an error code when it fails.
If the caller wants to warn when an error is returned, we should not
partially warn in the function itself.
Signed-off-by: Benjamin Tissoires
---
no changes in v3
new in v2
---
drivers/i2c/i2c-smbus.c | 1 -
1 file changed, 1
On Wed, 2016-09-28 at 16:09 +0800, Chen Yu wrote:
> Thanks for your reply. Do you mean we should add the logic to pm core?
> There is already one if the driver's
> .prepare() returns a positive number(aka, RPM_SUSPENDED), then pm core will
> keep
Yes, that makes sense.
Sorry
On 28/09/2016 01:07, Michael S. Tsirkin wrote:
> On Tue, Sep 27, 2016 at 11:20:12PM +0200, Paolo Bonzini wrote:
>> Since bf9f6ac8d749 ("KVM: Update Posted-Interrupts Descriptor when vCPU
>> is blocked", 2015-09-18) the posted interrupt descriptor is checked
>> unconditionally for PIR.ON. Therefo
On 23/09/16 03:12, Shawn Lin wrote:
> Per the vendor's requirement, we shouldn't do any setting for
> 1.8V Signaling Enable, otherwise the interaction/behaviour between
> phy and controller will be undefined. Mostly it works fine if we do
> that, but we still see failures. Anyway, let's fix it to m
On Wednesday 28 September 2016, Sinan Kaya wrote:
> On 9/27/2016 6:58 PM, Rafael J. Wysocki wrote:
> >> :04 04 9bf16c388d23bb66e087809f069eafed18e46a8c
> >> : bcac95fb33ee834aec7d23eab9eb0dc5e330c68c M drivers
> >
> > OK
> >
> > Sinan, can you help, please?
>
> Sure, let's see what's g
Hi,
This is the second version of Synaptics RMI4 over SMBus. There are few
differences compared to the previous submission:
- comments from Andrew are addressed
- fixed an oops when using the "rescan" feature from serio/drvctrl
- use alloc_ordered_workqueue instead of create_singlethread_workqueue
Typos...
Signed-off-by: Benjamin Tissoires
---
new in v2
---
include/linux/rmi.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/rmi.h b/include/linux/rmi.h
index 02e1dae..a4bbe90 100644
--- a/include/linux/rmi.h
+++ b/include/linux/rmi.h
@@ -106,7 +106,7 @@ s
From: Lyude Paul
This adds basic functionality for PS/2 passthrough on Synaptics
Touchpads using RMI4 through smbus.
Reviewed-by: Andrew Duggan
Signed-off-by: Lyude Paul
Signed-off-by: Benjamin Tissoires
---
changes in v2:
- switch to use rmi_dbg instead of plain dev_dbg
---
drivers/input/
If struct rmi_device_platform_data contains pointers to other struct,
it gets difficult to allocate a fixed size struct and copy it over between
drivers.
Change the pointers into a struct and change the code in rmi4 accordingly.
Reviewed-by: Andrew Duggan
Signed-off-by: Benjamin Tissoires
---
This driver is a glue between PS/2 devices that enumerate
the RMI4 device and the RMI4 SMBus driver.
We mostly use an intermediate platform device to not
add a dependency between psmouse and I2C. It also handles
the subtleties of going around the serio mutex lock by
deferring the i2c creation/dest
The SMBus Synaptics devices enumerated as PS/2 devices have
the problem of being deaf to I2C if the touchpad has been
fully initialized over PS/2 (psmouse_activate being called).
A simple PS/2 deactivate command is enough to make it back alive.
To make sure the pass-through device does not interfe
From: Dennis Wassenberg
First check if there are data available passed by the transport device.
If data available use these data. If there are no data available
try to read the rmi block if dsata are passed this way.
This is the way the other rmi function handlers will do this.
This patch is ne
With RMI4 over SMBus, the pass-through device can be instantiated
in a SMBus driver. However, compared to the psmouse-synaptics driver,
this pass-through PS/2 driver has no clue whether the current
serio_interrupt() is the beginning of the frame or not. Instead of
adding a protocol analysis in RMI4
If a function needs to communicate with an other, it's better to have
a way to retrieve this other.
Reviewed-by: Andrew Duggan
Signed-off-by: Benjamin Tissoires
---
no changes in v2
---
drivers/input/rmi4/rmi_driver.c | 13 +
drivers/input/rmi4/rmi_driver.h | 1 +
2 files changed
Code obtained from
https://raw.githubusercontent.com/mightybigcar/synaptics-rmi4/jf/drivers/input/rmi4/rmi_smbus.c
and updated to match upstream. And fixed to make it work.
Signed-off-by: Benjamin Tissoires
Signed-off-by: Andrew Duggan
---
no changes in v2
Changes in v1 of this series:
- rel
Most of the Synaptics devices are connected through PS/2 and a different
bus (SMBus or HID over I2C).
The secondary bus capability is indicated by the InterTouch bit in
extended capability 0x0C.
When we encounter such a device, we can create a platform device with
the information gathered through
In some rare cases, we can't retrieve the SMBus version and so we fail
binding the touchpad back. Instead of leaving a touchpad dead, try again
to reinitialize it.
Signed-off-by: Benjamin Tissoires
---
no changes in v2
---
drivers/input/rmi4/rmi_smbus.c | 21 -
1 file chang
On the latest series of ThinkPads, the button events for the TrackPoint
are reported through the touchpad itself as opposed to the TrackPoint
device. In order to report these buttons properly, we need to forward
them to the TrackPoint device and send the button presses/releases
through there instea
On Tue, Sep 27, 2016 at 12:33:27PM -0700, Babu Moger wrote:
> This new config parameter limits the space used for "Lock debugging:
> prove locking correctness" by about 4MB. The current sparc systems have
> the limitation of 32MB size for kernel size including .text, .data and
> .bss sections. With
On Wed, Sep 28, 2016 at 1:23 AM, Calvin Owens wrote:
> This implements ndo_poll_controller in net_device_ops callback for mlx5,
> which is necessary to use netconsole with this driver.
>
> Cc: Saeed Mahameed
> Signed-off-by: Calvin Owens
Acked-By: Saeed Mahameed
On 24/09/16 01:30, Greg Kroah-Hartman wrote:
On Fri, Sep 23, 2016 at 05:11:48PM +0200, Greg Kroah-Hartman wrote:
On Fri, Sep 23, 2016 at 06:25:33AM -0700, Guenter Roeck wrote:
On 09/23/2016 01:08 AM, Greg Kroah-Hartman wrote:
On Thu, Sep 22, 2016 at 08:01:35PM -0700, Guenter Roeck wrote:
e576
On Wed, Sep 28, 2016 at 10:53:49AM +0300, Roger Quadros wrote:
> Hi,
>
> On 12/09/16 14:38, Roger Quadros wrote:
> > Hi Santosh & Russell,
> >
> > On 19/08/16 19:38, Santosh Shilimkar wrote:
> >>
> >> On 8/19/2016 12:30 AM, Roger Quadros wrote:
> >>> Hi Santosh,
> >>>
> >>
> > So I'm 99.9% co
On Wednesday, September 28, 2016 1:18 AM Tim Chen wrote
>
> @@ -447,8 +505,9 @@ static void scan_swap_map_try_ssd_cluster(struct
> swap_info_struct *si,
> unsigned long *offset, unsigned long *scan_base)
> {
> struct percpu_cluster *cluster;
> + struct swap_cluster_info *ci;
>
Hillf Danton writes:
> On Wednesday, September 28, 2016 1:18 AM Tim Chen wrote
>>
>> @@ -447,8 +505,9 @@ static void scan_swap_map_try_ssd_cluster(struct
>> swap_info_struct *si,
>> unsigned long *offset, unsigned long *scan_base)
>> {
>> struct percpu_cluster *cluster;
>> +struc
From: Calvin Owens
Date: Tue, 27 Sep 2016 15:23:27 -0700
> This implements ndo_poll_controller in net_device_ops callback for mlx5,
> which is necessary to use netconsole with this driver.
>
> Cc: Saeed Mahameed
> Signed-off-by: Calvin Owens
> ---
> Changes in v2:
> * Only iterate channe
> Jan,
>
> Can you check if the problem occurs with this patch?
No issues in over-night test with this patch.
> --- a/drivers/crypto/vmx/vmx.c
> +++ b/drivers/crypto/vmx/vmx.c
> @@ -28,6 +28,8 @@
> #include
> #include
>
> +int p8_ghash_fallback_descsize(void);
> +
> extern struct shash_al
On 09/28/2016 03:41 AM, Johannes Weiner wrote:
> Hi guys,
>
> we noticed what looks like a regression in page mobility grouping
> during an upgrade from 3.10 to 4.0. Identical machines, workloads, and
> uptime, but /proc/pagetypeinfo on 3.10 looks like this:
>
> Number of blocks type Unmovabl
In criu we are actively using diag interface to collect sockets
present in the system when dumping applications. And while for
unix, tcp, udp[lite], packet, netlink it works as expected,
the raw sockets do not have. Thus add it.
v2:
- add missing sock_put calls in raw_diag_dump_one (by eric.dumaz
This is the start of the stable review cycle for the 4.4.23 release.
There are 73 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Fri Sep 30 09:04:22 UTC 2016.
Anything receive
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jeff Mahoney
commit 0a11b9aae49adf1f952427ef1a1d9e793dd6ffb6 upstream.
new_insert_key only makes any sense when it's associated with a
new_insert_ptr, which is initialized to NULL and changed t
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Herbert Xu
commit 53a5d5ddccf849dbc27a8c1bba0b43c3a45fb792 upstream.
The current implementation uses a global per-cpu array to store
data which are used to derive the next IV. This is insecure
4.7-stable review patch. If anyone has any objections, please let me know.
--
From: Jeff Mahoney
commit 0a11b9aae49adf1f952427ef1a1d9e793dd6ffb6 upstream.
new_insert_key only makes any sense when it's associated with a
new_insert_ptr, which is initialized to NULL and changed t
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Joseph Qi
commit e6f0c6e6170fec175fe676495f29029aecdf486c upstream.
Commit ac7cf246dfdb ("ocfs2/dlm: fix race between convert and recovery")
checks if lockres master has changed to identify whe
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Michal Nazarewicz
commit 8f57e4d930d48217268315898212518d4d3e0773 upstream.
Rewrite abs() so that its return type does not depend on the
architecture and no unexpected type conversion happen in
This is the start of the stable review cycle for the 4.7.6 release.
There are 69 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Fri Sep 30 09:04:31 UTC 2016.
Anything received
4.7-stable review patch. If anyone has any objections, please let me know.
--
From: Ard Biesheuvel
commit 2db34e78f126c6001d79d3b66ab1abb482dc7caa upstream.
The AES-CTR glue code avoids calling into the blkcipher API for the
tail portion of the walk, by comparing the remainder
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Xander Huff
[ Upstream commit c3e70edd7c2eed6acd234627a6007627f5c76e8e ]
This reverts:
commit 33c133cc7598 ("phy: IRQ cannot be shared")
On hardware with multiple PHY devices hooked up to t
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Michal Marek
commit a85a41ed69f27c4c667d8c418df14b4fb220c4ad upstream.
Based on a x86-only patch by Andy Lutomirski
With modular kernels, 'make install' is going to need the installed
modules
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Torvalds
commit 6e8d666e925333c55378e8d5540a8a9ee0eea9c5 upstream.
Several build configurations had already disabled this warning because
it generates a lot of false positives. But some
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit 86d65b7e7a0c927d07d18605c276d0f142438ead upstream.
gcc-6 warns about code in the nouveau driver that is obviously silly:
drivers/gpu/drm/nouveau/nvkm/engine/pm/nv40.c: In
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Davide Caratti
[ Upstream commit 9264251ee2a55bce8fb93826b3f581fb9eb7e2c2 ]
commit bc8c20acaea1 ("bridge: multicast: treat igmpv3 report with
INCLUDE and no sources as a leave") seems to have
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Herbert Xu
commit acdb04d0b36769b3e05990c488dc74d8b7ac8060 upstream.
When we need to allocate a temporary blkcipher_walk_next and it
fails, the code is supposed to take the slow path of process
4.7-stable review patch. If anyone has any objections, please let me know.
--
From: Herbert Xu
commit 53a5d5ddccf849dbc27a8c1bba0b43c3a45fb792 upstream.
The current implementation uses a global per-cpu array to store
data which are used to derive the next IV. This is insecure
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Ian Kent
commit 7cbdb4a286a60c5d519cb9223fe2134d26870d39 upstream.
Somewhere along the way the autofs expire operation has changed to hold
a spin lock over expired dentry selection. The autofs
4.7-stable review patch. If anyone has any objections, please let me know.
--
From: Ard Biesheuvel
commit f82e90b28654804ab72881d577d87c3d5c65e2bc upstream.
The AES-CTR glue code avoids calling into the blkcipher API for the
tail portion of the walk, by comparing the remainder
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit e72e2dfe7c16ffbfbabf9cb24adc6d9f93a4fe37 upstream.
When gcov profiling is enabled, we see a lot of spurious warnings about
possibly uninitialized variables being used:
arc
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit f4cceb2affcd1285d4ce498089e8a79f4cd2fa66 upstream.
If kmap fails, it leads to memory corruption.
Fixes: f64122c1f6ad ('drm: add new QXL driver. (v1.4)')
Signed-off-by: Dan
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Steven Rostedt
commit 377ccbb483738f84400ddf5840c7dd8825716985 upstream.
With the latest gcc compilers, they give a warning if
__builtin_return_address() parameter is greater than 0. That is be
4.7-stable review patch. If anyone has any objections, please let me know.
--
From: Arvind Yadav
commit bae170efd6c42bf116f513a1dd07639d68fa71b9 upstream.
Free memory mapping, if probe is not successful.
Fixes: 4a9b37371822 ("power: reset: move hisilicon reboot code")
Signed-
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Al Viro
commit 1ae2293dd6d2f5c823cf97e60b70d03631cd622f upstream.
Signed-off-by: Al Viro
Signed-off-by: Greg Kroah-Hartman
---
kernel/trace/trace.c | 14 --
1 file changed, 8
4.7-stable review patch. If anyone has any objections, please let me know.
--
From: John Youn
commit 168d7c4e8bb25c076ed8be67fcca84f5dcd0b2c6 upstream.
Prior to commit 6c96f05c8bb8 ("reset: Make [of_]reset_control_get[_foo]
functions wrappers"), the "optional" functions return
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Sven Van Asbroeck
commit 5381cfb6f0422da24cfa9da35b0433c0415830e0 upstream.
The device's model download function returns the model data as
an array of u32s, which is later compared to the refer
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins
commit b385d21f27d86426472f6ae92a231095f7de2a8d upstream.
init_tlb_ubc() looked unnecessary to me: tlb_ubc is statically
initialized with zeroes in the init_task, and copied from p
4.7-stable review patch. If anyone has any objections, please let me know.
--
From: Ashish Samant
commit d21c353d5e99c56cdd5b5c1183ffbcaf23b8b960 upstream.
If we punch a hole on a reflink such that following conditions are met:
1. start offset is on a cluster boundary
2. end
4.7-stable review patch. If anyone has any objections, please let me know.
--
From: Jeff Mahoney
commit 325c50e3cebb9208009083e841550f98a863bfa0 upstream.
If the subvol/snapshot create/destroy ioctls are passed a regular file
with execute permissions set, we'll eventually Oops
4.7-stable review patch. If anyone has any objections, please let me know.
--
From: Yadi.hu
commit 371a015344b6e270e7e3632107d9554ec6d27a6b upstream.
the eg20t driver call request_irq() function before the pch_base_address,
base address of i2c controller's register, is assigne
4.7-stable review patch. If anyone has any objections, please let me know.
--
From: Steven Rostedt (Red Hat)
commit 1245800c0f96eb6ebb368593e251d66c01e61022 upstream.
The iter->seq can be reset outside the protection of the mutex. So can
reading of user data. Move the mutex up
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Paul Burton
commit 7e956304eb8a285304a78582e4537e72c6365f20 upstream.
In the mipsr2_decoder() function, used to emulate pre-MIPSr6
instructions that were removed in MIPSr6, the init_fpu() funct
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Sudeep Holla
commit 331dcf421c34d227784d07943eb01e4023a42b0a upstream.
If the i2c device is already runtime suspended, if qup_i2c_suspend is
executed during suspend-to-idle or suspend-to-ram it
4.7-stable review patch. If anyone has any objections, please let me know.
--
From: Fabio Estevam
commit 4de349e786a3a2d51bd02d56f3de151bbc3c3df9 upstream.
On a imx6ul-pico board the following error is seen during system suspend:
dpm_run_callback(): platform_pm_resume+0x0/0x5
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: James Hogan
commit 554af0c396380baf416f54c439b99b495180b2f4 upstream.
The page structures associated with the vDSO pages in the kernel image
are calculated using virt_to_page(), which uses __pa
4.7-stable review patch. If anyone has any objections, please let me know.
--
From: Marek Vasut
commit 8d58790b832e13d6006d842037732304af357c3c upstream.
Configure the transmitter delay register at +0x1c to correctly handle
the CAN FD bitrate switch (BRS). This moves the SSP (
4.7-stable review patch. If anyone has any objections, please let me know.
--
From: Steven Rostedt
commit 377ccbb483738f84400ddf5840c7dd8825716985 upstream.
With the latest gcc compilers, they give a warning if
__builtin_return_address() parameter is greater than 0. That is be
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit ad5987b47e96a0fb6d13fea250e936aed93c upstream.
Due to an apparent copy/paste bug, the number of counters for the
beacon configuration were checked twice, instead of che
4.7-stable review patch. If anyone has any objections, please let me know.
--
From: Ilya Dryomov
commit 281dbe5db81c6137def9757e07a7aea14b1ed86e upstream.
An on-stack oid in ceph_ioctl_get_dataloc() is not initialized,
resulting in a WARN and a NULL pointer dereference later o
4.7-stable review patch. If anyone has any objections, please let me know.
--
From: Wei Yongjun
commit c22e853a2ed19321d00c1eae339ffdc4f5e7757e upstream.
In case of error, the function ceph_alloc_page_vector() returns
ERR_PTR() and never returns NULL. The NULL test in the retu
1 - 100 of 912 matches
Mail list logo
