What do you think about the following patches doing it?
drivers/platform/x86/scu.c:1541:3-8: No need to set .owner here. The core will
do it.
Remove .owner field if calls are used which set it automatically
Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci
CC: Guenter Roeck
Signed-off-by: Fengguang Wu
---
scu.c |1 -
1 file c
Hi Guenter,
[auto build test WARNING on platform-drivers-x86/for-next]
[also build test WARNING on v4.10-rc3 next-20170113]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Florian-Fainelli
Actually, this 1/2 patch will be useful only with combining crossrelease
implementation. However, you can easily guess the way to handle
stack_trace in crossrelease with these two patches.
->8-
>From 8093188ebba720a1a79cd73c52e992bad7d15bfd Mon Sep 17 00:00:00 2001
From: Byungchul Park
Da
-Yushchenko/dma-mapping-let-arch-know-origin-of-dma-range-passed-to-arch_setup_dma_ops/20170113-152733
config: arm64-defconfig (attached as .config)
compiler: aarch64-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
wget
https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git
On Thu, Jan 12, 2017 at 06:02:38PM +0100, Vlastimil Babka wrote:
> > Signed-off-by: Mel Gorman
> > Acked-by: Hillf Danton
> > Acked-by: Jesper Dangaard Brouer
>
> Very promising! But I have some worries. Should we put something like
> VM_BUG_ON(in_interrupt()) into free_hot_cold_page() and rmqu
Currently, a separate stack_trace instance cannot be used in
check_prev_add(). The simplest way to achieve it is to pass a
stack_trace instance to check_prev_add() as an argument after
saving it. However, unnecessary saving can happen if so implemented.
The proper solution is to pass a callback fu
On Thu, 2017-01-12 at 11:39 +0100, Ulf Hansson wrote:
> On 12 January 2017 at 11:04, Yong Mao wrote:
> > From: yong mao
> >
> > CMD response CRC error may cause cannot boot up
> > Change to use data tune for CMD line
> > Separate cmd internal delay for HS200/HS400 mode
>
> Please try to work a l
On Wed, Jan 11, 2017 at 11:06:39PM +0800, Hanjun Guo wrote:
> With the preparation of platform msi support and interrupt producer
> in DSDT, we can add mbigen ACPI support now.
>
> We are using _PRS methd to indicate number of irq pins instead
> of num_pins in DT to avoid _DSD usage in this case.
On Fri, Jan 13, 2017 at 09:54:02AM +, Alan J. Wylie wrote:
> root 1669 0.0 0.0 76144 5412 ?S09:51 0:00 \_
> /usr/sbin/postdrop -r
>
> Another hang.
>
> # dmesg | tail
> [ 22.352442] r8169 :03:00.0: loading
> /lib/firmware/4.9.3-dirty/rtl_nic/rtl8168e-3
On Wed, Jan 11, 2017 at 11:06 PM, Hanjun Guo wrote:
> With platform msi support landed in the kernel, and the introduction
> of IORT for GICv3 ITS (PCI MSI) and SMMU, the framework for platform msi
> is ready, this patch set add few patches to enable the ACPI platform
> msi support.
>
> For platfo
Boris,
On 1/13/17 00:52, Borislav Petkov wrote:
On Mon, Jan 09, 2017 at 09:33:47PM -0600, Suravee Suthikulpanit wrote:
This patch adds multi-IOMMU support for perf by exposing
an AMD IOMMU PMU for each IOMMU found in the system via:
/sys/device/amd_iommu_x /* where x is the IOMMU index.
Hi Markus,
On Fri, Jan 13, 2017 at 10:48 AM, SF Markus Elfring
wrote:
> --- a/drivers/sh/intc/core.c
> +++ b/drivers/sh/intc/core.c
> @@ -253,7 +253,8 @@ int __init register_intc_controller(struct intc_desc
> *desc)
> }
>
> if (hw->prio_regs) {
> - d->prio = kzallo
On Fri, Jan 13, 2017 at 12:01:03AM -0800, David Carrillo-Cisneros wrote:
> On Thu, Jan 12, 2017 at 4:14 AM, Mark Rutland wrote:
> > On Tue, Jan 10, 2017 at 12:51:58PM -0800, David Carrillo-Cisneros wrote:
> >> On Tue, Jan 10, 2017 at 8:38 AM, Mark Rutland wrote:
> >> > That's a fair point. Sorti
kbuild test robot wrote:
>fs/afs/cmservice.c: In function 'afs_deliver_cb_init_call_back_state3':
> >> fs/afs/cmservice.c:365:34: error: invalid application of 'sizeof' to
> >> incomplete type 'struct uuid_v1'
> call->request = kmalloc(sizeof(struct uuid_v1), GFP_KERNEL);
>
at 10:20 on Fri 13-Jan-2017 Al Viro (v...@zeniv.linux.org.uk) wrote:
> OK, so it is iov_iter_advance() failing to free the shit allocated, either
> due to some breakage in pipe_advance() or buggered 'copied'... Let's
> see which one; could you apply the following and run your reproducer? The
> o
On Thu, Jan 12, 2017 at 05:51:56PM +, Igor Druzhinin wrote:
> Eliminate memory leaks introduced several years ago by cleaning the queue
> resources which are allocated on XenBus connection event. Namely, queue
> structure array and pages used for IO rings.
> vif->lock is used to protect statist
Hi Arnd,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 557ed56cc75e0a33c15ba438734a280bac23bd32
commit: a76bcf557ef408b368cf26f52a60865bfc27b632 Kbuild: enable
-Wmaybe-uninitialized warning for "make W=1"
date:
-Yushchenko/dma-mapping-let-arch-know-origin-of-dma-range-passed-to-arch_setup_dma_ops/20170113-152733
config: x86_64-randconfig-u0-01131618 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH
When --state option is given, the summary will show total run, sleep,
iowait, preempt and delay time instead of statistics of runtime.
$ perf sched timehist -s --state
Wait-time summary
comm parent sched-in run-time sleep
iowait preempt
The --state option is to show task state when switched out. The state
is printed as a single character like in the /proc but I added 'I' for
idle state rather than 'R'.
$ perf sched timehist --state | head
Samples do not have callchains.
timecpu task name
Separate thread wait time into 3 parts - sleep, iowait and preempt
based on the prev_state of the last event.
Cc: David Ahern
Signed-off-by: Namhyung Kim
---
tools/perf/builtin-sched.c | 50 --
1 file changed, 44 insertions(+), 6 deletions(-)
diff --
Suggested-by: Borislav Petkov
Signed-off-by: Nicolas Dichtel
---
arch/x86/include/uapi/asm/Kbuild | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/x86/include/uapi/asm/Kbuild b/arch/x86/include/uapi/asm/Kbuild
index 3dec769cadf7..1c532b3f18ea 100644
--- a/arch/x86/include/uapi/asm/Kbuild
After the last four patches, all exported headers are under uapi/, thus
input-files2 are not needed anymore.
The side effect is that input-files1-name is exactly header-y.
Note also that input-files3-name is genhdr-y.
Signed-off-by: Nicolas Dichtel
---
scripts/Makefile.headersinst | 34
This patch adds thermal driver for ZTE's zx2967 family.
Signed-off-by: Baoyou Xie
---
drivers/thermal/Kconfig | 6 +
drivers/thermal/Makefile | 1 +
drivers/thermal/zx2967_thermal.c | 253 +++
3 files changed, 260 insertions(+)
create mod
This header file is exported, but from a userland pov, it's just a wrapper
to asm-generic/setup.h.
Signed-off-by: Nicolas Dichtel
---
arch/nios2/include/uapi/asm/Kbuild | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/nios2/include/uapi/asm/Kbuild
b/arch/nios2/include/uapi/asm/Kbuild
in
Add the zx2967 thermal drivers as maintained by ARM ZTE
architecture maintainers, as they're parts of the core IP.
Signed-off-by: Baoyou Xie
---
MAINTAINERS | 2 ++
1 file changed, 2 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 64f04df..2793808 100644
--- a/MAINTAINERS
+++ b/MAINT
> -Original Message-
> From: Wei Liu [mailto:wei.l...@citrix.com]
> Sent: 13 January 2017 10:38
> To: Igor Druzhinin
> Cc: Wei Liu ; xen-de...@lists.xenproject.org; Paul
> Durrant ; net...@vger.kernel.org; linux-
> ker...@vger.kernel.org
> Subject: Re: [PATCH] xen-netback: fix memory leaks
This header file is exported, thus move it to uapi.
Signed-off-by: Nicolas Dichtel
---
arch/h8300/include/asm/bitsperlong.h | 14 --
arch/h8300/include/uapi/asm/bitsperlong.h | 14 ++
2 files changed, 14 insertions(+), 14 deletions(-)
delete mode 100644 arch/h8300/i
On Fri, Jan 13, 2017 at 08:42:03AM +0200, Kalle Valo wrote:
> Greg Kroah-Hartman writes:
>
> > On Tue, Jan 10, 2017 at 10:51:56PM +0100, Willy Tarreau wrote:
> >> On Tue, Jan 10, 2017 at 03:23:27PM -0600, l...@pengaru.com wrote:
> >> > On Tue, Jan 10, 2017 at 09:40:24PM +0100, Greg Kroah-Hartman
This patch removes the need of subdir-y. Now all files/directories under
arch//include/uapi/ are exported.
The only change for userland is the layout of the command 'make
headers_install_all': directories asm- are replaced by arch-/.
Those new directories contains all files/directories of the spec
Regularly, when a new header is created in include/uapi/, the developer
forgets to add it in the corresponding Kbuild file. This error is usually
detected after the release is out.
In fact, all headers under uapi directories should be exported, thus it's
useless to have an exhaustive list.
After
Hi David,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.10-rc3 next-20170113]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/David-Howells/afs-Move-UUID-struct-to-linux
On Wed, Jan 11, 2017 at 11:06:36PM +0800, Hanjun Guo wrote:
> platform_msi_create_device_domain() is used to ctreate
> irqdomain for the device such as irqchip mbigen generating
> the MSIs, it's almost ready for ACPI use except
> of_node_to_fwnode() is for dt only, make it ACPI aware then
> things
This option was added in commit c7bb349e7c25 ("kbuild: introduce destination-y
for exported headers") but never used in-tree.
Signed-off-by: Nicolas Dichtel
---
Documentation/kbuild/makefiles.txt | 23 ---
scripts/Makefile.headersinst | 2 +-
2 files changed, 5 inserti
Here is the v3 of this series. The first 5 patches are just cleanup: some
exported headers were still under a non-uapi directory or (x86 case) were
wrongly exported.
The patch 6 was spotted by code review: there is no in-tree user of this
functionality.
Patches 7 and 8 remove the need to list expli
On 12.01.2017 07:41, Tomasz Nowicki wrote:
On 11.01.2017 13:19, Robin Murphy wrote:
On 11/01/17 11:51, 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 co
This header file is exported, thus move it to uapi.
Signed-off-by: Nicolas Dichtel
---
arch/arm/include/asm/types.h | 40 ---
arch/arm/include/uapi/asm/types.h | 40 +++
2 files changed, 40 insertions(+), 40 deletions(-
This patch adds dt-binding documentation for zx2967 family thermal sensor.
Signed-off-by: Baoyou Xie
Acked-by: Rob Herring
Reviewed-by: Shawn Guo
---
.../devicetree/bindings/thermal/zx2967-thermal.txt | 21 +
1 file changed, 21 insertions(+)
create mode 100644 Documentati
On 13/01/17 10:43, Tomasz Nowicki wrote:
> On 12.01.2017 07:41, Tomasz Nowicki wrote:
>> On 11.01.2017 13:19, Robin Murphy wrote:
>>> On 11/01/17 11:51, Tomasz Nowicki wrote:
The goal of erratum #27704 workaround was to make sure that ASIDs and
VMIDs
are unique across all SMMU instan
On 2017-01-13 at 11:46:41 +0100, Nicolas Dichtel
wrote:
> This header file is exported, but from a userland pov, it's just a wrapper
> to asm-generic/setup.h.
>
> Signed-off-by: Nicolas Dichtel
Reviewed-by: Tobias Klauser
From: Florian Fainelli
> Sent: 12 January 2017 22:51
> On 01/12/2017 01:21 PM, David Miller wrote:
> > From: Florian Fainelli
> > Date: Wed, 11 Jan 2017 19:41:16 -0800
> >
> >> Add a helper function to lookup a device reference given a class name.
> >> This is a preliminary patch to remove adhoc c
On Fri, Jan 06, 2017 at 10:54:38PM +0100, Yves-Alexis Perez wrote:
> On Fri, 2017-01-06 at 22:43 +0100, Greg Kroah-Hartman wrote:
> > 4.8-stable review patch. If anyone has any objections, please let me know.
>
> Hi Greg,
>
> Ben Gamari think there was a regression in that patch so I'm adding hi
On Fri, Jan 13, 2017 at 07:20:48AM +, David Carrillo-Cisneros wrote:
> On Thu, Jan 12, 2017 at 3:05 AM, Mark Rutland wrote:
> > On Tue, Jan 10, 2017 at 12:45:31PM -0800, David Carrillo-Cisneros wrote:
> >> >> diff --git a/include/linux/perf_event.h b/include/linux/perf_event.h
> >> >> index 47
On 13/01/17 10:00, Shawn Lin wrote:
> Hi,
>
> Sorry for sending this RFC for help as I couldn't find some useful hint
> to slove my issue by git-log the swiotlb commit from kernel v4.4 to
> v4.9 and I'm also not familar with these stuff. So could you kindly
> point me to the right direction to deb
A separate variable is not needed to handle error codes returned by
acpi_bus_register_driver(). If the latter fails, just use the value it
returned as the value returned by fujitsu_init().
Signed-off-by: Michał Kępień
---
drivers/platform/x86/fujitsu-laptop.c | 14 +-
1 file changed
On Fri 2017-01-13 11:28:43, Sergey Senozhatsky wrote:
> On (01/12/17 15:18), Petr Mladek wrote:
> > On Mon 2016-12-26 20:34:07, Sergey Senozhatsky wrote:
> > > console_trylock() used to always forbid rescheduling; but it got changed
> > > like a yaer ago.
> > >
> > > the other thing is... do we re
Linus,
The following changes since commit a121103c922847ba5010819a3f250f1f7fc84ab8:
Linux 4.10-rc3 (2017-01-08 14:18:17 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
for you to fetch changes up to 33ab91103b3415e12457e3104f0e451
Hi,
On 13/01/17 05:18, William Wu wrote:
> From: William wu
>
> The commit 4ac53087d6d4 ("usb: xhci: plat: Create both
> HCDs before adding them") move add hcd to the end of
> probe, this cause hcc_params uninitiated, because xHCI
> driver sets hcc_params in xhci_gen_setup() called from
> usb_ad
These patches should make fujitsu_init() a bit more palatable. I
intentionally stopped after four patches, because they should do no harm
and the next steps require some discussion.
The problem I have with this driver is that it is generally oblivious to
the user's chosen backlight provider. It
Error labels currently used in fujitsu_init() are really hard to follow:
some (fail_hotkey) indicate which operation has failed, others
(fail_sysfs_group) indicate where unrolling should start and the rest
(fail_platform_driver) is simply confusing. Change them to follow the
pattern used throughou
Move code responsible for backlight device registration to a separate
function in order to simplify error handling and decrease indentation.
Simplify initialization of struct backlight_properties. Use
KBUILD_MODNAME as device name to avoid repeating the same string literal
throughout the module.
Registering an ACPI driver does not mean the device it handles has to
exist. As the code which syncs backlight power status uses
call_fext_func(), it needs the FUJ02E3 ACPI device to be present, so
ensure that code is only run once the FUJ02E3 device is detected.
Signed-off-by: Michał Kępień
---
On 01/13/2017 09:15 AM, Hannes Reinecke wrote:
> On 01/11/2017 10:39 PM, Jens Axboe wrote:
>> Another year, another posting of this patchset. The previous posting
>> was here:
>>
>> https://www.spinics.net/lists/kernel/msg2406106.html
>>
>> (yes, I've skipped v5, it was fixes on top of v4, not the
On Thu, 12 Jan 2017, Johan Hovold wrote:
> These patches fix DMA buffers on stack and information leaks in the
> corsair HID driver.
>
> Note that this series has only been compile tested.
Adding Clément to CC, and applying to for-4.10/upstream-fixes branch.
Thanks!
--
Jiri Kosina
SUSE Labs
On 13/01/17 10:38, Wei Liu wrote:
> On Thu, Jan 12, 2017 at 05:51:56PM +, Igor Druzhinin wrote:
>> Eliminate memory leaks introduced several years ago by cleaning the queue
>> resources which are allocated on XenBus connection event. Namely, queue
>> structure array and pages used for IO rings.
Add support for DMA_ATTR_FORCE_CONTIGUOUS to the generic IOMMU DMA code.
This allows to allocate physically contiguous DMA buffers on arm64
systems with an IOMMU.
Note that as this uses the CMA allocator, setting this attribute has a
runtime-dependency on CONFIG_DMA_CMA, just like on arm32.
For a
On Thu, Jan 12, 2017 at 9:04 PM, Tahsin Erdogan wrote:
> fuse_abort_conn() moves requests from pending list to a temporary list
> before canceling them. This operation races with request_wait_answer()
> which also tries to remove the request after it gets a fatal signal. It
> checks FR_PENDING fla
[...]
>>> >
>>> > In the meantime, I will follow the process of Haibo Chen's debugging
>>> > around the voltage switch issue and look into what Dong's suggesting
>>> > around this may be.
>>> >
>>> > Just to be clear, I would definitely prefer a fix in the sdhci driver,
>>>
>>> yup, I prefer to fi
On Fri 2017-01-13 11:52:55, Sergey Senozhatsky wrote:
> On (01/12/17 14:10), Petr Mladek wrote:
> [..]
> > > /**
> > > * console_lock - lock the console system for exclusive use.
> > > *
> > > @@ -2316,7 +2321,7 @@ EXPORT_SYMBOL(console_unlock);
> > > */
> > > void __sched console_condition
On 01/11/2017 10:40 PM, Jens Axboe wrote:
> This adds a set of hooks that intercepts the blk-mq path of
> allocating/inserting/issuing/completing requests, allowing
> us to develop a scheduler within that framework.
>
> We reuse the existing elevator scheduler API on the registration
> side, but a
On Fri 2017-01-13 12:53:07, Sergey Senozhatsky wrote:
> On (01/13/17 11:52), Sergey Senozhatsky wrote:
> [..]
> > and we really don't want to cond_resched() when we are in panic.
> > that's why console_flush_on_panic() sets it to zero explicitly.
> >
> > console_trylock() checks oops_in_progress,
On Tue, Dec 13, 2016 at 8:50 PM, Dmitry Vyukov wrote:
> Hello,
>
> The following program:
> https://gist.githubusercontent.com/dvyukov/23d8bd622fd526d7701ac2057bbbc9c2/raw/aacd20451e6f460232f5e1da262b653fb3155613/gistfile1.txt
>
> leads to WARNING in mmu_spte_clear_track_bits and later to splash o
On Fri, Jan 13, 2017 at 10:20:19AM +, Al Viro wrote:
> OK, so it is iov_iter_advance() failing to free the shit allocated, either
> due to some breakage in pipe_advance() or buggered 'copied'... Let's
> see which one; could you apply the following and run your reproducer? The
> only differen
On Fri, Jan 13, 2017 at 01:59:35PM +0800, miles.c...@mediatek.com wrote:
> From: Miles Chen
>
> Use phys_addr_t instead of unsigned long for the
> return value of __pa(), make code easy to understand.
>
> Signed-off-by: Miles Chen
> ---
> arch/arm64/mm/mmu.c | 4 ++--
> 1 file changed, 2 inser
this OOPS always happens with 4.9. up to 4.9.3
all 4.8.x versions work fine.
Disabling VMAP_STACK does not fix it.
[9.043616] dvb-usb: found a 'Technotrend TT Connect S2-3600' in warm state.
[9.043619] pctv452e: pctv452e_power_ctrl: 1
[9.051329] BUG: unable to handle kernel NULL po
On Fri, Jan 13, 2017 at 01:59:35PM +0800, miles.c...@mediatek.com wrote:
> From: Miles Chen
>
> Use phys_addr_t instead of unsigned long for the
> return value of __pa(), make code easy to understand.
>
> Signed-off-by: Miles Chen
This looks sensible to me. It's consistent with the types these
[...]
> Hi Ulf and Shawn,
>
> Aisheng and I debug this issue these days, and we find the root cause. There
> are two things
> to describe.
>
> 1) voltage switch issue. The properity "no-1-8-v" do not work for
> MMC_TIMING_MMC_DDR52.
> This is another bug, we need to fix, but has no relation wi
On 13 January 2017 at 11:03, Robin Murphy wrote:
> On 13/01/17 10:00, Shawn Lin wrote:
>> Hi,
>>
>> Sorry for sending this RFC for help as I couldn't find some useful hint
>> to slove my issue by git-log the swiotlb commit from kernel v4.4 to
>> v4.9 and I'm also not familar with these stuff. So c
On Fri, Jan 13, 2017 at 10:32:47AM +, Alan J. Wylie wrote:
> # dmesg | tail
> ...
> [ 141.553455] nr: 0->16, cur: 5->5, buffers: 16->16
> [ 141.553461] copied: 0, count:2147479552, idx:5, offs:0
OK, that looks like pipe_advance() fencepost (hopefully) dealt with in
the lib/iov_iter.c patch
On Thu, Jan 12, 2017 at 06:38:07PM -0800, Paul E. McKenney wrote:
> The current preemptible RCU implementation goes through three phases
> during bootup. In the first phase, there is only one CPU that is running
> with preemption disabled, so that a no-op is a synchronous grace period.
> In the se
On 01/05/2017 11:02 PM, Hari Bathini wrote:
> Now that crashkernel parameter parsing and vmcoreinfo related code is
> moved under CONFIG_CRASH_CORE instead of CONFIG_KEXEC_CORE, remove
> dependency with CONFIG_KEXEC for CONFIG_FA_DUMP. While here, get rid
> of definitions of fadump_append_elf_note(
On 13 January 2017 at 11:22, Mark Rutland wrote:
> On Fri, Jan 13, 2017 at 01:59:35PM +0800, miles.c...@mediatek.com wrote:
>> From: Miles Chen
>>
>> Use phys_addr_t instead of unsigned long for the
>> return value of __pa(), make code easy to understand.
>>
>> Signed-off-by: Miles Chen
>
> This
On Thu, Jan 12, 2017 at 11:07:08AM -0800, Bart Van Assche wrote:
> Signed-off-by: Bart Van Assche
> Reviewed-by: Christoph Hellwig
> Reviewed-by: Sagi Grimberg
> ---
> drivers/infiniband/ulp/ipoib/ipoib_cm.c | 34 +++---
> drivers/infiniband/ulp/ipoib/ipoib_ib.c | 42
>
On Fri, Jan 13, 2017 at 12:15:05PM +0100, Wolfgang Rohdewald wrote:
> this OOPS always happens with 4.9. up to 4.9.3
>
> all 4.8.x versions work fine.
Ick. Any chance you can use 'git bisect' to determine which commit
broke this for you?
thanks,
greg k-h
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: stephen hemminger
[ Upstream commit a50af86dd49ee1851d1ccf06dd0019c05b95e297 ]
Hyper-V (and Azure) support using NVGRE which requires some extra space
for encapsulation headers. Because of thi
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
[ Upstream commit 93a97c50cbf1c007caf12db5cc23e0d5b9c8473c ]
If we can't allocate the resources in gigaset_initdriver() then we
should return -ENOMEM instead of zero.
Fixes: 286
This is the start of the stable review cycle for the 4.4.43 release.
There are 27 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 Sun Jan 15 11:36:57 UTC 2017.
Anything receive
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 7cfd5fd5a9813f1430290d20c0fead9b4582a307 ]
On 32bit arches, (skb->end - skb->data) is not 'unsigned int',
so we shall use min_t() instead of min() to avoid a com
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Dennis Kadioglu
commit 2e40795c3bf344cfb5220d94566205796e3ef19a upstream.
Plantronics BT600 does not support reading the sample rate which leads
to many lines of "cannot get freq at ep 0x1" and
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Florian Fainelli
[ Upstream commit 5701659004d68085182d2fd4199c79172165fa65 ]
There is currently a small window during which the network device registered by
stmmac can be made visible, yet al
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Noa Osherovich
[ Upstream commit 883371c453b937f9eb581fb4915210865982736f ]
When setting HCA capabilities, set log_max_qp to be the minimum
between the selected profile's value and the HCA lim
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Alexander Duyck
[ Upstream commit 5350d54f6cd12eaff623e890744c79b700bd3f17 ]
In the case of custom rules being present we need to handle the case of the
LOCAL table being intialized after the
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Michal Tesar
[ Upstream commit 7ababb782690e03b78657e27bd051e20163af2d6 ]
5.2. Action on Reception of a Query
When a system receives a Query, it does not respond immediately.
Instead, it de
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Reiter Wolfgang
[ Upstream commit 3b48ab2248e61408910e792fe84d6ec466084c1a ]
Final nlmsg_len field update must reflect inserted net_dm_drop_point
data.
This patch depends on previous patch:
"
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Reiter Wolfgang
[ Upstream commit 4200462d88f47f3759bdf4705f87e207b0f5b2e4 ]
Update nlmsg_len field with genlmsg_end to enable userspace processing
using nlmsg_next helper. Also adds error han
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Jones
[ Upstream commit a98f91758995cb59611e613188a6956b52c3 ]
By setting certain socket options on ipv6 raw sockets, we can confuse the
length calculation in rawv6_push_pending_frame
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Tony Lindgren
commit cbf2642872333547b56b8c4d943f5ed04ac9a4ee upstream.
We don't want to fall through to a bunch of errors for retention
if PM_OMAP4_CPU_OSWR_DISABLE is not configured for a SoC
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: hayeswang
[ Upstream commit 75dc692eda114cb234a46cb11893a9c3ea520934 ]
Pause the rx and make sure the rx fifo is empty when the autosuspend
occurs.
If the rx data comes when the driver is can
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Larry Finger
commit 8ae679c4bc2ea2d16d92620da8e3e9332fa4039f upstream.
I am getting the following warning when I build kernel 4.9-git on my
PowerBook G4 with a 32-bit PPC processor:
AS
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: David Ahern
[ Upstream commit eb63ecc1706b3e094d0f57438b6c2067cfc299f2 ]
Locally originated traffic in a VRF fails in the presence of a POSTROUTING
rule. For example,
$ iptables -t nat -A
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: David Ahern
[ Upstream commit 7a18c5b9fb31a999afc62b0e60978aa896fc89e9 ]
fib_select_path does not call fib_select_multipath if oif is set in the
flow struct. For VRF use cases oif is always se
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: David Ahern
[ Upstream commit 24c63bbc18e25d5d8439422aa5fd2d66390b88eb ]
Frank reported that vrf devices can be created with a table id of 0.
This breaks many of the run time table id checks a
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Herbert Xu
[ Upstream commit 1272ce87fa017ca4cf32920764d879656b7a005a ]
The GRO path has a fast-path where we avoid calling pskb_may_pull
and pskb_expand by directly accessing frag0. However,
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Herbert Xu
[ Upstream commit 57ea52a865144aedbcd619ee0081155e658b6f7d ]
The GRO fast path caches the frag0 address. This address becomes
invalid if frag0 is modified by pskb_may_pull or its v
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: hayeswang
[ Upstream commit 8fb280616878b81c0790a0c33acbeec59c5711f4 ]
Split rtl8152_suspend() into rtl8152_system_suspend() and
rtl8152_rumtime_suspend().
Signed-off-by: Hayes Wang
Signed-o
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Oliver O'Halloran
commit 90cae1fe1c3540f791d5b8e025985fa5e699b2bb upstream.
As a part of memory initialisation the architecture passes an array to
free_area_init_nodes() which specifies the max
On 13/01/17 11:07, Geert Uytterhoeven wrote:
> Add support for DMA_ATTR_FORCE_CONTIGUOUS to the generic IOMMU DMA code.
> This allows to allocate physically contiguous DMA buffers on arm64
> systems with an IOMMU.
Can anyone explain what this attribute is actually used for? I've never
quite figure
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Sakamoto
commit 6a2a2f45560a9cb7bc49820883b042e44f83726c upstream.
This module has a bug not to return error code in a case that data
structure for transmitted packets fails to be initi
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Greg Kroah-Hartman
commit 1ebb71143758f45dc0fa76e2f48429e13b16d110 upstream.
Make sure we have enough of a report structure to validate before
looking at it.
Reported-by: Benoit Camredon
Test
101 - 200 of 805 matches
Mail list logo
