Re: [PATCH v8 00/14] lockdep: Implement crossrelease feature

On Wed, Aug 16, 2017 at 02:05:06PM +0900, Byungchul Park wrote: > On Wed, Aug 16, 2017 at 12:05:31PM +0800, Boqun Feng wrote: > > > I see... > > > > > > Worker A : acquired of wfc.work -> wait for cpu_hotplug_lock to be > > > released > > > Task B : acquired of cpu_hotplug_lock -> wait for

Re: [PATCH v8 00/14] lockdep: Implement crossrelease feature

On Wed, Aug 16, 2017 at 02:05:06PM +0900, Byungchul Park wrote: > On Wed, Aug 16, 2017 at 12:05:31PM +0800, Boqun Feng wrote: > > > I see... > > > > > > Worker A : acquired of wfc.work -> wait for cpu_hotplug_lock to be > > > released > > > Task B : acquired of cpu_hotplug_lock -> wait for

Re: [virtio-dev] [PATCH v13 0/5] Virtio-balloon Enhancement

On Thu, Aug 03, 2017 at 02:38:14PM +0800, Wei Wang wrote: > This patch series enhances the existing virtio-balloon with the following > new features: > 1) fast ballooning: transfer ballooned pages between the guest and host in > chunks using sgs, instead of one by one; and > 2) free_page_vq: a new

Re: [virtio-dev] [PATCH v13 0/5] Virtio-balloon Enhancement

On Thu, Aug 03, 2017 at 02:38:14PM +0800, Wei Wang wrote: > This patch series enhances the existing virtio-balloon with the following > new features: > 1) fast ballooning: transfer ballooned pages between the guest and host in > chunks using sgs, instead of one by one; and > 2) free_page_vq: a new

Re: [PATCHv3] perf bpf: Fix endianness problem when loading parameters in prologue

On 08/15/2017 05:25 PM, Arnaldo Carvalho de Melo wrote: > Em Tue, Aug 15, 2017 at 11:21:59AM +0200, Thomas Richter escreveu: > > Ok, I'm applying this, the only missing bit was the following line, > right at the start of the patch message body; > > From: Wang Nan > > To

Re: [PATCHv3] perf bpf: Fix endianness problem when loading parameters in prologue

On 08/15/2017 05:25 PM, Arnaldo Carvalho de Melo wrote: > Em Tue, Aug 15, 2017 at 11:21:59AM +0200, Thomas Richter escreveu: > > Ok, I'm applying this, the only missing bit was the following line, > right at the start of the patch message body; > > From: Wang Nan > > To state that the patch

Re: [PATCH v4 14/20] mtd: nand: qcom: add command elements in BAM transaction

On 08/11/2017 05:09 PM, Abhishek Sahu wrote: All the QPIC register read/write through BAM DMA requires command descriptor which contains the array of command elements. Reviewed-by: Archit Taneja Thanks, Archit Signed-off-by: Abhishek Sahu

Re: [PATCH v4 14/20] mtd: nand: qcom: add command elements in BAM transaction

On 08/11/2017 05:09 PM, Abhishek Sahu wrote: All the QPIC register read/write through BAM DMA requires command descriptor which contains the array of command elements. Reviewed-by: Archit Taneja Thanks, Archit Signed-off-by: Abhishek Sahu --- drivers/mtd/nand/qcom_nandc.c | 19

Re: [PATCH v4 13/20] mtd: nand: qcom: support for different DEV_CMD register offsets

On 08/11/2017 05:09 PM, Abhishek Sahu wrote: The FLASH_DEV_CMD registers starting offset is not same in different QPIC NAND controller versions. This patch adds the starting offset in NAND controller properties and uses the same for calculating the actual offset of these registers.

Re: [PATCH v4 13/20] mtd: nand: qcom: support for different DEV_CMD register offsets

On 08/11/2017 05:09 PM, Abhishek Sahu wrote: The FLASH_DEV_CMD registers starting offset is not same in different QPIC NAND controller versions. This patch adds the starting offset in NAND controller properties and uses the same for calculating the actual offset of these registers.

linux-next: Tree for Aug 16

Hi all, There will be no linux-next releases this coming Friday or Monday. Changes since 20170815: The pci tree gained a conflict against the net tree. The net-next tree still had its build failure for which I reverted a commit. The akpm-current tree gained a build failure due

linux-next: Tree for Aug 16

Hi all, There will be no linux-next releases this coming Friday or Monday. Changes since 20170815: The pci tree gained a conflict against the net tree. The net-next tree still had its build failure for which I reverted a commit. The akpm-current tree gained a build failure due

[PATCH] Input: i8042: constify pnp_device_id

pnp_device_id are not supposed to change at runtime. All functions working with pnp_device_id provided by work with const pnp_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/input/serio/i8042-x86ia64io.h | 4 ++-- 1 file

[PATCH] Input: i8042: constify pnp_device_id

pnp_device_id are not supposed to change at runtime. All functions working with pnp_device_id provided by work with const pnp_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/input/serio/i8042-x86ia64io.h | 4 ++-- 1 file changed, 2 insertions(+), 2

Re: [PATCH v4 12/20] mtd: nand: qcom: QPIC data descriptors handling

On 08/11/2017 05:09 PM, Abhishek Sahu wrote: 1. Add the data descriptor preparation function which will be used only by BAM DMA for forming the data SGL’s 2. Add clear BAM transaction and call it before every new request 3. Check DMA mode for ADM or BAM and call the appropriate

Re: [PATCH v4 12/20] mtd: nand: qcom: QPIC data descriptors handling

On 08/11/2017 05:09 PM, Abhishek Sahu wrote: 1. Add the data descriptor preparation function which will be used only by BAM DMA for forming the data SGL’s 2. Add clear BAM transaction and call it before every new request 3. Check DMA mode for ADM or BAM and call the appropriate

[PATCH] sg: protect against races between mmap() and SG_SET_RESERVED_SIZE

Take f_mutex around mmap() processing to protect against races with the SG_SET_RESERVED_SIZE ioctl. Ensure the reserve buffer length remains consistent during the mapping operation, and set the "mmap called" flag to prevent further changes to the reserved buffer size as an atomic operation with

[PATCH] sg: protect against races between mmap() and SG_SET_RESERVED_SIZE

Take f_mutex around mmap() processing to protect against races with the SG_SET_RESERVED_SIZE ioctl. Ensure the reserve buffer length remains consistent during the mapping operation, and set the "mmap called" flag to prevent further changes to the reserved buffer size as an atomic operation with

Re: [PATCH v8 00/14] lockdep: Implement crossrelease feature

On Wed, Aug 16, 2017 at 01:37:46PM +0900, Byungchul Park wrote: > On Wed, Aug 16, 2017 at 12:05:31PM +0800, Boqun Feng wrote: > > On Wed, Aug 16, 2017 at 09:16:37AM +0900, Byungchul Park wrote: > > > On Tue, Aug 15, 2017 at 10:20:20AM +0200, Ingo Molnar wrote: > > > > > > > > So with the latest

Re: [PATCH v8 00/14] lockdep: Implement crossrelease feature

On Wed, Aug 16, 2017 at 01:37:46PM +0900, Byungchul Park wrote: > On Wed, Aug 16, 2017 at 12:05:31PM +0800, Boqun Feng wrote: > > On Wed, Aug 16, 2017 at 09:16:37AM +0900, Byungchul Park wrote: > > > On Tue, Aug 15, 2017 at 10:20:20AM +0200, Ingo Molnar wrote: > > > > > > > > So with the latest

[PATCH 1/2] cpufreq: dt-platdev: Automatically create cpufreq device with OPP v2

The initial idea of creating the cpufreq-dt-platdev.c file was to keep a list of platforms that use the "operating-points" (V1) bindings and create cpufreq device for them only, as we weren't sure which platforms would want the device to get created automatically as some had their own cpufreq

[PATCH 2/2] cpufreq: dt-platdev: Drop few entries from whitelist

Drop few ARM (32 and 64 bit) platforms from the whitelist which always use "operating-points-v2" property from their DT. They should continue to work after this patch. Tested on Hikey platform (only the "hisilicon,hi6220" entry). Signed-off-by: Viresh Kumar ---

[PATCH 1/2] cpufreq: dt-platdev: Automatically create cpufreq device with OPP v2

The initial idea of creating the cpufreq-dt-platdev.c file was to keep a list of platforms that use the "operating-points" (V1) bindings and create cpufreq device for them only, as we weren't sure which platforms would want the device to get created automatically as some had their own cpufreq

[PATCH 2/2] cpufreq: dt-platdev: Drop few entries from whitelist

Drop few ARM (32 and 64 bit) platforms from the whitelist which always use "operating-points-v2" property from their DT. They should continue to work after this patch. Tested on Hikey platform (only the "hisilicon,hi6220" entry). Signed-off-by: Viresh Kumar ---

Re: [PATCH] scsi: cxlflash: Fix an error handling path in 'cxlflash_disk_attach()'

On 16/08/17 06:18, Christophe JAILLET wrote: 'rc' is known to be 0 at this point. If 'create_context()' fails, returns -ENOMEM instead of 0 which means success. Signed-off-by: Christophe JAILLET ENOMEM seems right here. Reviewed-by: Andrew Donnellan

Re: [PATCH] scsi: cxlflash: Fix an error handling path in 'cxlflash_disk_attach()'

On 16/08/17 06:18, Christophe JAILLET wrote: 'rc' is known to be 0 at this point. If 'create_context()' fails, returns -ENOMEM instead of 0 which means success. Signed-off-by: Christophe JAILLET ENOMEM seems right here. Reviewed-by: Andrew Donnellan ---

[PATCH] sata: ahci-da850: Fix some error handling paths in 'ahci_da850_probe()'

'rc' is known to be 0 at this point. If 'platform_get_resource()' or 'devm_ioremap()' fail, return -ENOMEM instead of 0 which means success. Signed-off-by: Christophe JAILLET --- drivers/ata/ahci_da850.c | 8 ++-- 1 file changed, 6 insertions(+), 2

[PATCH] sata: ahci-da850: Fix some error handling paths in 'ahci_da850_probe()'

'rc' is known to be 0 at this point. If 'platform_get_resource()' or 'devm_ioremap()' fail, return -ENOMEM instead of 0 which means success. Signed-off-by: Christophe JAILLET --- drivers/ata/ahci_da850.c | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git

[PATCH] [media] radio: constify pnp_device_id

pnp_device_id are not supposed to change at runtime. All functions working with pnp_device_id provided by work with const pnp_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/media/radio/radio-cadet.c| 2 +-

[PATCH] [media] radio: constify pnp_device_id

pnp_device_id are not supposed to change at runtime. All functions working with pnp_device_id provided by work with const pnp_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/media/radio/radio-cadet.c| 2 +- drivers/media/radio/radio-gemtek.c | 2

[PATCH v2 4/4] staging: pi433: Remove camel case variable names

Remove Camel casing by renaming variables. Signed-off-by: Rishabh Hardas --- drivers/staging/pi433/pi433_if.c | 4 ++-- drivers/staging/pi433/pi433_if.h | 6 +++--- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/drivers/staging/pi433/pi433_if.c

[PATCH v2 4/4] staging: pi433: Remove camel case variable names

Remove Camel casing by renaming variables. Signed-off-by: Rishabh Hardas --- drivers/staging/pi433/pi433_if.c | 4 ++-- drivers/staging/pi433/pi433_if.h | 6 +++--- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/drivers/staging/pi433/pi433_if.c b/drivers/staging/pi433/pi433_if.c

[PATCH v2 3/4] staging: pi433: Renaming Enums

Remove camel casing by renaming enums. Signed-off-by: Rishabh Hardas --- drivers/staging/pi433/pi433_if.h | 36 drivers/staging/pi433/rf69.c | 26 +- drivers/staging/pi433/rf69.h | 26

[PATCH v2 3/4] staging: pi433: Renaming Enums

Remove camel casing by renaming enums. Signed-off-by: Rishabh Hardas --- drivers/staging/pi433/pi433_if.h | 36 drivers/staging/pi433/rf69.c | 26 +- drivers/staging/pi433/rf69.h | 26 +-

[PATCH v2 2/4] staging: pi433: Change Comments

Shorten long comments and format them in kernel style comments. Signed-off-by: Rishabh Hardas --- drivers/staging/pi433/pi433_if.h | 15 --- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/drivers/staging/pi433/pi433_if.h

[PATCH v2 2/4] staging: pi433: Change Comments

Shorten long comments and format them in kernel style comments. Signed-off-by: Rishabh Hardas --- drivers/staging/pi433/pi433_if.h | 15 --- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/drivers/staging/pi433/pi433_if.h b/drivers/staging/pi433/pi433_if.h index

[PATCH v2 1/4] staging: pi433: Style fix - Correct long lines

Correct lines above 80 characters in pi433_if.h Signed-off-by: Rishabh Hardas --- drivers/staging/pi433/pi433_if.h | 28 +++- 1 file changed, 15 insertions(+), 13 deletions(-) diff --git a/drivers/staging/pi433/pi433_if.h

[PATCH v2 0/4] staging: pi433: Rename camel case and other style issues

Hi, This series pf patches solves some of the coding style issues. I have corrected long lines, changed comment style, renamed enums and variables that were in camel case. Tried to get zero erros and warnings on the pi433_if.h file. Regards, Rishabh Hardas Rishabh Hardas (4): staging: pi433:

[PATCH v2 1/4] staging: pi433: Style fix - Correct long lines

Correct lines above 80 characters in pi433_if.h Signed-off-by: Rishabh Hardas --- drivers/staging/pi433/pi433_if.h | 28 +++- 1 file changed, 15 insertions(+), 13 deletions(-) diff --git a/drivers/staging/pi433/pi433_if.h b/drivers/staging/pi433/pi433_if.h index

[PATCH v2 0/4] staging: pi433: Rename camel case and other style issues

Hi, This series pf patches solves some of the coding style issues. I have corrected long lines, changed comment style, renamed enums and variables that were in camel case. Tried to get zero erros and warnings on the pi433_if.h file. Regards, Rishabh Hardas Rishabh Hardas (4): staging: pi433:

Re: [PATCH 2/3] libnvdimm, pfn, dax: show supported dax/pfn region alignments in sysfs

On Wed, Aug 16, 2017 at 1:47 AM, Dan Williams wrote: > On Mon, Aug 14, 2017 at 11:46 PM, Oliver wrote: >> On Tue, Aug 15, 2017 at 4:02 PM, kbuild test robot wrote: > [..] >>>114 static const unsigned long

Re: [PATCH 2/3] libnvdimm, pfn, dax: show supported dax/pfn region alignments in sysfs

On Wed, Aug 16, 2017 at 1:47 AM, Dan Williams wrote: > On Mon, Aug 14, 2017 at 11:46 PM, Oliver wrote: >> On Tue, Aug 15, 2017 at 4:02 PM, kbuild test robot wrote: > [..] >>>114 static const unsigned long *nd_pfn_supported_alignments(void) >>>115 { >>>116 /* >>>117

[rcu:rcu/dev 14/15] kernel/time/tick-sched.c:820: undefined reference to `__divdi3'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/dev head: 551164572a4a41968abd020ec24499085cc2adf7 commit: 33103e7b1f89ef432dfe3337d2a6932cdf5c1312 [14/15] EXP: Trace tick return from tick_nohz_stop_sched_tick config: mips-nlm_xlr_defconfig (attached as

[rcu:rcu/dev 14/15] kernel/time/tick-sched.c:820: undefined reference to `__divdi3'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/dev head: 551164572a4a41968abd020ec24499085cc2adf7 commit: 33103e7b1f89ef432dfe3337d2a6932cdf5c1312 [14/15] EXP: Trace tick return from tick_nohz_stop_sched_tick config: mips-nlm_xlr_defconfig (attached as

[PATCH] crypto: cavium/nitrox - Fix an error handling path in 'nitrox_probe()'

'err' is known to be 0 at this point. If 'kzalloc()' fails, returns -ENOMEM instead of 0 which means success. Signed-off-by: Christophe JAILLET --- drivers/crypto/cavium/nitrox/nitrox_main.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git

[PATCH] crypto: cavium/nitrox - Fix an error handling path in 'nitrox_probe()'

'err' is known to be 0 at this point. If 'kzalloc()' fails, returns -ENOMEM instead of 0 which means success. Signed-off-by: Christophe JAILLET --- drivers/crypto/cavium/nitrox/nitrox_main.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git

[PATCH] bpf: Update sysctl documentation to list all supported architectures

The sysctl documentation states that the JIT is only available on x86_64, which is no longer correct. Update the list to include all architectures that enable HAVE_CBPF_JIT or HAVE_EBPF_JIT under some configuration. Signed-off-by: Michael Ellerman ---

[PATCH] bpf: Update sysctl documentation to list all supported architectures

The sysctl documentation states that the JIT is only available on x86_64, which is no longer correct. Update the list to include all architectures that enable HAVE_CBPF_JIT or HAVE_EBPF_JIT under some configuration. Signed-off-by: Michael Ellerman --- Documentation/sysctl/net.txt | 5 +++-- 1

RE: [PATCH v2 19/22] fpga: intel: afu: add header sub feature support

> On Sun, Jun 25, 2017 at 8:52 PM, Wu Hao wrote: > > Hi Hao, > > > The header register set is always present for the Port/AFU, it is mainly > > for capability, control and status of the ports that AFU connected to. > > So just to be clear, the reset function is acting on the

RE: [PATCH v2 19/22] fpga: intel: afu: add header sub feature support

> On Sun, Jun 25, 2017 at 8:52 PM, Wu Hao wrote: > > Hi Hao, > > > The header register set is always present for the Port/AFU, it is mainly > > for capability, control and status of the ports that AFU connected to. > > So just to be clear, the reset function is acting on the Port, not the >

RE: [PATCH 0/5] cramfs refresh for embedded usage

On Tue, 15 Aug 2017, Chris Brandt wrote: > On Tuesday, August 15, 2017 1, Nicolas Pitre wrote: > > I was able to reproduce. The following patch on top should partially fix > > it. I'm trying to figure out how to split a vma and link it properly in > > the case the vma cannot be mapped entirely.

RE: [PATCH 0/5] cramfs refresh for embedded usage

On Tue, 15 Aug 2017, Chris Brandt wrote: > On Tuesday, August 15, 2017 1, Nicolas Pitre wrote: > > I was able to reproduce. The following patch on top should partially fix > > it. I'm trying to figure out how to split a vma and link it properly in > > the case the vma cannot be mapped entirely.

Re: Possible race in c4.ko

Hello Anton, Thanks for reviewing the code. This would be right, if the c4 could rise an interrupt at this moment ... After a reset with c4_reset(), the card will not generate an interrupt, until firmware has been loaded and the SEND_INIT message has been sent. c4_load_firmware() ->

Re: Possible race in c4.ko

Hello Anton, Thanks for reviewing the code. This would be right, if the c4 could rise an interrupt at this moment ... After a reset with c4_reset(), the card will not generate an interrupt, until firmware has been loaded and the SEND_INIT message has been sent. c4_load_firmware() ->

Re: [PATCH v8 00/14] lockdep: Implement crossrelease feature

On Wed, Aug 16, 2017 at 12:05:31PM +0800, Boqun Feng wrote: > > I see... > > > > Worker A : acquired of wfc.work -> wait for cpu_hotplug_lock to be released > > Task B : acquired of cpu_hotplug_lock -> wait for lock#3 to be released > > Task C : acquired of lock#3 -> wait for completion of

Re: [PATCH v8 00/14] lockdep: Implement crossrelease feature

On Wed, Aug 16, 2017 at 12:05:31PM +0800, Boqun Feng wrote: > > I see... > > > > Worker A : acquired of wfc.work -> wait for cpu_hotplug_lock to be released > > Task B : acquired of cpu_hotplug_lock -> wait for lock#3 to be released > > Task C : acquired of lock#3 -> wait for completion of

[PATCH] EDAC, altera: Fix an error handling path in 'altr_edac_device_probe()'

'res' is known to be 0 at this point. If 'devm_ioremap()' fails, returns -ENOMEM instead of 0 which means success. Signed-off-by: Christophe JAILLET --- drivers/edac/altera_edac.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git

[PATCH] EDAC, altera: Fix an error handling path in 'altr_edac_device_probe()'

'res' is known to be 0 at this point. If 'devm_ioremap()' fails, returns -ENOMEM instead of 0 which means success. Signed-off-by: Christophe JAILLET --- drivers/edac/altera_edac.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/edac/altera_edac.c

[PATCH] scsi: aha1542: constify pnp_device_id

pnp_device_id are not supposed to change at runtime. All functions working with pnp_device_id provided by work with const pnp_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/scsi/aha1542.c | 2 +- 1 file changed, 1

[PATCH] scsi: ncr5380: constify pnp_device_id

pnp_device_id are not supposed to change at runtime. All functions working with pnp_device_id provided by work with const pnp_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/scsi/g_NCR5380.c | 2 +- 1 file changed, 1

[PATCH] scsi: aha1542: constify pnp_device_id

pnp_device_id are not supposed to change at runtime. All functions working with pnp_device_id provided by work with const pnp_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/scsi/aha1542.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

[PATCH] scsi: ncr5380: constify pnp_device_id

pnp_device_id are not supposed to change at runtime. All functions working with pnp_device_id provided by work with const pnp_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/scsi/g_NCR5380.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

Re: [PATCH v7 9/9] sparc64: Add support for ADI (Application Data Integrity)

From: Khalid Aziz Date: Wed, 9 Aug 2017 15:26:02 -0600 > +void adi_restore_tags(struct mm_struct *mm, struct vm_area_struct *vma, > + unsigned long addr, pte_t pte) > +{ ... > + tag = tag_start(addr, tag_desc); > + paddr = pte_val(pte) &

Re: [PATCH v7 9/9] sparc64: Add support for ADI (Application Data Integrity)

From: Khalid Aziz Date: Wed, 9 Aug 2017 15:26:02 -0600 > +void adi_restore_tags(struct mm_struct *mm, struct vm_area_struct *vma, > + unsigned long addr, pte_t pte) > +{ ... > + tag = tag_start(addr, tag_desc); > + paddr = pte_val(pte) & _PAGE_PADDR_4V; > + for

[PATCH] EDAC, thunderx: Fix an error handling path in 'thunderx_lmc_probe()'

'ret' is known to be 0 at this point. If 'ioremap()' fails, returns -ENOMEM instead of 0 which means success. Signed-off-by: Christophe JAILLET --- drivers/edac/thunderx_edac.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/edac/thunderx_edac.c

[PATCH] EDAC, thunderx: Fix an error handling path in 'thunderx_lmc_probe()'

'ret' is known to be 0 at this point. If 'ioremap()' fails, returns -ENOMEM instead of 0 which means success. Signed-off-by: Christophe JAILLET --- drivers/edac/thunderx_edac.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/edac/thunderx_edac.c b/drivers/edac/thunderx_edac.c index

[PATCH] watchdog: sc1200: constify pnp_device_id

pnp_device_id are not supposed to change at runtime. All functions working with pnp_device_id provided by work with const pnp_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/watchdog/sc1200wdt.c | 2 +- 1 file changed, 1

[PATCH] watchdog: sc1200: constify pnp_device_id

pnp_device_id are not supposed to change at runtime. All functions working with pnp_device_id provided by work with const pnp_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/watchdog/sc1200wdt.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH] net: 3c509: constify pnp_device_id

pnp_device_id are not supposed to change at runtime. All functions working with pnp_device_id provided by work with const pnp_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/net/ethernet/3com/3c509.c | 2 +- 1 file changed,

[PATCH] net: 3c509: constify pnp_device_id

pnp_device_id are not supposed to change at runtime. All functions working with pnp_device_id provided by work with const pnp_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/net/ethernet/3com/3c509.c | 2 +- 1 file changed, 1 insertion(+), 1

Re: [PATCH] ASoC: Medfield: Delete an error message for a failed memory allocation in snd_mfld_mc_probe()

On Fri, Aug 11, 2017 at 11:33:56AM +0200, SF Markus Elfring wrote: > From: Markus Elfring > Date: Fri, 11 Aug 2017 11:25:41 +0200 > > Omit an extra message for a memory allocation failure in this function. > > This issue was detected by using the Coccinelle

Re: [PATCH] ASoC: Medfield: Delete an error message for a failed memory allocation in snd_mfld_mc_probe()

On Fri, Aug 11, 2017 at 11:33:56AM +0200, SF Markus Elfring wrote: > From: Markus Elfring > Date: Fri, 11 Aug 2017 11:25:41 +0200 > > Omit an extra message for a memory allocation failure in this function. > > This issue was detected by using the Coccinelle software. Acked-By: Vinod Koul >

[PATCH] PNP: ide: constify pnp_device_id

pnp_device_id are not supposed to change at runtime. All functions working with pnp_device_id provided by work with const pnp_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/ide/ide-pnp.c | 2 +- 1 file changed, 1

[PATCH] PNP: ide: constify pnp_device_id

pnp_device_id are not supposed to change at runtime. All functions working with pnp_device_id provided by work with const pnp_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/ide/ide-pnp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

Re: [PATCH v7 2/9] mm, swap: Add infrastructure for saving page metadata on swap

From: Khalid Aziz Date: Wed, 9 Aug 2017 15:25:55 -0600 > @@ -1399,6 +1399,12 @@ static bool try_to_unmap_one(struct page *page, struct > vm_area_struct *vma, > (flags & TTU_MIGRATION)) { > swp_entry_t entry; >

[PATCH v2 0/5] K2G: Add QSPI support

This series adds support for Cadence QSPI IP present in TI's 66AK2G SoC. The patches enhance the existing cadence-quadspi driver to support loopback clock circuit, pm_runtime support and tweaks for 66AK2G SoC. Changes in v2: * Drop DT patches. Will be sent as separate series as requested by

Re: [PATCH v7 2/9] mm, swap: Add infrastructure for saving page metadata on swap

From: Khalid Aziz Date: Wed, 9 Aug 2017 15:25:55 -0600 > @@ -1399,6 +1399,12 @@ static bool try_to_unmap_one(struct page *page, struct > vm_area_struct *vma, > (flags & TTU_MIGRATION)) { > swp_entry_t entry; > pte_t

[PATCH v2 0/5] K2G: Add QSPI support

This series adds support for Cadence QSPI IP present in TI's 66AK2G SoC. The patches enhance the existing cadence-quadspi driver to support loopback clock circuit, pm_runtime support and tweaks for 66AK2G SoC. Changes in v2: * Drop DT patches. Will be sent as separate series as requested by

[PATCH v2 2/5] mtd: spi-nor: cadence-quadspi: add a delay in write sequence

As per 66AK2G02 TRM[1] SPRUHY8F section 11.15.5.3 Indirect Access Controller programming sequence, a delay equal to couple of QSPI master clock(~5ns) is required after setting CQSPI_REG_INDIRECTWR_START bit and writing data to the flash. Introduce a quirk flag CQSPI_NEEDS_WR_DELAY to handle this

[PATCH v2 2/5] mtd: spi-nor: cadence-quadspi: add a delay in write sequence

As per 66AK2G02 TRM[1] SPRUHY8F section 11.15.5.3 Indirect Access Controller programming sequence, a delay equal to couple of QSPI master clock(~5ns) is required after setting CQSPI_REG_INDIRECTWR_START bit and writing data to the flash. Introduce a quirk flag CQSPI_NEEDS_WR_DELAY to handle this

[PATCH v2 1/5] mtd: spi-nor: cadence-quadspi: Add TI 66AK2G SoC specific compatible

Update binding documentation to add a new compatible for TI 66AK2G SoC, to handle TI SoC specific quirks in the driver. Signed-off-by: Vignesh R --- Documentation/devicetree/bindings/mtd/cadence-quadspi.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git

[PATCH v2 3/5] mtd: spi-nor: cadence-quadspi: Add new binding to enable loop-back circuit

Cadence QSPI IP has a adapted loop-back circuit which can be enabled by setting BYPASS field to 0 in READCAPTURE register. It enables use of QSPI return clock to latch the data rather than the internal QSPI reference clock. For high speed operations, adapted loop-back circuit using QSPI return

[PATCH v2 3/5] mtd: spi-nor: cadence-quadspi: Add new binding to enable loop-back circuit

Cadence QSPI IP has a adapted loop-back circuit which can be enabled by setting BYPASS field to 0 in READCAPTURE register. It enables use of QSPI return clock to latch the data rather than the internal QSPI reference clock. For high speed operations, adapted loop-back circuit using QSPI return

[PATCH v2 1/5] mtd: spi-nor: cadence-quadspi: Add TI 66AK2G SoC specific compatible

Update binding documentation to add a new compatible for TI 66AK2G SoC, to handle TI SoC specific quirks in the driver. Signed-off-by: Vignesh R --- Documentation/devicetree/bindings/mtd/cadence-quadspi.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git

[PATCH][RFC v2] PM / Hibernate: Disable wathdog when creating snapshot

There is a problem that when counting the pages for creating the hibernation snapshot will take significant amount of time, especially on system with large memory. Since the counting job is performed with irq disabled, this might lead to NMI lockup. The following warning were found on a system

[PATCH v2 5/5] mtd: spi-nor: cadence-quadspi: Add runtime PM support

Add pm_runtime* calls to cadence-quadspi driver. This is required to switch on QSPI power domain on TI 66AK2G SoC during probe. Signed-off-by: Vignesh R --- drivers/mtd/spi-nor/cadence-quadspi.c | 11 +++ 1 file changed, 11 insertions(+) diff --git

[PATCH][RFC v2] PM / Hibernate: Disable wathdog when creating snapshot

There is a problem that when counting the pages for creating the hibernation snapshot will take significant amount of time, especially on system with large memory. Since the counting job is performed with irq disabled, this might lead to NMI lockup. The following warning were found on a system

[PATCH v2 5/5] mtd: spi-nor: cadence-quadspi: Add runtime PM support

Add pm_runtime* calls to cadence-quadspi driver. This is required to switch on QSPI power domain on TI 66AK2G SoC during probe. Signed-off-by: Vignesh R --- drivers/mtd/spi-nor/cadence-quadspi.c | 11 +++ 1 file changed, 11 insertions(+) diff --git

Re: [PATCH][RFC] PM / Hibernate: Feed NMI wathdog when creating snapshot

On Tue, Aug 15, 2017 at 02:41:19PM +0200, Michal Hocko wrote: > On Tue 15-08-17 01:19:16, Chen Yu wrote: > [...] > > @@ -2561,8 +2562,10 @@ void mark_free_pages(struct zone *zone) > > unsigned long i; > > > > pfn = page_to_pfn(page); > > -

Re: [PATCH][RFC] PM / Hibernate: Feed NMI wathdog when creating snapshot

On Tue, Aug 15, 2017 at 02:41:19PM +0200, Michal Hocko wrote: > On Tue 15-08-17 01:19:16, Chen Yu wrote: > [...] > > @@ -2561,8 +2562,10 @@ void mark_free_pages(struct zone *zone) > > unsigned long i; > > > > pfn = page_to_pfn(page); > > -

[PATCH v2 4/5] mtd: spi-nor: cadence-quadspi: Add support to enable loop-back clock circuit

Cadence QSPI IP has a adapted loop-back circuit which can be enabled by setting BYPASS field to 0 in READCAPTURE register. It enables use of QSPI return clock to latch the data rather than the internal QSPI reference clock. For high speed operations, adapted loop-back circuit using QSPI return

[PATCH v2 4/5] mtd: spi-nor: cadence-quadspi: Add support to enable loop-back clock circuit

Cadence QSPI IP has a adapted loop-back circuit which can be enabled by setting BYPASS field to 0 in READCAPTURE register. It enables use of QSPI return clock to latch the data rather than the internal QSPI reference clock. For high speed operations, adapted loop-back circuit using QSPI return

Re: [PATCH v2] zsmalloc: zs_page_migrate: schedule free_work if zspage is ZS_EMPTY

On Wed, Aug 16, 2017 at 10:49:14AM +0800, Hui Zhu wrote: > Hi Minchan, > > 2017-08-16 10:13 GMT+08:00 Minchan Kim : > > Hi Hui, > > > > On Mon, Aug 14, 2017 at 05:56:30PM +0800, Hui Zhu wrote: > >> After commit e2846124f9a2 ("zsmalloc: zs_page_migrate: skip unnecessary > > > >

Re: [PATCH v2] zsmalloc: zs_page_migrate: schedule free_work if zspage is ZS_EMPTY

On Wed, Aug 16, 2017 at 10:49:14AM +0800, Hui Zhu wrote: > Hi Minchan, > > 2017-08-16 10:13 GMT+08:00 Minchan Kim : > > Hi Hui, > > > > On Mon, Aug 14, 2017 at 05:56:30PM +0800, Hui Zhu wrote: > >> After commit e2846124f9a2 ("zsmalloc: zs_page_migrate: skip unnecessary > > > > This patch is not

Re: [PATCH v4 11/20] mtd: nand: qcom: enable BAM or ADM mode

On 08/11/2017 05:09 PM, Abhishek Sahu wrote: 1. DM_EN is only required for EBI2 NAND controller which uses ADM 2. BAM mode will be disabled after power on reset which needs to be enabled before starting any BAM transfers. Signed-off-by: Abhishek Sahu ---

Re: [PATCH v4 11/20] mtd: nand: qcom: enable BAM or ADM mode

On 08/11/2017 05:09 PM, Abhishek Sahu wrote: 1. DM_EN is only required for EBI2 NAND controller which uses ADM 2. BAM mode will be disabled after power on reset which needs to be enabled before starting any BAM transfers. Signed-off-by: Abhishek Sahu --- drivers/mtd/nand/qcom_nandc.c |

[PATCH] sg: recheck MMAP_IO request length with lock held

Commit 1bc0eb044615 ("scsi: sg: protect accesses to 'reserved' page array") adds needed concurrency protection for the "reserve" buffer. Some checks that are initially made outside the lock are replicated once the lock is taken to ensure the checks and resulting decisions are made using consistent

[PATCH] sg: recheck MMAP_IO request length with lock held

Commit 1bc0eb044615 ("scsi: sg: protect accesses to 'reserved' page array") adds needed concurrency protection for the "reserve" buffer. Some checks that are initially made outside the lock are replicated once the lock is taken to ensure the checks and resulting decisions are made using consistent

Re: [PATCH v1 2/6] fs: use on-stack-bio if backing device has BDI_CAP_SYNC capability

Hi Jens, On Mon, Aug 14, 2017 at 10:17:09AM -0600, Jens Axboe wrote: > On 08/14/2017 09:38 AM, Jens Axboe wrote: > > On 08/14/2017 09:31 AM, Minchan Kim wrote: > >>> Secondly, generally you don't have slow devices and fast devices > >>> intermingled when running workloads. That's the rare case. >

Re: [PATCH v1 2/6] fs: use on-stack-bio if backing device has BDI_CAP_SYNC capability

Hi Jens, On Mon, Aug 14, 2017 at 10:17:09AM -0600, Jens Axboe wrote: > On 08/14/2017 09:38 AM, Jens Axboe wrote: > > On 08/14/2017 09:31 AM, Minchan Kim wrote: > >>> Secondly, generally you don't have slow devices and fast devices > >>> intermingled when running workloads. That's the rare case. >

  1   2   3   4   5   6   7   8   9   10   >