[PATCH 4.4 44/68] clk: rockchip: initialize flags of clk_init_data in mmc-phase clock

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Heiko Stuebner commit 595144c1141c951a3c6bb9004ae6a2bc29aad66f upstream. The flags element of clk_init_data was never initialized for mmc- phase-clocks resulting in the element containing a

[PATCH 4.4 13/68] mm, meminit: ensure node is online before checking whether pages are uninitialised

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mel Gorman commit ef70b6f41cda6270165a6f27b2548ed31cfa3cb2 upstream. early_page_uninitialised looks up an arbitrary PFN. While a machine without node 0 will boot with "mm, page_alloc: Always

[PATCH 4.4 16/68] kernel/sysrq, watchdog, sched/core: Reset watchdog on all CPUs while processing sysrq-w

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Andrey Ryabinin commit 57675cb976eff977aefb428e68e4e0236d48a9ff upstream. Lengthy output of sysrq-w may take a lot of time on slow serial console. Currently we reset

[PATCH 4.4 12/68] mm, meminit: always return a valid node from early_pfn_to_nid

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mel Gorman commit e4568d3803852d00effd41dcdd489e726b998879 upstream. early_pfn_to_nid can return node 0 if a PFN is invalid on machines that has no node 0. A

[PATCH 4.4 14/68] vmlinux.lds: account for destructor sections

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Vyukov commit e41f501d391265ff568f3e49d6128cc30856a36f upstream. If CONFIG_KASAN is enabled and gcc is configured with --disable-initfini-array and/or gold linker is

[PATCH 4.4 16/68] kernel/sysrq, watchdog, sched/core: Reset watchdog on all CPUs while processing sysrq-w

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Andrey Ryabinin commit 57675cb976eff977aefb428e68e4e0236d48a9ff upstream. Lengthy output of sysrq-w may take a lot of time on slow serial console. Currently we reset NMI-watchdog on the

[PATCH 4.4 12/68] mm, meminit: always return a valid node from early_pfn_to_nid

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mel Gorman commit e4568d3803852d00effd41dcdd489e726b998879 upstream. early_pfn_to_nid can return node 0 if a PFN is invalid on machines that has no node 0. A machine with only node 1 was

[PATCH 4.4 14/68] vmlinux.lds: account for destructor sections

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Vyukov commit e41f501d391265ff568f3e49d6128cc30856a36f upstream. If CONFIG_KASAN is enabled and gcc is configured with --disable-initfini-array and/or gold linker is used, gcc emits

[PATCH 4.4 08/68] mm, sl[au]b: add __GFP_ATOMIC to the GFP reclaim mask

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mel Gorman commit e838a45f9392a5bd2be1cd3ab0b16ae85857461c upstream. Commit d0164adc89f6 ("mm, page_alloc: distinguish between being unable to sleep, unwilling to

[PATCH 4.4 08/68] mm, sl[au]b: add __GFP_ATOMIC to the GFP reclaim mask

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mel Gorman commit e838a45f9392a5bd2be1cd3ab0b16ae85857461c upstream. Commit d0164adc89f6 ("mm, page_alloc: distinguish between being unable to sleep, unwilling to sleep and avoiding waking

[PATCH 4.4 60/68] posix_cpu_timer: Exit early when process has been reaped

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Dobriyan commit 2c13ce8f6b2f6fd9ba2f9261b1939fc0f62d1307 upstream. Variable "now" seems to be genuinely used unintialized if branch if

[PATCH 4.4 59/68] media: fix airspy usb probe error path

4.4-stable review patch. If anyone has any objections, please let me know. -- From: James Patrick-Evans commit aa93d1fee85c890a34f2510a310e55ee76a27848 upstream. Fix a memory leak on probe error of the airspy usb device driver. The problem is triggered when

[PATCH 4.4 60/68] posix_cpu_timer: Exit early when process has been reaped

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Dobriyan commit 2c13ce8f6b2f6fd9ba2f9261b1939fc0f62d1307 upstream. Variable "now" seems to be genuinely used unintialized if branch if (CPUCLOCK_PERTHREAD(timer->it_clock)) {

[PATCH 4.4 59/68] media: fix airspy usb probe error path

4.4-stable review patch. If anyone has any objections, please let me know. -- From: James Patrick-Evans commit aa93d1fee85c890a34f2510a310e55ee76a27848 upstream. Fix a memory leak on probe error of the airspy usb device driver. The problem is triggered when more than 64 usb

[PATCH 4.4 57/68] SCSI: fix new bug in scsi_dev_info_list string matching

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alan Stern commit 5e7ff2ca7f2da55fe777167849d0c93403bd0dc8 upstream. Commit b704f70ce200 ("SCSI: fix bug in scsi_dev_info_list matching") changed the way vendor- and

[PATCH 4.4 57/68] SCSI: fix new bug in scsi_dev_info_list string matching

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alan Stern commit 5e7ff2ca7f2da55fe777167849d0c93403bd0dc8 upstream. Commit b704f70ce200 ("SCSI: fix bug in scsi_dev_info_list matching") changed the way vendor- and model-string matching was

Re: [RFC PATCH V5 0/5] ECAM quirks handling for ARM64 platforms

On Mon, 2016-08-08 at 15:05 +0200, Tomasz Nowicki wrote: > Quirk handling relies on an idea of matching MCFG OEM ID, TABLE ID and > revision (the ones from standard header of MCFG table). > > Static array is used to keep quirk entries. Each entry consists of > mentioned MCFG IDs along with custom

Re: [RFC PATCH V5 0/5] ECAM quirks handling for ARM64 platforms

On Mon, 2016-08-08 at 15:05 +0200, Tomasz Nowicki wrote: > Quirk handling relies on an idea of matching MCFG OEM ID, TABLE ID and > revision (the ones from standard header of MCFG table). > > Static array is used to keep quirk entries. Each entry consists of > mentioned MCFG IDs along with custom

[PATCH 4.4 64/68] libceph: apply new_state before new_up_client on incrementals

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ilya Dryomov commit 930c532869774ebf8af9efe9484c597f896a7d46 upstream. Currently, osd_weight and osd_state fields are updated in the encoding order. This is wrong, because

[PATCH 4.4 63/68] libata: LITE-ON CX1-JB256-HP needs lower max_sectors

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Tejun Heo commit 1488a1e3828d60d74c9b802a05e24c0487babe4e upstream. Since 34b48db66e08 ("block: remove artifical max_hw_sectors cap"), max_sectors is no longer limited to

[PATCH 4.4 66/68] intel_th: pci: Add Kaby Lake PCH-H support

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Shishkin commit 7a1a47ce35821b40f5b2ce46379ba14393bc3873 upstream. This adds Intel(R) Trace Hub PCI ID for Kaby Lake PCH-H. Signed-off-by:

[PATCH 4.4 63/68] libata: LITE-ON CX1-JB256-HP needs lower max_sectors

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Tejun Heo commit 1488a1e3828d60d74c9b802a05e24c0487babe4e upstream. Since 34b48db66e08 ("block: remove artifical max_hw_sectors cap"), max_sectors is no longer limited to BLK_DEF_MAX_SECTORS

[PATCH 4.4 66/68] intel_th: pci: Add Kaby Lake PCH-H support

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Shishkin commit 7a1a47ce35821b40f5b2ce46379ba14393bc3873 upstream. This adds Intel(R) Trace Hub PCI ID for Kaby Lake PCH-H. Signed-off-by: Alexander Shishkin Signed-off-by: Greg

[PATCH 4.4 64/68] libceph: apply new_state before new_up_client on incrementals

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ilya Dryomov commit 930c532869774ebf8af9efe9484c597f896a7d46 upstream. Currently, osd_weight and osd_state fields are updated in the encoding order. This is wrong, because an incremental map

[PATCH 4.4 68/68] vfs: fix deadlock in file_remove_privs() on overlayfs

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Miklos Szeredi commit c1892c37769cf89c7e7ba57528ae2ccb5d153c9b upstream. file_remove_privs() is called with inode lock on file_inode(), which proceeds to calling

Re: [RFC PATCH 2/3] Add generation of Module.ksymb file in streamline_config.pl

On Sun, Jul 31, 2016 at 05:33:51PM +0200, Cristina Moraru wrote: > Add generation of ./scripts/mod/Module.ksymb file containing > associations of driver file names and corresponding CONFIG_* > symbol. > > This file will be used by modpost to peg kconfig CONFIG_* > symbol to its corresponding

[PATCH 4.4 49/68] sched/fair: Fix effective_load() to consistently use smoothed load

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 7dd4912594daf769a46744848b05bd5bc6d62469 upstream. Starting with the following commit: fde7d22e01aa ("sched/fair: Fix overly small weight for

[PATCH 4.4 53/68] can: c_can: Update D_CAN TX and RX functions to 32 bit - fix Altera Cyclone access

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Thor Thayer commit 427460c83cdf55069eee49799a0caef7dde8df69 upstream. When testing CAN write floods on Altera's CycloneV, the first 2 bytes are sometimes 0x00,

[PATCH 4.4 67/68] intel_th: Fix a deadlock in modprobing

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Shishkin commit a36aa80f3cb2540fb1dbad6240852de4365a2e82 upstream. Driver initialization tries to request a hub (GTH) driver module from its probe

[PATCH 4.4 51/68] perf/x86: fix PEBS issues on Intel Atom/Core2

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Stephane Eranian commit 1424a09a9e1839285e948d4ea9fdfca26c9a2086 upstream. This patch fixes broken PEBS support on Intel Atom and Core2 due to wrong pointer arithmetic in

[PATCH 4.4 54/68] can: fix handling of unmodifiable configuration options fix

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Oliver Hartkopp commit bce271f255dae8335dc4d2ee2c4531e09cc67f5a upstream. With upstream commit bb208f144cf3f59 (can: fix handling of unmodifiable configuration options)

[PATCH 4.4 68/68] vfs: fix deadlock in file_remove_privs() on overlayfs

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Miklos Szeredi commit c1892c37769cf89c7e7ba57528ae2ccb5d153c9b upstream. file_remove_privs() is called with inode lock on file_inode(), which proceeds to calling notify_change() on

Re: [RFC PATCH 2/3] Add generation of Module.ksymb file in streamline_config.pl

On Sun, Jul 31, 2016 at 05:33:51PM +0200, Cristina Moraru wrote: > Add generation of ./scripts/mod/Module.ksymb file containing > associations of driver file names and corresponding CONFIG_* > symbol. > > This file will be used by modpost to peg kconfig CONFIG_* > symbol to its corresponding

[PATCH 4.4 49/68] sched/fair: Fix effective_load() to consistently use smoothed load

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 7dd4912594daf769a46744848b05bd5bc6d62469 upstream. Starting with the following commit: fde7d22e01aa ("sched/fair: Fix overly small weight for interactive group

[PATCH 4.4 53/68] can: c_can: Update D_CAN TX and RX functions to 32 bit - fix Altera Cyclone access

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Thor Thayer commit 427460c83cdf55069eee49799a0caef7dde8df69 upstream. When testing CAN write floods on Altera's CycloneV, the first 2 bytes are sometimes 0x00, 0x00 or corrupted instead of the

[PATCH 4.4 67/68] intel_th: Fix a deadlock in modprobing

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Shishkin commit a36aa80f3cb2540fb1dbad6240852de4365a2e82 upstream. Driver initialization tries to request a hub (GTH) driver module from its probe callback, resulting in a deadlock.

[PATCH 4.4 51/68] perf/x86: fix PEBS issues on Intel Atom/Core2

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Stephane Eranian commit 1424a09a9e1839285e948d4ea9fdfca26c9a2086 upstream. This patch fixes broken PEBS support on Intel Atom and Core2 due to wrong pointer arithmetic in

[PATCH 4.4 54/68] can: fix handling of unmodifiable configuration options fix

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Oliver Hartkopp commit bce271f255dae8335dc4d2ee2c4531e09cc67f5a upstream. With upstream commit bb208f144cf3f59 (can: fix handling of unmodifiable configuration options) a new can_validate()

[PATCH 4.6 21/96] radix-tree: fix radix_tree_iter_retry() for tagged iterators.

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Andrey Ryabinin commit 3cb9185c67304b2a7ea9be73e7d13df6fb2793a1 upstream. radix_tree_iter_retry() resets slot to NULL, but it doesn't reset tags. Then NULL slot and

[PATCH 4.6 22/96] pps: do not crash when failed to register

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Slaby commit 368301f2fe4b07e5fb71dba3cc566bc59eb6705f upstream. With this command sequence: modprobe plip modprobe pps_parport rmmod pps_parport the partport_pps

[PATCH 4.6 16/96] mm, meminit: always return a valid node from early_pfn_to_nid

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Mel Gorman commit e4568d3803852d00effd41dcdd489e726b998879 upstream. early_pfn_to_nid can return node 0 if a PFN is invalid on machines that has no node 0. A

[PATCH 4.6 18/96] vmlinux.lds: account for destructor sections

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Vyukov commit e41f501d391265ff568f3e49d6128cc30856a36f upstream. If CONFIG_KASAN is enabled and gcc is configured with --disable-initfini-array and/or gold linker is

[PATCH 4.6 21/96] radix-tree: fix radix_tree_iter_retry() for tagged iterators.

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Andrey Ryabinin commit 3cb9185c67304b2a7ea9be73e7d13df6fb2793a1 upstream. radix_tree_iter_retry() resets slot to NULL, but it doesn't reset tags. Then NULL slot and non-zero iter.tags passed

[PATCH 4.6 22/96] pps: do not crash when failed to register

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Slaby commit 368301f2fe4b07e5fb71dba3cc566bc59eb6705f upstream. With this command sequence: modprobe plip modprobe pps_parport rmmod pps_parport the partport_pps modules causes

[PATCH 4.6 16/96] mm, meminit: always return a valid node from early_pfn_to_nid

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Mel Gorman commit e4568d3803852d00effd41dcdd489e726b998879 upstream. early_pfn_to_nid can return node 0 if a PFN is invalid on machines that has no node 0. A machine with only node 1 was

[PATCH 4.6 18/96] vmlinux.lds: account for destructor sections

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Vyukov commit e41f501d391265ff568f3e49d6128cc30856a36f upstream. If CONFIG_KASAN is enabled and gcc is configured with --disable-initfini-array and/or gold linker is used, gcc emits

[PATCH 4.4 46/68] qeth: delete napi struct when removing a qeth device

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ursula Braun commit 7831b4ff0d926e0deeaabef9db8800ed069a2757 upstream. A qeth_card contains a napi_struct linked to the net_device during device probing. This struct

[PATCH 4.6 10/96] memcg: css_alloc should return an ERR_PTR value on error

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Tejun Heo commit ea3a9645866e12d2b198434f03df3c3e96fb86ce upstream. mem_cgroup_css_alloc() was returning NULL on failure while cgroup core expected it to return an ERR_PTR

[PATCH 4.4 46/68] qeth: delete napi struct when removing a qeth device

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ursula Braun commit 7831b4ff0d926e0deeaabef9db8800ed069a2757 upstream. A qeth_card contains a napi_struct linked to the net_device during device probing. This struct must be deleted when

[PATCH 4.6 10/96] memcg: css_alloc should return an ERR_PTR value on error

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Tejun Heo commit ea3a9645866e12d2b198434f03df3c3e96fb86ce upstream. mem_cgroup_css_alloc() was returning NULL on failure while cgroup core expected it to return an ERR_PTR value leading to the

[PATCH 4.6 14/96] mm, compaction: prevent VM_BUG_ON when terminating freeing scanner

4.6-stable review patch. If anyone has any objections, please let me know. -- From: David Rientjes commit a46cbf3bc53b6a93fb84a5ffb288c354fa807954 upstream. It's possible to isolate some freepages in a pageblock and then fail split_free_page() due to the

[PATCH 4.6 02/96] x86/quirks: Apply nvidia_bugs quirk only on root bus

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Lukas Wunner commit 447d29d1d3aed839e74c2401ef63387780ac51ed upstream. Since the following commit: 8659c406ade3 ("x86: only scan the root bus in early PCI quirks") ...

[PATCH 4.6 14/96] mm, compaction: prevent VM_BUG_ON when terminating freeing scanner

4.6-stable review patch. If anyone has any objections, please let me know. -- From: David Rientjes commit a46cbf3bc53b6a93fb84a5ffb288c354fa807954 upstream. It's possible to isolate some freepages in a pageblock and then fail split_free_page() due to the low watermark check.

[PATCH 4.6 02/96] x86/quirks: Apply nvidia_bugs quirk only on root bus

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Lukas Wunner commit 447d29d1d3aed839e74c2401ef63387780ac51ed upstream. Since the following commit: 8659c406ade3 ("x86: only scan the root bus in early PCI quirks") ... early quirks are

[PATCH 4.6 30/96] xenbus: dont bail early from xenbus_dev_request_and_reply()

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Jan Beulich commit 7469be95a487319514adce2304ad2af3553d2fc9 upstream. xenbus_dev_request_and_reply() needs to track whether a transaction is open. For XS_TRANSACTION_START

[PATCH 4.6 31/96] xen-blkfront: fix resume issues after a migration

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Bob Liu commit 2a6f71ad99cabe436e70c3f5fcf58072cb3bc07f upstream. After a migrate to another host (which may not have multiqueue support), the number of rings (block

[PATCH 4.6 24/96] sched/debug: Fix deadlock when enabling sched events

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Josh Poimboeuf commit eda8dca519269c92a0771668b3d5678792de7b78 upstream. I see a hang when enabling sched events: echo 1 > /sys/kernel/debug/tracing/events/sched/enable

[PATCH v3 05/14] media: platform: pxa_camera: convert to vb2

Convert pxa_camera from videobuf to videobuf2. As the soc_camera was already compatible with videobuf2, the port is quite straightforward. The special case of this code in which the vb2 to prepare is "too big" in terms of size for the new capture format, the pxa_camera will fail. Signed-off-by:

Re: [PATCH] x86/hweight: Don't clobber %rdi

On Mon, Aug 08, 2016 at 08:53:16PM +0200, Jiri Kosina wrote: > Ville's patch is the proper thing to do; I still think the comments > probably should be removed as they might provide more confusion than help, > but that's a separate discussion. Right, so while trying to debug this with a pen and

[PATCH 4.6 30/96] xenbus: dont bail early from xenbus_dev_request_and_reply()

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Jan Beulich commit 7469be95a487319514adce2304ad2af3553d2fc9 upstream. xenbus_dev_request_and_reply() needs to track whether a transaction is open. For XS_TRANSACTION_START messages it calls

[PATCH 4.6 31/96] xen-blkfront: fix resume issues after a migration

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Bob Liu commit 2a6f71ad99cabe436e70c3f5fcf58072cb3bc07f upstream. After a migrate to another host (which may not have multiqueue support), the number of rings (block hardware queues) may be

[PATCH 4.6 24/96] sched/debug: Fix deadlock when enabling sched events

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Josh Poimboeuf commit eda8dca519269c92a0771668b3d5678792de7b78 upstream. I see a hang when enabling sched events: echo 1 > /sys/kernel/debug/tracing/events/sched/enable The printk buffer

[PATCH v3 05/14] media: platform: pxa_camera: convert to vb2

Convert pxa_camera from videobuf to videobuf2. As the soc_camera was already compatible with videobuf2, the port is quite straightforward. The special case of this code in which the vb2 to prepare is "too big" in terms of size for the new capture format, the pxa_camera will fail. Signed-off-by:

Re: [PATCH] x86/hweight: Don't clobber %rdi

On Mon, Aug 08, 2016 at 08:53:16PM +0200, Jiri Kosina wrote: > Ville's patch is the proper thing to do; I still think the comments > probably should be removed as they might provide more confusion than help, > but that's a separate discussion. Right, so while trying to debug this with a pen and

[PATCH 4.6 03/96] x86/quirks: Reintroduce scanning of secondary buses

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Lukas Wunner commit 850c321027c2e31d0afc71588974719a4b565550 upstream. We used to scan secondary buses until the following commit that was applied in 2009: 8659c406ade3

[PATCH v3 13/14] media: platform: pxa_camera: change stop_streaming semantics

Instead of the legacy behavior where it was required to wait for all video buffers to be finished by the hardware, use a cancel like strategy : as soon as the stop_streaming() call is done, abort all DMA transfers, report the already buffers as failed and return. This makes stop_streaming() more

[PATCH 4.6 03/96] x86/quirks: Reintroduce scanning of secondary buses

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Lukas Wunner commit 850c321027c2e31d0afc71588974719a4b565550 upstream. We used to scan secondary buses until the following commit that was applied in 2009: 8659c406ade3 ("x86: only scan the

[PATCH v3 13/14] media: platform: pxa_camera: change stop_streaming semantics

Instead of the legacy behavior where it was required to wait for all video buffers to be finished by the hardware, use a cancel like strategy : as soon as the stop_streaming() call is done, abort all DMA transfers, report the already buffers as failed and return. This makes stop_streaming() more

[PATCH 4.6 26/96] ARC: unwind: ensure that .debug_frame is generated (vs. .eh_frame)

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Vineet Gupta commit f52e126cc7476196f44f3c313b7d9f0699a881fc upstream. With recent binutils update to support dwarf CFI pseudo-ops in gas, we now get .eh_frame vs.

[PATCH v3 11/14] media: platform: pxa_camera: make a standalone v4l2 device

This patch removes the soc_camera API dependency from pxa_camera. In the current status : - all previously captures are working the same on pxa270 - the s_crop() call was removed, judged not working (see what happens soc_camera_s_crop() when get_crop() == NULL) - if the pixel clock is

[PATCH 4.6 23/96] kernel/sysrq, watchdog, sched/core: Reset watchdog on all CPUs while processing sysrq-w

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Andrey Ryabinin commit 57675cb976eff977aefb428e68e4e0236d48a9ff upstream. Lengthy output of sysrq-w may take a lot of time on slow serial console. Currently we reset

[PATCH 4.6 26/96] ARC: unwind: ensure that .debug_frame is generated (vs. .eh_frame)

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Vineet Gupta commit f52e126cc7476196f44f3c313b7d9f0699a881fc upstream. With recent binutils update to support dwarf CFI pseudo-ops in gas, we now get .eh_frame vs. .debug_frame. Although the

[PATCH v3 11/14] media: platform: pxa_camera: make a standalone v4l2 device

This patch removes the soc_camera API dependency from pxa_camera. In the current status : - all previously captures are working the same on pxa270 - the s_crop() call was removed, judged not working (see what happens soc_camera_s_crop() when get_crop() == NULL) - if the pixel clock is

[PATCH 4.6 23/96] kernel/sysrq, watchdog, sched/core: Reset watchdog on all CPUs while processing sysrq-w

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Andrey Ryabinin commit 57675cb976eff977aefb428e68e4e0236d48a9ff upstream. Lengthy output of sysrq-w may take a lot of time on slow serial console. Currently we reset NMI-watchdog on the

Re: [PATCH v2] perf probe: fix module name matching

Em Sat, Aug 06, 2016 at 07:30:45PM +0900, Masami Hiramatsu escreveu: > On Fri, 05 Aug 2016 15:22:36 +0300 > Konstantin Khlebnikov wrote: > > > If module is "module" then dso->short_name is "[module]". > > Substring comparing is't enough: "raid10" matches to "[raid1]".

[PATCH v3 00/14] pxa_camera transition to v4l2 standalone device

Hi Hans, We're leaving the domain of the RFC to a proper submission. This is very alike to what you reviewed earlier, the code is very close, and : - the split between patches is done to better isolate cleanups from real code - start_streaming() was implemented - your remarks have been taken

Re: [PATCH v2] perf probe: fix module name matching

Em Sat, Aug 06, 2016 at 07:30:45PM +0900, Masami Hiramatsu escreveu: > On Fri, 05 Aug 2016 15:22:36 +0300 > Konstantin Khlebnikov wrote: > > > If module is "module" then dso->short_name is "[module]". > > Substring comparing is't enough: "raid10" matches to "[raid1]". > > This patch also checks

[PATCH v3 00/14] pxa_camera transition to v4l2 standalone device

Hi Hans, We're leaving the domain of the RFC to a proper submission. This is very alike to what you reviewed earlier, the code is very close, and : - the split between patches is done to better isolate cleanups from real code - start_streaming() was implemented - your remarks have been taken

Re: [PATCH] perf probe: fix module name matching

Em Fri, Aug 05, 2016 at 09:17:29PM +0900, Masami Hiramatsu escreveu: > On Fri, 05 Aug 2016 12:41:03 +0300 > Konstantin Khlebnikov wrote: > > > If module is "module" then dso->short_name is "[module]". > > Substring comparing is't enough: "raid10" matches to "[raid1]".

[PATCH 4.6 47/96] pinctrl: imx: Do not treat a PIN without MUX register as an error

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Shiyan commit ba562d5e54fd3136bfea0457add3675850247774 upstream. Some PINs do not have a MUX register, it is not an error. It is necessary to allow the continuation

[PATCH 4.6 08/96] mm, sl[au]b: add __GFP_ATOMIC to the GFP reclaim mask

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Mel Gorman commit e838a45f9392a5bd2be1cd3ab0b16ae85857461c upstream. Commit d0164adc89f6 ("mm, page_alloc: distinguish between being unable to sleep, unwilling to

[PATCH v3 04/14] media: mt9m111: move mt9m111 out of soc_camera

As the mt9m111 is now working as a standalone v4l2 subdevice sensor, move it out of soc_camera directory and severe its dependency on soc_camera. Signed-off-by: Robert Jarzmik --- drivers/media/i2c/Kconfig |7 + drivers/media/i2c/Makefile |

[PATCH 4.6 06/96] dmaengine: at_xdmac: fix residue corruption

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Ludovic Desroches commit 53398f488821c2b5b15291e3debec6ad33f75d3d upstream. An unexpected value of CUBC can lead to a corrupted residue. A more complex sequence is

Re: [PATCH] perf probe: fix module name matching

Em Fri, Aug 05, 2016 at 09:17:29PM +0900, Masami Hiramatsu escreveu: > On Fri, 05 Aug 2016 12:41:03 +0300 > Konstantin Khlebnikov wrote: > > > If module is "module" then dso->short_name is "[module]". > > Substring comparing is't enough: "raid10" matches to "[raid1]". > > This patch also checks

[PATCH 4.6 47/96] pinctrl: imx: Do not treat a PIN without MUX register as an error

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Shiyan commit ba562d5e54fd3136bfea0457add3675850247774 upstream. Some PINs do not have a MUX register, it is not an error. It is necessary to allow the continuation of the PINs

[PATCH 4.6 08/96] mm, sl[au]b: add __GFP_ATOMIC to the GFP reclaim mask

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Mel Gorman commit e838a45f9392a5bd2be1cd3ab0b16ae85857461c upstream. Commit d0164adc89f6 ("mm, page_alloc: distinguish between being unable to sleep, unwilling to sleep and avoiding waking

[PATCH v3 04/14] media: mt9m111: move mt9m111 out of soc_camera

As the mt9m111 is now working as a standalone v4l2 subdevice sensor, move it out of soc_camera directory and severe its dependency on soc_camera. Signed-off-by: Robert Jarzmik --- drivers/media/i2c/Kconfig |7 + drivers/media/i2c/Makefile |1 +

[PATCH 4.6 06/96] dmaengine: at_xdmac: fix residue corruption

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Ludovic Desroches commit 53398f488821c2b5b15291e3debec6ad33f75d3d upstream. An unexpected value of CUBC can lead to a corrupted residue. A more complex sequence is needed to detect an

[PATCH 4.6 00/96] 4.6.6-stable review

This is the start of the stable review cycle for the 4.6.6 release. There are 96 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 Wed Aug 10 18:02:27 UTC 2016. Anything

[PATCH v3 01/14] media: mt9m111: make a standalone v4l2 subdevice

Remove the soc_camera adherence. Mostly the change removes the power manipulation provided by soc_camera, and instead : - powers on the sensor when the s_power control is activated - powers on the sensor in initial probe - enables and disables the MCLK provided to it in power on/off

Re: [PATCH v2] libnvdimm, nd_blk: mask off reserved status bits

On Mon, Aug 8, 2016 at 12:10 PM, Ross Zwisler wrote: > On Tue, Aug 02, 2016 at 12:26:53PM -0600, Ross Zwisler wrote: >> The "NVDIMM Block Window Driver Writer's Guide": >> >> http://pmem.io/documents/ >>

Re: [PATCH v2] libnvdimm, nd_blk: mask off reserved status bits

On Mon, Aug 8, 2016 at 12:10 PM, Ross Zwisler wrote: > On Tue, Aug 02, 2016 at 12:26:53PM -0600, Ross Zwisler wrote: >> The "NVDIMM Block Window Driver Writer's Guide": >> >> http://pmem.io/documents/ >> http://pmem.io/documents/NVDIMM_DriverWritersGuide-July-2016.pdf >> >> defines the layout of

[PATCH 4.6 00/96] 4.6.6-stable review

This is the start of the stable review cycle for the 4.6.6 release. There are 96 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 Wed Aug 10 18:02:27 UTC 2016. Anything

[PATCH v3 01/14] media: mt9m111: make a standalone v4l2 subdevice

Remove the soc_camera adherence. Mostly the change removes the power manipulation provided by soc_camera, and instead : - powers on the sensor when the s_power control is activated - powers on the sensor in initial probe - enables and disables the MCLK provided to it in power on/off

Re: perf test BPF failing on f24: fix

Em Sat, Aug 06, 2016 at 07:29:48PM +0900, Masami Hiramatsu escreveu: > On Fri, 5 Aug 2016 11:35:32 -0300 > Arnaldo Carvalho de Melo wrote: > > > Em Fri, Aug 05, 2016 at 06:45:50PM +0900, Masami Hiramatsu escreveu: > > > On Thu, 4 Aug 2016 18:47:24 -0300 > > > Arnaldo Carvalho de

[PATCH 4.6 37/96] Input: elantech - add more IC body types to the list

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Torokhov commit 226ba707744a51acb4244724e09caacb1d96aed9 upstream. The touchpad in HP Pavilion 14-ab057ca reports it's version as 12 and according to Elan

[PATCH 4.6 37/96] Input: elantech - add more IC body types to the list

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Torokhov commit 226ba707744a51acb4244724e09caacb1d96aed9 upstream. The touchpad in HP Pavilion 14-ab057ca reports it's version as 12 and according to Elan both 11 and 12 are valid IC

Re: perf test BPF failing on f24: fix

Em Sat, Aug 06, 2016 at 07:29:48PM +0900, Masami Hiramatsu escreveu: > On Fri, 5 Aug 2016 11:35:32 -0300 > Arnaldo Carvalho de Melo wrote: > > > Em Fri, Aug 05, 2016 at 06:45:50PM +0900, Masami Hiramatsu escreveu: > > > On Thu, 4 Aug 2016 18:47:24 -0300 > > > Arnaldo Carvalho de Melo wrote: > >

[PATCH v3 03/14] media: mt9m111: use only the SRGB colorspace

mt9m111 being a camera sensor, its colorspace should always be SRGB, for both RGB based formats or YCbCr based ones. Signed-off-by: Robert Jarzmik --- drivers/media/i2c/soc_camera/mt9m111.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git

[PATCH v3 08/14] media: platform: pxa_camera: make printk consistent

Make all print consistent by always using : - dev_xxx(pcdev_to_dev(pcdev), ) This prepares the soc_camera adherence removal by making these call rely on only pcdev, and not the soc_camera icd structure. Signed-off-by: Robert Jarzmik ---

<    1   2   3   4   5   6   7   8   9   10   >