[PATCH 1/3] spi: allow attaching device properties to SPI board info

Generic device properties support statically defined property sets. For them to be usable, we need to attach these property sets before devices are registered and probed. Allowing to attach property list to spi_board_info structure will allow non-ACPI non-DT boards switch to using generic

[PATCH 1/3] spi: allow attaching device properties to SPI board info

Generic device properties support statically defined property sets. For them to be usable, we need to attach these property sets before devices are registered and probed. Allowing to attach property list to spi_board_info structure will allow non-ACPI non-DT boards switch to using generic

[PATCH 3/3] spi: allow registering empty spi_board_info lists

Many boards form list of spi_board_info entries depending on config, and it is possible to end up with empty list. Do not report error in such cases. Signed-off-by: Dmitry Torokhov --- drivers/spi/spi.c | 3 --- 1 file changed, 3 deletions(-) diff --git

[PATCH 3/3] spi: allow registering empty spi_board_info lists

Many boards form list of spi_board_info entries depending on config, and it is possible to end up with empty list. Do not report error in such cases. Signed-off-by: Dmitry Torokhov --- drivers/spi/spi.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/drivers/spi/spi.c b/drivers/spi/spi.c

Re: [PATCH 2/3] spi: allocate spi_board_info entries one by one

On Mon, Feb 27, 2017 at 08:08:47PM -0800, Dmitry Torokhov wrote: > Lists of spi_board_info entries registered with spi_register_board_info() > can be quite long; instead of forcing memory allocator find contagious > chunk of memory, let;s allocate them one-by-one, so they can be packed as >

Re: [PATCH 2/3] spi: allocate spi_board_info entries one by one

On Mon, Feb 27, 2017 at 08:08:47PM -0800, Dmitry Torokhov wrote: > Lists of spi_board_info entries registered with spi_register_board_info() > can be quite long; instead of forcing memory allocator find contagious > chunk of memory, let;s allocate them one-by-one, so they can be packed as >

Re: [PATCH] jump_label: align jump_entry table to at least 4-bytes

On 02/27/2017 02:36 PM, Steven Rostedt wrote: On Mon, 27 Feb 2017 14:21:21 -0800 David Daney wrote: See attached for mips. It seems to do the right thing. I leave it as an exercise to the reader to fix the other architectures. Consult your own binutils experts

Re: [PATCH] jump_label: align jump_entry table to at least 4-bytes

On 02/27/2017 02:36 PM, Steven Rostedt wrote: On Mon, 27 Feb 2017 14:21:21 -0800 David Daney wrote: See attached for mips. It seems to do the right thing. I leave it as an exercise to the reader to fix the other architectures. Consult your own binutils experts to verify that what I say is

[locking/ww_mutex] f2a5fec173 EIP: __mutex_trylock

/scm/linux/kernel/git/groeck/linux-staging # extra tests on tree/branch linux-next/master git bisect bad ed7b11e565c736828f0b793f596a4ca20efee747 # 19:06 8- 13 Add linux-next specific files for 20170227 --- 0-DAY kernel test infrastructureOpen Source Technology Center https://lists.01.or

[locking/ww_mutex] f2a5fec173 EIP: __mutex_trylock

linux-next/master git bisect bad ed7b11e565c736828f0b793f596a4ca20efee747 # 19:06 8- 13 Add linux-next specific files for 20170227 --- 0-DAY kernel test infrastructureOpen Source Technology Center https://lists.01.org/pipermail/lkp Intel Corpo

Re: [PATCH 2/8] watchdog: s3c2410: Fix infinite interrupt in soft mode

On Fri, Feb 24, 2017 at 05:11:16PM +0200, Krzysztof Kozlowski wrote: > In soft (no-reboot) mode, the driver self-pings watchdog upon expiration > of an interrupt. However the interrupt itself was not cleared thus on > first hit, the system enters infinite interrupt handling loop. > > On Odroid

Re: [PATCH 2/8] watchdog: s3c2410: Fix infinite interrupt in soft mode

On Fri, Feb 24, 2017 at 05:11:16PM +0200, Krzysztof Kozlowski wrote: > In soft (no-reboot) mode, the driver self-pings watchdog upon expiration > of an interrupt. However the interrupt itself was not cleared thus on > first hit, the system enters infinite interrupt handling loop. > > On Odroid

[PATCH 00/10] Drivers: hv: vmbus: Miscellaneous fixes

From: K. Y. Srinivasan Miscellaneous fixes. Stephen Hemminger (10): vmbus: only reschedule tasklet if time limit exceeded vmbus: use rcu for per-cpu channel list hyperv: fix warning about missing prototype vmbus: remove useless return's vmbus: remove unnecessary

[PATCH 00/10] Drivers: hv: vmbus: Miscellaneous fixes

From: K. Y. Srinivasan Miscellaneous fixes. Stephen Hemminger (10): vmbus: only reschedule tasklet if time limit exceeded vmbus: use rcu for per-cpu channel list hyperv: fix warning about missing prototype vmbus: remove useless return's vmbus: remove unnecessary initialization

[PATCH 1/2 v4] pci-hyperv: properly handle pci bus remove

hv_pci_devices_present is called in hv_pci_remove when we remove a PCI device from host (e.g. by disabling SRIOV on a device). In hv_pci_remove, the bus is already removed before the call, so we don't need to rescan the bus in the workqueue scheduled from hv_pci_devices_present. By introducing

[PATCH 2/2 v4] pci-hyperv: lock pci bus on device eject

A PCI_EJECT message can arrive at the same time we are calling pci_scan_child_bus in the workqueue for the previous PCI_BUS_RELATIONS message or in create_root_hv_pci_bus(), in this case we could potentially modify the bus from multiple places. Properly lock the bus access. Thanks Dexuan Cui

[PATCH 1/2 v4] pci-hyperv: properly handle pci bus remove

hv_pci_devices_present is called in hv_pci_remove when we remove a PCI device from host (e.g. by disabling SRIOV on a device). In hv_pci_remove, the bus is already removed before the call, so we don't need to rescan the bus in the workqueue scheduled from hv_pci_devices_present. By introducing

[PATCH 2/2 v4] pci-hyperv: lock pci bus on device eject

A PCI_EJECT message can arrive at the same time we are calling pci_scan_child_bus in the workqueue for the previous PCI_BUS_RELATIONS message or in create_root_hv_pci_bus(), in this case we could potentially modify the bus from multiple places. Properly lock the bus access. Thanks Dexuan Cui

[git pull] drm fixes for v4.11-rc1

This is a selection of fixes for recent bugs, the vmwgfx one is important to avoid a regression, and compat ioctl one is pretty urgent for stable. Otherwise nothing too much. I've got a separate pull req for some AST hw IBM need to enable. Dave. The following changes since commit

[git pull] drm fixes for v4.11-rc1

This is a selection of fixes for recent bugs, the vmwgfx one is important to avoid a regression, and compat ioctl one is pretty urgent for stable. Otherwise nothing too much. I've got a separate pull req for some AST hw IBM need to enable. Dave. The following changes since commit

[git pull] drm ast support for ast 2500 hardware

This is a set of changes to enable the AST2500 BMC hardware, and also fix some bugs interacting with the older AST hardware. Some of the bug fixes are cc'ed to stable. Dave. The following changes since commit 45554b2357d5782497e59f09146cc3636d6ad551: Merge tag 'trace-v4.11-2' of

[git pull] drm ast support for ast 2500 hardware

This is a set of changes to enable the AST2500 BMC hardware, and also fix some bugs interacting with the older AST hardware. Some of the bug fixes are cc'ed to stable. Dave. The following changes since commit 45554b2357d5782497e59f09146cc3636d6ad551: Merge tag 'trace-v4.11-2' of

Re: [f2fs-dev] [PATCH 2/3 v2] f2fs: add bitmaps for empty or full NAT blocks

On 2017/2/24 6:58, Jaegeuk Kim wrote: > @@ -2326,7 +2431,8 @@ void flush_nat_entries(struct f2fs_sb_info *sbi) >* entries, remove all entries from journal and merge them >* into nat entry set. >*/ > - if (!__has_cursum_space(journal, nm_i->dirty_nat_cnt, NAT_JOURNAL)) >

Re: [f2fs-dev] [PATCH 2/3 v2] f2fs: add bitmaps for empty or full NAT blocks

On 2017/2/24 6:58, Jaegeuk Kim wrote: > @@ -2326,7 +2431,8 @@ void flush_nat_entries(struct f2fs_sb_info *sbi) >* entries, remove all entries from journal and merge them >* into nat entry set. >*/ > - if (!__has_cursum_space(journal, nm_i->dirty_nat_cnt, NAT_JOURNAL)) >

Re: [PATCH V5 3/6] mm: move MADV_FREE pages into LRU_INACTIVE_FILE list

Hi, On Mon, Feb 27, 2017 at 08:13:10AM -0800, Shaohua Li wrote: > On Mon, Feb 27, 2017 at 03:28:01PM +0900, Minchan Kim wrote: > > Hello Shaohua, > > > > On Fri, Feb 24, 2017 at 01:31:46PM -0800, Shaohua Li wrote: > > > madv MADV_FREE indicate pages are 'lazyfree'. They are still anonymous > > >

Re: [PATCH V5 3/6] mm: move MADV_FREE pages into LRU_INACTIVE_FILE list

Hi, On Mon, Feb 27, 2017 at 08:13:10AM -0800, Shaohua Li wrote: > On Mon, Feb 27, 2017 at 03:28:01PM +0900, Minchan Kim wrote: > > Hello Shaohua, > > > > On Fri, Feb 24, 2017 at 01:31:46PM -0800, Shaohua Li wrote: > > > madv MADV_FREE indicate pages are 'lazyfree'. They are still anonymous > > >

Ext4 new shutdown ioctl fails generic/04{4,5,6}

Hi, On latest Linus tree, xfstests generic/04{4,5,6} fails. FSTYP -- ext4 PLATFORM -- Linux/x86_64 rhel73 4.10.0-master-45554b2+ MKFS_OPTIONS -- /dev/sdc MOUNT_OPTIONS -- -o acl,user_xattr -o context=system_u:object_r:nfs_t:s0 /dev/sdc /test2 generic/045 - output mismatch

Re: [PATCH V2] vhost: introduce O(1) vq metadata cache

On 2017年02月28日 02:35, Michael S. Tsirkin wrote: On Wed, Feb 15, 2017 at 01:37:17PM +0800, Jason Wang wrote: On 2016年12月14日 17:53, Jason Wang wrote: When device IOTLB is enabled, all address translations were stored in interval tree. O(lgN) searching time could be slow for virtqueue metadata

Ext4 new shutdown ioctl fails generic/04{4,5,6}

Hi, On latest Linus tree, xfstests generic/04{4,5,6} fails. FSTYP -- ext4 PLATFORM -- Linux/x86_64 rhel73 4.10.0-master-45554b2+ MKFS_OPTIONS -- /dev/sdc MOUNT_OPTIONS -- -o acl,user_xattr -o context=system_u:object_r:nfs_t:s0 /dev/sdc /test2 generic/045 - output mismatch

Re: [PATCH V2] vhost: introduce O(1) vq metadata cache

On 2017年02月28日 02:35, Michael S. Tsirkin wrote: On Wed, Feb 15, 2017 at 01:37:17PM +0800, Jason Wang wrote: On 2016年12月14日 17:53, Jason Wang wrote: When device IOTLB is enabled, all address translations were stored in interval tree. O(lgN) searching time could be slow for virtqueue metadata

linux-next: Tree for Feb 28

Hi all, Please do not add any material intended for v4.12 to your linux-next included branches until after v4.11-rc1 has been released. Changes since 20170227: The vfs tree still had its build failure for which I added a fix patch. The scsi tree lost its build failure. Non-merge commits

linux-next: Tree for Feb 28

Hi all, Please do not add any material intended for v4.12 to your linux-next included branches until after v4.11-rc1 has been released. Changes since 20170227: The vfs tree still had its build failure for which I added a fix patch. The scsi tree lost its build failure. Non-merge commits

Re: [PATCH V5 6/6] proc: show MADV_FREE pages info in smaps

On February 25, 2017 5:32 AM Shaohua Li wrote: > > show MADV_FREE pages info of each vma in smaps. The interface is for > diganose or monitoring purpose, userspace could use it to understand > what happens in the application. Since userspace could dirty MADV_FREE > pages without notice from

Re: [PATCH V5 6/6] proc: show MADV_FREE pages info in smaps

On February 25, 2017 5:32 AM Shaohua Li wrote: > > show MADV_FREE pages info of each vma in smaps. The interface is for > diganose or monitoring purpose, userspace could use it to understand > what happens in the application. Since userspace could dirty MADV_FREE > pages without notice from

Re: [PATCH V5 5/6] mm: enable MADV_FREE for swapless system

On February 25, 2017 5:32 AM Shaohua Li wrote: > > Now MADV_FREE pages can be easily reclaimed even for swapless system. We > can safely enable MADV_FREE for all systems. > > Cc: Michal Hocko > Cc: Minchan Kim > Cc: Hugh Dickins > Cc:

Re: [PATCH V5 5/6] mm: enable MADV_FREE for swapless system

On February 25, 2017 5:32 AM Shaohua Li wrote: > > Now MADV_FREE pages can be easily reclaimed even for swapless system. We > can safely enable MADV_FREE for all systems. > > Cc: Michal Hocko > Cc: Minchan Kim > Cc: Hugh Dickins > Cc: Rik van Riel > Cc: Mel Gorman > Cc: Andrew Morton >

Re: [PATCH V5 3/6] mm: move MADV_FREE pages into LRU_INACTIVE_FILE list

On February 25, 2017 5:32 AM Shaohua Li wrote: > > madv MADV_FREE indicate pages are 'lazyfree'. They are still anonymous > pages, but they can be freed without pageout. To destinguish them > against normal anonymous pages, we clear their SwapBacked flag. > > MADV_FREE pages could be freed

Re: [PATCH V5 3/6] mm: move MADV_FREE pages into LRU_INACTIVE_FILE list

On February 25, 2017 5:32 AM Shaohua Li wrote: > > madv MADV_FREE indicate pages are 'lazyfree'. They are still anonymous > pages, but they can be freed without pageout. To destinguish them > against normal anonymous pages, we clear their SwapBacked flag. > > MADV_FREE pages could be freed

Re: [PATCH] scsi: aacraid: remove redundant zero check on ret

> "Colin" == Colin King writes: Colin, Colin> The check for ret being zero is redundant as a few statements Colin> earlier we break out of the while loop if ret is non-zero. Thus Colin> we can remove the zero check and also the dead-code non-zero case Colin> too.

Re: [PATCH] scsi: aacraid: remove redundant zero check on ret

> "Colin" == Colin King writes: Colin, Colin> The check for ret being zero is redundant as a few statements Colin> earlier we break out of the while loop if ret is non-zero. Thus Colin> we can remove the zero check and also the dead-code non-zero case Colin> too. Applied to

Re: [PATCH] sd: close hole in > 2T device rejection when !CONFIG_LBDAF

> "Bart" == Bart Van Assche writes: Bart, Bart> Sorry but I still don't understand why the two checks are Bart> different. How about the (untested) patch below? The approach Bart> below avoids that the check is duplicated and - at least in my Bart> opinion -

Re: [Regression?] 1ea0ce4069 ("selinux: allow changing labels for cgroupfs") stops Android from booting

On Mon, Feb 27, 2017 at 4:23 PM, Stephen Smalley wrote: > On Mon, 2017-02-27 at 12:48 -0800, Nick Kralevich wrote: >> On Mon, Feb 27, 2017 at 11:53 AM, Stephen Smalley >> wrote: >> > >> > > >> > > I can reproduce it on angler (with a back-port of just that

Re: [PATCH] sd: close hole in > 2T device rejection when !CONFIG_LBDAF

> "Bart" == Bart Van Assche writes: Bart, Bart> Sorry but I still don't understand why the two checks are Bart> different. How about the (untested) patch below? The approach Bart> below avoids that the check is duplicated and - at least in my Bart> opinion - results in code that is easier

Re: [Regression?] 1ea0ce4069 ("selinux: allow changing labels for cgroupfs") stops Android from booting

On Mon, Feb 27, 2017 at 4:23 PM, Stephen Smalley wrote: > On Mon, 2017-02-27 at 12:48 -0800, Nick Kralevich wrote: >> On Mon, Feb 27, 2017 at 11:53 AM, Stephen Smalley >> wrote: >> > >> > > >> > > I can reproduce it on angler (with a back-port of just that >> > > patch), >> > > although I am

Re: [PATCH V5 4/6] mm: reclaim MADV_FREE pages

On February 25, 2017 5:32 AM Shaohua Li wrote: > > When memory pressure is high, we free MADV_FREE pages. If the pages are > not dirty in pte, the pages could be freed immediately. Otherwise we > can't reclaim them. We put the pages back to anonumous LRU list (by > setting SwapBacked flag) and

Re: [PATCH V5 4/6] mm: reclaim MADV_FREE pages

On February 25, 2017 5:32 AM Shaohua Li wrote: > > When memory pressure is high, we free MADV_FREE pages. If the pages are > not dirty in pte, the pages could be freed immediately. Otherwise we > can't reclaim them. We put the pages back to anonumous LRU list (by > setting SwapBacked flag) and

Re: [PATCH] jump_label: align jump_entry table to at least 4-bytes

On 02/27/2017 02:50 PM, Jason Baron wrote: On 02/27/2017 05:45 PM, David Daney wrote: On 02/27/2017 02:36 PM, Steven Rostedt wrote: On Mon, 27 Feb 2017 14:21:21 -0800 David Daney wrote: See attached for mips. It seems to do the right thing. I leave it as an

Re: [PATCH] jump_label: align jump_entry table to at least 4-bytes

On 02/27/2017 02:50 PM, Jason Baron wrote: On 02/27/2017 05:45 PM, David Daney wrote: On 02/27/2017 02:36 PM, Steven Rostedt wrote: On Mon, 27 Feb 2017 14:21:21 -0800 David Daney wrote: See attached for mips. It seems to do the right thing. I leave it as an exercise to the reader to fix

[mm/kasan] 80a9201a59 BUG: kernel reboot-without-warning in early-boot stage, last printk: Booting the kernel.

ra tests on tree/branch linux-next/master git bisect bad ed7b11e565c736828f0b793f596a4ca20efee747 # 15:40 0- 3 Add linux-next specific files for 20170227 --- 0-DAY kernel test infrastructureOpen Source Technology Center https://lists.01.org/pipermail/lkp

[mm/kasan] 80a9201a59 BUG: kernel reboot-without-warning in early-boot stage, last printk: Booting the kernel.

ster git bisect bad ed7b11e565c736828f0b793f596a4ca20efee747 # 15:40 0- 3 Add linux-next specific files for 20170227 --- 0-DAY kernel test infrastructureOpen Source Technology Center https://lists.01.org/pipermail/lkp Intel Corporation dmesg-yocto-intel12-44:20170227142414:

[PATCH] arm: exynos increase CONFIG_CMA_SIZE_MBYTES to 96

Current CMA size of 64 Mbytes is right on the edge of being too small for some display managers. With the proposed s5p_mfc patch series that pre-allocate buffers, when display manager starts, it fails to get GEM buffers. Increasing the CMA size to 96 solves the problem. Change

[PATCH] arm: exynos increase CONFIG_CMA_SIZE_MBYTES to 96

Current CMA size of 64 Mbytes is right on the edge of being too small for some display managers. With the proposed s5p_mfc patch series that pre-allocate buffers, when display manager starts, it fails to get GEM buffers. Increasing the CMA size to 96 solves the problem. Change

Re: [PATCH] scsi: lpfc: use proper format string for dma_addr_t

> "Arnd" == Arnd Bergmann writes: Arnd> dma_addr_t may be either u32 or u64, depending on the kernel Arnd> configuration, and we get a warning for the 32-bit case: Applied to 4.11/scsi-fixes. -- Martin K. Petersen Oracle Linux Engineering

Re: [PATCH] scsi: lpfc: use div_u64 for 64-bit division

> "Arnd" == Arnd Bergmann writes: Arnd> The new debugfs output causes a link error on 32-bit Arnd> architectures: ERROR: "__aeabi_uldivmod" Arnd> [drivers/scsi/lpfc/lpfc.ko] undefined! Arnd> This code is not performance critical, so we can simply use Arnd> div_u64(). Applied

Re: [PATCH] scsi: lpfc: use proper format string for dma_addr_t

> "Arnd" == Arnd Bergmann writes: Arnd> dma_addr_t may be either u32 or u64, depending on the kernel Arnd> configuration, and we get a warning for the 32-bit case: Applied to 4.11/scsi-fixes. -- Martin K. Petersen Oracle Linux Engineering

Re: [PATCH] scsi: lpfc: use div_u64 for 64-bit division

> "Arnd" == Arnd Bergmann writes: Arnd> The new debugfs output causes a link error on 32-bit Arnd> architectures: ERROR: "__aeabi_uldivmod" Arnd> [drivers/scsi/lpfc/lpfc.ko] undefined! Arnd> This code is not performance critical, so we can simply use Arnd> div_u64(). Applied to

[PATCH 03/10] hyperv: fix warning about missing prototype

From: Stephen Hemminger Compiling with warnings enabled finds missing prototype for hv_do_hypercall. Signed-off-by: Stephen Hemminger Signed-off-by: K. Y. Srinivasan --- arch/x86/hyperv/hv_init.c |2 +- 1 files

[PATCH 04/10] vmbus: remove useless return's

From: Stephen Hemminger No need for empty return at end of void function Signed-off-by: Stephen Hemminger Signed-off-by: K. Y. Srinivasan --- drivers/hv/hv_balloon.c |2 -- drivers/hv/hv_fcopy.c|2 --

[PATCH 03/10] hyperv: fix warning about missing prototype

From: Stephen Hemminger Compiling with warnings enabled finds missing prototype for hv_do_hypercall. Signed-off-by: Stephen Hemminger Signed-off-by: K. Y. Srinivasan --- arch/x86/hyperv/hv_init.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git

[PATCH 04/10] vmbus: remove useless return's

From: Stephen Hemminger No need for empty return at end of void function Signed-off-by: Stephen Hemminger Signed-off-by: K. Y. Srinivasan --- drivers/hv/hv_balloon.c |2 -- drivers/hv/hv_fcopy.c|2 -- drivers/hv/hv_kvp.c |2 -- drivers/hv/hv_snapshot.c |2 --

[PATCH 08/10] vmbus: make channel_message table constant

From: Stephen Hemminger This table is immutable and should be const. Cleanup indentation and whitespace for this as well. Signed-off-by: Stephen Hemminger Signed-off-by: K. Y. Srinivasan --- drivers/hv/channel_mgmt.c |

[PATCH 08/10] vmbus: make channel_message table constant

From: Stephen Hemminger This table is immutable and should be const. Cleanup indentation and whitespace for this as well. Signed-off-by: Stephen Hemminger Signed-off-by: K. Y. Srinivasan --- drivers/hv/channel_mgmt.c | 48 ++--

[PATCH 06/10] vmbus: fix spelling errors

From: Stephen Hemminger Several spelling errors in comments Signed-off-by: Stephen Hemminger Signed-off-by: K. Y. Srinivasan --- drivers/hv/channel.c | 10 +- drivers/hv/hv_kvp.c | 10 +- 2 files

[PATCH 05/10] vmbus: remove unnecessary initialization

From: Stephen Hemminger Don't initialize variables that are then set a few lines later. Signed-off-by: Stephen Hemminger Signed-off-by: K. Y. Srinivasan --- drivers/hv/ring_buffer.c | 13 + 1 files changed,

[PATCH 06/10] vmbus: fix spelling errors

From: Stephen Hemminger Several spelling errors in comments Signed-off-by: Stephen Hemminger Signed-off-by: K. Y. Srinivasan --- drivers/hv/channel.c | 10 +- drivers/hv/hv_kvp.c | 10 +- 2 files changed, 10 insertions(+), 10 deletions(-) diff --git

[PATCH 05/10] vmbus: remove unnecessary initialization

From: Stephen Hemminger Don't initialize variables that are then set a few lines later. Signed-off-by: Stephen Hemminger Signed-off-by: K. Y. Srinivasan --- drivers/hv/ring_buffer.c | 13 + 1 files changed, 5 insertions(+), 8 deletions(-) diff --git a/drivers/hv/ring_buffer.c

Re: [PATCH] target/user: Add daynmic growing data area feature support

On 02/22/2017 02:32 PM, Andy Grover wrote: > On 02/17/2017 01:24 AM, lixi...@cmss.chinamobile.com wrote: >> > From: Xiubo Li >> > >> > Currently for the TCMU, the ring buffer size is fixed to 64K cmd >> > area + 1M data area, and this will be bottlenecks for high

[PATCH v5 4/5] staging: ks7010: fix coding style issue of using __func__ instead of __FUNCTION__

This patch fixes coding style issue of using __func__ instead of gcc specific __FUNCTION__, warning as issued by checkpatch Signed-off-by: Chetan Sethi --- v2: - split multiple changes across different patches v3: - mentioned patch revision in subject v4: - modified

Re: [PATCH] target/user: Add daynmic growing data area feature support

On 02/22/2017 02:32 PM, Andy Grover wrote: > On 02/17/2017 01:24 AM, lixi...@cmss.chinamobile.com wrote: >> > From: Xiubo Li >> > >> > Currently for the TCMU, the ring buffer size is fixed to 64K cmd >> > area + 1M data area, and this will be bottlenecks for high iops. > Hi Xiubo, thanks for

[PATCH v5 4/5] staging: ks7010: fix coding style issue of using __func__ instead of __FUNCTION__

This patch fixes coding style issue of using __func__ instead of gcc specific __FUNCTION__, warning as issued by checkpatch Signed-off-by: Chetan Sethi --- v2: - split multiple changes across different patches v3: - mentioned patch revision in subject v4: - modified description to exclude

[PATCH 02/10] vmbus: use rcu for per-cpu channel list

From: Stephen Hemminger The per-cpu channel list is now referred to in the interrupt routine. This is mostly safe since the host will not normally generate an interrupt when channel is being deleted but if it did then there would be a use after free problem. To

[PATCH 01/10] vmbus: only reschedule tasklet if time limit exceeded

From: Stephen Hemminger The change to reschedule tasklet if more data arrives in ring buffer can cause performance regression if host timing is such that the next response happens in small window. Go back to a modified version of the original looping behavior. If the

[PATCH 10/10] vmbus: expose debug info for drivers

From: Stephen Hemminger Allow driver to get debug information about state of the ring. Signed-off-by: Stephen Hemminger Signed-off-by: K. Y. Srinivasan --- drivers/hv/hyperv_vmbus.h | 11 ---

[PATCH 07/10] hyperv: remove unnecessary return variable

From: Stephen Hemminger hv_ringbuffer_read cleanup. Signed-off-by: Stephen Hemminger Signed-off-by: K. Y. Srinivasan --- drivers/hv/ring_buffer.c |6 ++ 1 files changed, 2 insertions(+), 4 deletions(-) diff

[PATCH 01/10] vmbus: only reschedule tasklet if time limit exceeded

From: Stephen Hemminger The change to reschedule tasklet if more data arrives in ring buffer can cause performance regression if host timing is such that the next response happens in small window. Go back to a modified version of the original looping behavior. If the race occurs in a small

[PATCH 10/10] vmbus: expose debug info for drivers

From: Stephen Hemminger Allow driver to get debug information about state of the ring. Signed-off-by: Stephen Hemminger Signed-off-by: K. Y. Srinivasan --- drivers/hv/hyperv_vmbus.h | 11 --- drivers/hv/ring_buffer.c |1 + include/linux/hyperv.h| 17 + 3

[PATCH 07/10] hyperv: remove unnecessary return variable

From: Stephen Hemminger hv_ringbuffer_read cleanup. Signed-off-by: Stephen Hemminger Signed-off-by: K. Y. Srinivasan --- drivers/hv/ring_buffer.c |6 ++ 1 files changed, 2 insertions(+), 4 deletions(-) diff --git a/drivers/hv/ring_buffer.c b/drivers/hv/ring_buffer.c index

[PATCH 02/10] vmbus: use rcu for per-cpu channel list

From: Stephen Hemminger The per-cpu channel list is now referred to in the interrupt routine. This is mostly safe since the host will not normally generate an interrupt when channel is being deleted but if it did then there would be a use after free problem. To solve, this use RCU protection on

[PATCH 09/10] vmbus: cleanup header file style

From: Stephen Hemminger Minor changes to align hyper-v vmbus include files with current linux kernel style. Signed-off-by: Stephen Hemminger Signed-off-by: K. Y. Srinivasan --- drivers/hv/hyperv_vmbus.h | 16

[PATCH 09/10] vmbus: cleanup header file style

From: Stephen Hemminger Minor changes to align hyper-v vmbus include files with current linux kernel style. Signed-off-by: Stephen Hemminger Signed-off-by: K. Y. Srinivasan --- drivers/hv/hyperv_vmbus.h | 16 include/linux/hyperv.h| 12 ++-- 2 files changed,

[PATCH v5 2/5] staging: ks7010: fix coding style issue of enclosing complex macro value in parentheses

This patch fixes error of enclosing complex macro value in parentheses, error as issued by checkpatch Signed-off-by: Chetan Sethi --- v2: - split multiple changes across different patches v3: - mentioned patch revision in subject - incorporated review comment of correct

[PATCH v5 2/5] staging: ks7010: fix coding style issue of enclosing complex macro value in parentheses

This patch fixes error of enclosing complex macro value in parentheses, error as issued by checkpatch Signed-off-by: Chetan Sethi --- v2: - split multiple changes across different patches v3: - mentioned patch revision in subject - incorporated review comment of correct indentation for do

Re: [PATCH v7 7/8] uapi: export all headers under uapi directories

On Mon, Feb 27, 2017 at 05:01:55PM +0100, Nicolas Dichtel wrote: > Le 24/02/2017 à 17:49, Nicolas Dichtel a écrit : > > 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

[PATCH] mm,fs,dax: mark dax_iomap_pmd_fault as const

The two alternative implementations of dax_iomap_fault have different prototypes, and one of them is obviously wrong as seen from this build warning: fs/dax.c: In function 'dax_iomap_fault': fs/dax.c:1462:35: error: passing argument 2 of 'dax_iomap_pmd_fault' discards 'const' qualifier from

Re: [PATCH v7 7/8] uapi: export all headers under uapi directories

On Mon, Feb 27, 2017 at 05:01:55PM +0100, Nicolas Dichtel wrote: > Le 24/02/2017 à 17:49, Nicolas Dichtel a écrit : > > 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

[PATCH] mm,fs,dax: mark dax_iomap_pmd_fault as const

The two alternative implementations of dax_iomap_fault have different prototypes, and one of them is obviously wrong as seen from this build warning: fs/dax.c: In function 'dax_iomap_fault': fs/dax.c:1462:35: error: passing argument 2 of 'dax_iomap_pmd_fault' discards 'const' qualifier from

[PATCH v5 3/4] iio: accel: adxl345: Split driver into core and I2C

Move I2C-specific code into its own file and rely on regmap to access registers. The core code provides access to x, y, z and scale readings. Signed-off-by: Eva Rachel Retuya Reviewed-by: Andy Shevchenko --- Changes from v4: * Add Andy's

[PATCH v5 3/4] iio: accel: adxl345: Split driver into core and I2C

Move I2C-specific code into its own file and rely on regmap to access registers. The core code provides access to x, y, z and scale readings. Signed-off-by: Eva Rachel Retuya Reviewed-by: Andy Shevchenko --- Changes from v4: * Add Andy's Reviewed-by tag Changes from v3: * Revert to explicit

Re: [PATCH v4 0/4] iio: accel: adxl345: Split driver into core and I2C then add SPI support

On Tue, Feb 28, 2017 at 12:41:50AM +0200, Andy Shevchenko wrote: [...] > I did couple of rounds of review and found no major issues with the > series (though, I would amend some style there and minor things). So, > for moving forward FWIW: > > Reviewed-by: Andy Shevchenko

Re: [PATCH v4 0/4] iio: accel: adxl345: Split driver into core and I2C then add SPI support

On Tue, Feb 28, 2017 at 12:41:50AM +0200, Andy Shevchenko wrote: [...] > I did couple of rounds of review and found no major issues with the > series (though, I would amend some style there and minor things). So, > for moving forward FWIW: > > Reviewed-by: Andy Shevchenko Hello Andy, thank you

[PATCH v5 2/4] iio: accel: adxl345: Use I2C regmap instead of direct I2C access

Convert the driver to use regmap instead of I2C-specific functions. This is done in preparation for splitting this driver into core and I2C-specific code as well as introduction of SPI driver. Signed-off-by: Eva Rachel Retuya Reviewed-by: Andy Shevchenko

[PATCH v5 2/4] iio: accel: adxl345: Use I2C regmap instead of direct I2C access

Convert the driver to use regmap instead of I2C-specific functions. This is done in preparation for splitting this driver into core and I2C-specific code as well as introduction of SPI driver. Signed-off-by: Eva Rachel Retuya Reviewed-by: Andy Shevchenko --- Changes from v4: * Add Andy's

[GIT PULL] Pull request fro 4.11 for IPMI

The following changes since commit c433eb70f37de2514f3ae3d43dd7e4a75493fe48: Merge tag 'pinctrl-v4.10-2' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl (2017-01-05 10:36:56 -0800) are available in the git repository at: git://git.code.sf.net/p/openipmi/linux-ipmi

[PATCH v5 1/4] dt-bindings: iio: accel: Document ADXL345 accelerometer binding

Add the device tree binding documentation for the ADXL345 3-axis digital accelerometer. Signed-off-by: Eva Rachel Retuya --- Changes from v4: * Update subject-prefix * Update node name from "adxl345@unit-address" to "accelerometer@unit-address"

[GIT PULL] Pull request fro 4.11 for IPMI

The following changes since commit c433eb70f37de2514f3ae3d43dd7e4a75493fe48: Merge tag 'pinctrl-v4.10-2' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl (2017-01-05 10:36:56 -0800) are available in the git repository at: git://git.code.sf.net/p/openipmi/linux-ipmi

[PATCH v5 1/4] dt-bindings: iio: accel: Document ADXL345 accelerometer binding

Add the device tree binding documentation for the ADXL345 3-axis digital accelerometer. Signed-off-by: Eva Rachel Retuya --- Changes from v4: * Update subject-prefix * Update node name from "adxl345@unit-address" to "accelerometer@unit-address" .../devicetree/bindings/iio/accel/adxl345.txt

[PATCH v5 0/4] iio: accel: adxl345: Split driver into core and I2C then add SPI support

This patchset modifies the adxl345 to use regmap. In doing so, we can easily introduce SPI support and let regmap handle the rest. Recap of basic features: read_raw for x, y and z axes, scale. After applying this series, driver now supports the SPI protocol and enumeration of device via device

RE: [PATCH] Drivers: hv: util: on deinit, don't wait the release event, if we shouldn't

> From: Stephen Hemminger > Sent: Tuesday, February 28, 2017 01:02 > > The patch looks good. I don't understand the exact semantics here and > therefore have a couple of naïve questions > > Is it possible device could be opened multiple times? Is reference counting > done above? The file can

[PATCH v5 0/4] iio: accel: adxl345: Split driver into core and I2C then add SPI support

This patchset modifies the adxl345 to use regmap. In doing so, we can easily introduce SPI support and let regmap handle the rest. Recap of basic features: read_raw for x, y and z axes, scale. After applying this series, driver now supports the SPI protocol and enumeration of device via device

RE: [PATCH] Drivers: hv: util: on deinit, don't wait the release event, if we shouldn't

> From: Stephen Hemminger > Sent: Tuesday, February 28, 2017 01:02 > > The patch looks good. I don't understand the exact semantics here and > therefore have a couple of naïve questions > > Is it possible device could be opened multiple times? Is reference counting > done above? The file can

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