[PATCH] Input: Change BTN_TOOL_FINGER falg when HOVER event trigger

Only ABS_DISTANCE is not enough for upper OS to distiguish hover event be triggered from object form faraway to and close touchpad surface or from object prepare to leave the touchpad surface. We add BNT_TOOL_FINGER to help it. Object_at_faraway

[PATCH] Input: Change BTN_TOOL_FINGER falg when HOVER event trigger

Only ABS_DISTANCE is not enough for upper OS to distiguish hover event be triggered from object form faraway to and close touchpad surface or from object prepare to leave the touchpad surface. We add BNT_TOOL_FINGER to help it. Object_at_faraway

Re: [lustre-devel] [PATCH] Revert "Staging: lustre: o2iblnd: Use sizeof type *pointer instead of sizeof type."

On 2016/03/22, 19:49, "lustre-devel on behalf of Greg Kroah-Hartman" wrote: >On Tue, Mar 22, 2016 at 06:21:04PM -0400, James Simmons wrote: >> Latest testing fails when using ko2iblnd. It was tracked down >> to commit

Re: [lustre-devel] [PATCH] Revert "Staging: lustre: o2iblnd: Use sizeof type *pointer instead of sizeof type."

On 2016/03/22, 19:49, "lustre-devel on behalf of Greg Kroah-Hartman" wrote: >On Tue, Mar 22, 2016 at 06:21:04PM -0400, James Simmons wrote: >> Latest testing fails when using ko2iblnd. It was tracked down >> to commit 4671a026616df26000f7d8ad2f2ea4b6de79263c. >> >> This reverts commit

[PATCH] tpm_tis: drop manufacturer_id from struct tpm_vendor_specific

Dropped manufacturer_id from struct tpm_vendor_specific and redeclared it in the private struct priv_data that tpm_tis uses because the field is only used tpm_tis. Signed-off-by: Jarkko Sakkinen --- drivers/char/tpm/tpm.h | 2 -- drivers/char/tpm/tpm_tis.c |

[PATCH] tpm_tis: drop manufacturer_id from struct tpm_vendor_specific

Dropped manufacturer_id from struct tpm_vendor_specific and redeclared it in the private struct priv_data that tpm_tis uses because the field is only used tpm_tis. Signed-off-by: Jarkko Sakkinen --- drivers/char/tpm/tpm.h | 2 -- drivers/char/tpm/tpm_tis.c | 7 +-- 2 files changed, 5

Re: [PATCH] tty/hvc: Use IRQF_SHARED for hvc consoles

Samuel Mendoza-Jonas writes: > Commit 2def86a7200c > ("hvc: Convert to using interrupts instead of opal events") > enabled the use of interrupts in the hvc_driver for OPAL platforms. > However on machines with more than one hvc console, any console after > the first will

Re: [PATCH] tty/hvc: Use IRQF_SHARED for hvc consoles

Samuel Mendoza-Jonas writes: > Commit 2def86a7200c > ("hvc: Convert to using interrupts instead of opal events") > enabled the use of interrupts in the hvc_driver for OPAL platforms. > However on machines with more than one hvc console, any console after > the first will fail to register an

[PATCH] staging: dgnc: fix CamelCase in dgnc_driver.c

fix checkpatch.pl warning about CamelCase. Signed-off-by: Daeseok Youn --- drivers/staging/dgnc/dgnc_driver.c | 52 +++--- 1 file changed, 26 insertions(+), 26 deletions(-) diff --git a/drivers/staging/dgnc/dgnc_driver.c

[PATCH] staging: dgnc: fix CamelCase in dgnc_driver.c

fix checkpatch.pl warning about CamelCase. Signed-off-by: Daeseok Youn --- drivers/staging/dgnc/dgnc_driver.c | 52 +++--- 1 file changed, 26 insertions(+), 26 deletions(-) diff --git a/drivers/staging/dgnc/dgnc_driver.c b/drivers/staging/dgnc/dgnc_driver.c

Re: [PATCH 0/3] Remaining fixes for v4.5 (post tpmdd-next-20160120)

On Wed, Mar 23, 2016 at 07:09:24AM +0200, Jarkko Sakkinen wrote: > Fixes remaining after tpmdd-next-20160120 has been pulled and API change > so that session object stays intact after a successful unseal operation. Oops. Please ignore this, did a mistake with git send-email. Sorry about this.

Re: [PATCH 0/3] Remaining fixes for v4.5 (post tpmdd-next-20160120)

On Wed, Mar 23, 2016 at 07:09:24AM +0200, Jarkko Sakkinen wrote: > Fixes remaining after tpmdd-next-20160120 has been pulled and API change > so that session object stays intact after a successful unseal operation. Oops. Please ignore this, did a mistake with git send-email. Sorry about this.

[PATCH] tpm_atmel: drop tpm_atmel specific fields from tpm_vendor_specific

Introduced a private struct tpm_atmel_priv that contains the variables have_region and region_size that were previously located in struct tpm_vendor_specific. These fields were only used by tpm_atmel. Signed-off-by: Jarkko Sakkinen --- drivers/char/tpm/tpm.h

[PATCH] tpm_atmel: drop tpm_atmel specific fields from tpm_vendor_specific

Introduced a private struct tpm_atmel_priv that contains the variables have_region and region_size that were previously located in struct tpm_vendor_specific. These fields were only used by tpm_atmel. Signed-off-by: Jarkko Sakkinen --- drivers/char/tpm/tpm.h | 3 ---

[PATCH 0/3] Remaining fixes for v4.5 (post tpmdd-next-20160120)

Fixes remaining after tpmdd-next-20160120 has been pulled and API change so that session object stays intact after a successful unseal operation. Harald Hoyer (1): tpm_eventlog.c: fix binary_bios_measurements Jarkko Sakkinen (2): tpm: fix: keep auth session intact after unseal operation

[PATCH 0/3] Remaining fixes for v4.5 (post tpmdd-next-20160120)

Fixes remaining after tpmdd-next-20160120 has been pulled and API change so that session object stays intact after a successful unseal operation. Harald Hoyer (1): tpm_eventlog.c: fix binary_bios_measurements Jarkko Sakkinen (2): tpm: fix: keep auth session intact after unseal operation

Re: [PATCH v2 13/18] mm/compaction: support non-lru movable page migration

On Tue, Mar 22, 2016 at 11:55:45PM +0900, Minchan Kim wrote: > On Tue, Mar 22, 2016 at 02:50:37PM +0900, Joonsoo Kim wrote: > > On Mon, Mar 21, 2016 at 03:31:02PM +0900, Minchan Kim wrote: > > > We have allowed migration for only LRU pages until now and it was > > > enough to make high-order

Re: [PATCH v2 13/18] mm/compaction: support non-lru movable page migration

On Tue, Mar 22, 2016 at 11:55:45PM +0900, Minchan Kim wrote: > On Tue, Mar 22, 2016 at 02:50:37PM +0900, Joonsoo Kim wrote: > > On Mon, Mar 21, 2016 at 03:31:02PM +0900, Minchan Kim wrote: > > > We have allowed migration for only LRU pages until now and it was > > > enough to make high-order

Re: [RFC 2/2] staging: android: ion: Add of_ion_device_get function

On Tue, Mar 22, 2016 at 03:33:51PM -0700, Moritz Fischer wrote: > +struct ion_device *of_ion_device_get(struct device_node *node) > +{ > + struct miscdevice *mdev = of_misc_get(node); > + > + if (IS_ERR(mdev)) > + return ERR_PTR(PTR_ERR(mdev)); Use ERR_CAST() for this.

Re: [RFC 2/2] staging: android: ion: Add of_ion_device_get function

On Tue, Mar 22, 2016 at 03:33:51PM -0700, Moritz Fischer wrote: > +struct ion_device *of_ion_device_get(struct device_node *node) > +{ > + struct miscdevice *mdev = of_misc_get(node); > + > + if (IS_ERR(mdev)) > + return ERR_PTR(PTR_ERR(mdev)); Use ERR_CAST() for this.

Re: rcu stalls and soft lockups with recent kernels

(cc) On Tue, 2016-03-22 at 16:22 -0400, Ion Badulescu wrote: > On 03/17/2016 10:28 PM, Mike Galbraith wrote: > > On Wed, 2016-03-16 at 12:15 -0400, Ion Badulescu wrote: > > > Just following up to my own email: > > > > > > It turns out that we can eliminate the RCU stalls by changing from > > >

Re: rcu stalls and soft lockups with recent kernels

(cc) On Tue, 2016-03-22 at 16:22 -0400, Ion Badulescu wrote: > On 03/17/2016 10:28 PM, Mike Galbraith wrote: > > On Wed, 2016-03-16 at 12:15 -0400, Ion Badulescu wrote: > > > Just following up to my own email: > > > > > > It turns out that we can eliminate the RCU stalls by changing from > > >

Re: [PATCH] zram: revive swap_slot_free_notify

On Tue, Mar 22, 2016 at 11:06:29PM +0900, Minchan Kim wrote: > On Tue, Mar 22, 2016 at 05:20:08PM +0900, Joonsoo Kim wrote: > > 2016-03-22 17:00 GMT+09:00 Minchan Kim : > > > On Tue, Mar 22, 2016 at 02:08:59PM +0900, Joonsoo Kim wrote: > > >> On Fri, Mar 18, 2016 at 04:58:31PM

Re: [PATCH] zram: revive swap_slot_free_notify

On Tue, Mar 22, 2016 at 11:06:29PM +0900, Minchan Kim wrote: > On Tue, Mar 22, 2016 at 05:20:08PM +0900, Joonsoo Kim wrote: > > 2016-03-22 17:00 GMT+09:00 Minchan Kim : > > > On Tue, Mar 22, 2016 at 02:08:59PM +0900, Joonsoo Kim wrote: > > >> On Fri, Mar 18, 2016 at 04:58:31PM +0900, Minchan Kim

Re: Suspicious error for CMA stress test

On Fri, Mar 18, 2016 at 03:10:09PM +0100, Vlastimil Babka wrote: > On 03/17/2016 04:52 PM, Joonsoo Kim wrote: > > 2016-03-18 0:43 GMT+09:00 Vlastimil Babka : > >> > >> Okay. I used following slightly optimized version and I need to > >> add 'max_order = min_t(unsigned

Re: Suspicious error for CMA stress test

On Fri, Mar 18, 2016 at 03:10:09PM +0100, Vlastimil Babka wrote: > On 03/17/2016 04:52 PM, Joonsoo Kim wrote: > > 2016-03-18 0:43 GMT+09:00 Vlastimil Babka : > >> > >> Okay. I used following slightly optimized version and I need to > >> add 'max_order = min_t(unsigned int, MAX_ORDER,

Re: Suspicious error for CMA stress test

On Tue, Mar 22, 2016 at 03:56:46PM +0100, Lucas Stach wrote: > Am Montag, den 21.03.2016, 13:42 +0900 schrieb Joonsoo Kim: > > On Fri, Mar 18, 2016 at 02:32:35PM +0100, Lucas Stach wrote: > > > Hi Vlastimil, Joonsoo, > > > > > > Am Freitag, den 18.03.2016, 00:52 +0900 schrieb Joonsoo Kim: > > > >

Re: Suspicious error for CMA stress test

On Tue, Mar 22, 2016 at 03:56:46PM +0100, Lucas Stach wrote: > Am Montag, den 21.03.2016, 13:42 +0900 schrieb Joonsoo Kim: > > On Fri, Mar 18, 2016 at 02:32:35PM +0100, Lucas Stach wrote: > > > Hi Vlastimil, Joonsoo, > > > > > > Am Freitag, den 18.03.2016, 00:52 +0900 schrieb Joonsoo Kim: > > > >

Re: [PATCH v2] cpufreq: rockchip: add driver

On 23-03-16, 10:18, Feng Xiao wrote: > diff --git a/drivers/cpufreq/Kconfig.arm b/drivers/cpufreq/Kconfig.arm > index 14b1f93..1786315 100644 > --- a/drivers/cpufreq/Kconfig.arm > +++ b/drivers/cpufreq/Kconfig.arm > @@ -97,6 +97,16 @@ config ARM_OMAP2PLUS_CPUFREQ > depends on ARCH_OMAP2PLUS

Re: [PATCH v2] cpufreq: rockchip: add driver

On 23-03-16, 10:18, Feng Xiao wrote: > diff --git a/drivers/cpufreq/Kconfig.arm b/drivers/cpufreq/Kconfig.arm > index 14b1f93..1786315 100644 > --- a/drivers/cpufreq/Kconfig.arm > +++ b/drivers/cpufreq/Kconfig.arm > @@ -97,6 +97,16 @@ config ARM_OMAP2PLUS_CPUFREQ > depends on ARCH_OMAP2PLUS

Re: [PATCH 1/2] mm/hugetlb: Introduce hugetlb_bad_size

On Wed, 23 Mar 2016, Vaishali Thakkar wrote: On Wednesday 23 March 2016 04:57 AM, SeongJae Park wrote: Hello Vaishali, The patch looks good to me. However, I have few trivial questions. On Tue, 22 Mar 2016, Vaishali Thakkar wrote: When any unsupported hugepage size is specified,

Re: [PATCH 1/2] mm/hugetlb: Introduce hugetlb_bad_size

On Wed, 23 Mar 2016, Vaishali Thakkar wrote: On Wednesday 23 March 2016 04:57 AM, SeongJae Park wrote: Hello Vaishali, The patch looks good to me. However, I have few trivial questions. On Tue, 22 Mar 2016, Vaishali Thakkar wrote: When any unsupported hugepage size is specified,

Re: [PATCH 2/2] arch:mm: Use hugetlb_bad_size

> > Do you want me to send new version of the patchset breaking this patch in > to separate patches? > Yes. thanks Hillf

Re: [PATCH 2/2] arch:mm: Use hugetlb_bad_size

> > Do you want me to send new version of the patchset breaking this patch in > to separate patches? > Yes. thanks Hillf

[PATCH v6] acpi: Issue _OSC call for native thermal interrupt handling

There are several reports of freeze on enabling HWP (Hardware PStates) feature on Skylake based systems by Intel P states driver. The root cause is identified as the HWP interrupts causing BIOS code to freeze. HWP interrupts uses thermal LVT. Linux natively handles thermal interrupts, but in

[PATCH v6] acpi: Issue _OSC call for native thermal interrupt handling

There are several reports of freeze on enabling HWP (Hardware PStates) feature on Skylake based systems by Intel P states driver. The root cause is identified as the HWP interrupts causing BIOS code to freeze. HWP interrupts uses thermal LVT. Linux natively handles thermal interrupts, but in

Re: [PATCH 1/2] mm/hugetlb: Introduce hugetlb_bad_size

On Wednesday 23 March 2016 04:57 AM, SeongJae Park wrote: > Hello Vaishali, > > > The patch looks good to me. However, I have few trivial questions. > > On Tue, 22 Mar 2016, Vaishali Thakkar wrote: > >> When any unsupported hugepage size is specified, 'hugepagesz=' and >> 'hugepages=' should be

Re: [PATCH 1/2] mm/hugetlb: Introduce hugetlb_bad_size

On Wednesday 23 March 2016 04:57 AM, SeongJae Park wrote: > Hello Vaishali, > > > The patch looks good to me. However, I have few trivial questions. > > On Tue, 22 Mar 2016, Vaishali Thakkar wrote: > >> When any unsupported hugepage size is specified, 'hugepagesz=' and >> 'hugepages=' should be

Re: [PATCH 2/2] arch:mm: Use hugetlb_bad_size

On Wednesday 23 March 2016 08:45 AM, Hillf Danton wrote: >> Update the setup_hugepagesz function to call the routine >> hugetlb_bad_size when unsupported hugepage size is found. >> >> Misc: >> - Silent 80 characters warning >> >> Signed-off-by: Vaishali Thakkar >>

Re: [PATCH 2/2] arch:mm: Use hugetlb_bad_size

On Wednesday 23 March 2016 08:45 AM, Hillf Danton wrote: >> Update the setup_hugepagesz function to call the routine >> hugetlb_bad_size when unsupported hugepage size is found. >> >> Misc: >> - Silent 80 characters warning >> >> Signed-off-by: Vaishali Thakkar >> Cc: Mike Kravetz >> Cc:

RE: [PATCH] usb: xhci: Fix incomplete PM resume operation due to XHCI commmand timeout

> -Original Message- > From: Mathias Nyman [mailto:mathias.ny...@linux.intel.com] > Sent: Tuesday, March 22, 2016 5:36 PM > To: Rajesh Bhagat > Cc: gre...@linuxfoundation.org; linux-...@vger.kernel.org; linux- > ker...@vger.kernel.org; Sriram Dash

RE: [PATCH] usb: xhci: Fix incomplete PM resume operation due to XHCI commmand timeout

> -Original Message- > From: Mathias Nyman [mailto:mathias.ny...@linux.intel.com] > Sent: Tuesday, March 22, 2016 5:36 PM > To: Rajesh Bhagat > Cc: gre...@linuxfoundation.org; linux-...@vger.kernel.org; linux- > ker...@vger.kernel.org; Sriram Dash > Subject: Re: [PATCH] usb: xhci: Fix

Re: [PATCH V2 0/2] kexec: Make a pair of map/unmap reserved pages in error path

On 2016/03/23 at 10:48, Baoquan He wrote: > On 03/01/16 at 05:53pm, Xunlei Pang wrote: >> This is a bug fix. >> >> After this, I will try to do a cleanup for crash_unmap/map_reserved_pages() >> (only used by S390) to consolidate it with >> arch_kexec_unprotect/protect_crashkres(). > Hi Xunlei,

Re: [PATCH V2 0/2] kexec: Make a pair of map/unmap reserved pages in error path

On 2016/03/23 at 10:48, Baoquan He wrote: > On 03/01/16 at 05:53pm, Xunlei Pang wrote: >> This is a bug fix. >> >> After this, I will try to do a cleanup for crash_unmap/map_reserved_pages() >> (only used by S390) to consolidate it with >> arch_kexec_unprotect/protect_crashkres(). > Hi Xunlei,

Re: [PATCH 4/5] mm/lru: is_file/active_lru can be boolean

On Wed, 2016-03-23 at 10:26 +0800, Yaowei Bai wrote: > This patch makes is_file/active_lru return bool to improve > readability due to these particular functions only using either > one or zero as their return value. > > No functional change. These assignments to int should likely be modified

Re: [PATCH 4/5] mm/lru: is_file/active_lru can be boolean

On Wed, 2016-03-23 at 10:26 +0800, Yaowei Bai wrote: > This patch makes is_file/active_lru return bool to improve > readability due to these particular functions only using either > one or zero as their return value. > > No functional change. These assignments to int should likely be modified

Re: [PATCH 2/2] arch:mm: Use hugetlb_bad_size

> > Update the setup_hugepagesz function to call the routine > hugetlb_bad_size when unsupported hugepage size is found. > > Misc: > - Silent 80 characters warning > > Signed-off-by: Vaishali Thakkar > Cc: Mike Kravetz > Cc: Naoya

Re: [PATCH 2/2] arch:mm: Use hugetlb_bad_size

> > Update the setup_hugepagesz function to call the routine > hugetlb_bad_size when unsupported hugepage size is found. > > Misc: > - Silent 80 characters warning > > Signed-off-by: Vaishali Thakkar > Cc: Mike Kravetz > Cc: Naoya Horiguchi > Cc: Hillf Danton > Cc: Michal Hocko > Cc:

Question about PCI I/O space in ARM64

Hi all， If no pci, the PCI I/O space(16M) is mapped into an irrelevant mem space(right ?), not a right IO space, that is, no one call pci_remap_iospace() to remap the memory mapped I/O space, once driver like f71805f loaded, write value to IO space(see

Question about PCI I/O space in ARM64

Hi all， If no pci, the PCI I/O space(16M) is mapped into an irrelevant mem space(right ?), not a right IO space, that is, no one call pci_remap_iospace() to remap the memory mapped I/O space, once driver like f71805f loaded, write value to IO space(see

Re: [PATCH V2 0/2] kexec: Make a pair of map/unmap reserved pages in error path

On 03/01/16 at 05:53pm, Xunlei Pang wrote: > This is a bug fix. > > After this, I will try to do a cleanup for crash_unmap/map_reserved_pages() > (only used by S390) to consolidate it with > arch_kexec_unprotect/protect_crashkres(). Hi Xunlei, Minfei, I think you need discuss together about

Re: [PATCH V2 0/2] kexec: Make a pair of map/unmap reserved pages in error path

On 03/01/16 at 05:53pm, Xunlei Pang wrote: > This is a bug fix. > > After this, I will try to do a cleanup for crash_unmap/map_reserved_pages() > (only used by S390) to consolidate it with > arch_kexec_unprotect/protect_crashkres(). Hi Xunlei, Minfei, I think you need discuss together about

[PATCH v2] misc: sram: fix check of devm_ioremap*() return value

Both devm_ioremap() and devm_ioremap_wc() functions return either a pointer to valid iomem region or NULL, check for IS_ERR() is improper and may result in oops on error path. Now on error -ENOMEM is returned. Fixes: 0ab163ad1ea0 ("misc: sram: switch to ioremap_wc from ioremap") Signed-off-by:

[PATCH v2] misc: sram: fix check of devm_ioremap*() return value

Both devm_ioremap() and devm_ioremap_wc() functions return either a pointer to valid iomem region or NULL, check for IS_ERR() is improper and may result in oops on error path. Now on error -ENOMEM is returned. Fixes: 0ab163ad1ea0 ("misc: sram: switch to ioremap_wc from ioremap") Signed-off-by:

Re: [RFC] high preempt off latency in vfree path

> (1) > One is we reduce the number of lazy_max_pages (right now its around 32MB per > core worth of pages). > > diff --git a/mm/vmalloc.c b/mm/vmalloc.c > index aa3891e..2720f4f 100644 > --- a/mm/vmalloc.c > +++ b/mm/vmalloc.c > @@ -564,7 +564,7 @@ static unsigned long lazy_max_pages(void) > >

Re: [RFC] high preempt off latency in vfree path

> (1) > One is we reduce the number of lazy_max_pages (right now its around 32MB per > core worth of pages). > > diff --git a/mm/vmalloc.c b/mm/vmalloc.c > index aa3891e..2720f4f 100644 > --- a/mm/vmalloc.c > +++ b/mm/vmalloc.c > @@ -564,7 +564,7 @@ static unsigned long lazy_max_pages(void) > >

Re: [PATCH 2/2] arch:mm: Use hugetlb_bad_size

On 03/22/2016 03:05 AM, Vaishali Thakkar wrote: > Update the setup_hugepagesz function to call the routine > hugetlb_bad_size when unsupported hugepage size is found. > > Misc: > - Silent 80 characters warning > > Signed-off-by: Vaishali Thakkar > Cc: Mike Kravetz

Re: [PATCH 2/2] arch:mm: Use hugetlb_bad_size

On 03/22/2016 03:05 AM, Vaishali Thakkar wrote: > Update the setup_hugepagesz function to call the routine > hugetlb_bad_size when unsupported hugepage size is found. > > Misc: > - Silent 80 characters warning > > Signed-off-by: Vaishali Thakkar > Cc: Mike Kravetz > Cc: Naoya Horiguchi >

Re: [PATCH 1/2] mm/hugetlb: Introduce hugetlb_bad_size

On 03/22/2016 03:00 AM, Vaishali Thakkar wrote: > When any unsupported hugepage size is specified, 'hugepagesz=' and > 'hugepages=' should be ignored during command line parsing until any > supported hugepage size is found. But currently incorrect number of > hugepages are allocated when

Re: [PATCH 1/2] mm/hugetlb: Introduce hugetlb_bad_size

On 03/22/2016 03:00 AM, Vaishali Thakkar wrote: > When any unsupported hugepage size is specified, 'hugepagesz=' and > 'hugepages=' should be ignored during command line parsing until any > supported hugepage size is found. But currently incorrect number of > hugepages are allocated when

[PATCH] lib: scatterlist: fix ifnullfree.cocci warnings

lib/sg_pool.c:152:3-18: WARNING: NULL check before freeing functions like kfree, debugfs_remove, debugfs_remove_recursive or usb_free_urb is not needed. Maybe consider reorganizing relevant code to avoid passing NULL values. lib/sg_pool.c:154:3-21: WARNING: NULL check before freeing functions

[PATCH] lib: scatterlist: fix ifnullfree.cocci warnings

lib/sg_pool.c:152:3-18: WARNING: NULL check before freeing functions like kfree, debugfs_remove, debugfs_remove_recursive or usb_free_urb is not needed. Maybe consider reorganizing relevant code to avoid passing NULL values. lib/sg_pool.c:154:3-21: WARNING: NULL check before freeing functions

Re: [PATCH v2 5/5] lib: scatterlist: move SG pool code from SCSI driver to lib/sg_pool.c

Hi Ming, [auto build test WARNING on scsi/for-next] [also build test WARNING on v4.5 next-20160322] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https://github.com/0day-ci/linux/commits/Ming-Lin/mempool-based-chained-scatterlist

Re: [PATCH v2 5/5] lib: scatterlist: move SG pool code from SCSI driver to lib/sg_pool.c

Hi Ming, [auto build test WARNING on scsi/for-next] [also build test WARNING on v4.5 next-20160322] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https://github.com/0day-ci/linux/commits/Ming-Lin/mempool-based-chained-scatterlist

Re: [PATCH] Add fwupdate and Mok GUID's to the EFI variable immutable whitelist

On 03/22/2016 04:37 PM, Limonciello, Mario wrote: > ed8b0de5a33d2a2557dce7f9429dca8cb5bc5879 caused all variables to be > immutable by default. This causes problems with userspace applications > mokutil and fwupdate. > --- > drivers/firmware/efi/vars.c | 2 ++ > include/linux/efi.h | 8

Re: [PATCH] Add fwupdate and Mok GUID's to the EFI variable immutable whitelist

On 03/22/2016 04:37 PM, Limonciello, Mario wrote: > ed8b0de5a33d2a2557dce7f9429dca8cb5bc5879 caused all variables to be > immutable by default. This causes problems with userspace applications > mokutil and fwupdate. > --- > drivers/firmware/efi/vars.c | 2 ++ > include/linux/efi.h | 8

Re: [PATCH] vlan: propagate gso_min_segs

On Wed, 2016-03-23 at 09:35 +0800, Haishuang Yan wrote: > vlan drivers lack proper propagation of gso_min_segs from lower device. > > Signed-off-by: Haishuang Yan > --- The plan was to get rid of gso_min_segs, as nothing uses it. Otherwise I would have

Re: [PATCH] vlan: propagate gso_min_segs

On Wed, 2016-03-23 at 09:35 +0800, Haishuang Yan wrote: > vlan drivers lack proper propagation of gso_min_segs from lower device. > > Signed-off-by: Haishuang Yan > --- The plan was to get rid of gso_min_segs, as nothing uses it. Otherwise I would have included this in my recent patches...

Re: RCU stall

On Tue, Mar 22, 2016 at 06:59:32PM -0700, Paul E. McKenney wrote: > On Tue, Mar 22, 2016 at 04:53:26PM -0700, Bart Van Assche wrote: > > On 03/22/2016 01:45 PM, Paul E. McKenney wrote: > > >You are getting a soft lockup as well as an RCU CPU stall warning, so > > >it looks like something is taking

Re: RCU stall

On Tue, Mar 22, 2016 at 06:59:32PM -0700, Paul E. McKenney wrote: > On Tue, Mar 22, 2016 at 04:53:26PM -0700, Bart Van Assche wrote: > > On 03/22/2016 01:45 PM, Paul E. McKenney wrote: > > >You are getting a soft lockup as well as an RCU CPU stall warning, so > > >it looks like something is taking

[PATCH 2/5] mm/memory_hotplug: is_mem_section_removable can be boolean

This patch makes is_mem_section_removable return bool to improve readability due to this particular function only using either one or zero as its return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/memory_hotplug.h | 6 +++---

[PATCH 2/5] mm/memory_hotplug: is_mem_section_removable can be boolean

This patch makes is_mem_section_removable return bool to improve readability due to this particular function only using either one or zero as its return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/memory_hotplug.h | 6 +++--- mm/memory_hotplug.c| 6

Re: [PATCH] staging: delete STE RMI4 hackish driver

On Fri, Mar 18, 2016 at 10:12:15AM +0100, Linus Walleij wrote: > As of commit 62d5bdf972ebcfc99f72f734ae979713e4ca6450 > "Merge branch 'synaptics-rmi4' into next" the input subsystem > has a proper RMI4 infrastructure and touchscreen driver. > The ST Ux500 platform has been converted to use the

[PATCH 0/5] mm: make several functions return bool

This series only makes several functions return bool to improve readability, no other functional changes. Yaowei Bai (5): mm/hugetlb: is_vm_hugetlb_page can be boolean mm/memory_hotplug: is_mem_section_removable can be boolean mm/vmalloc: is_vmalloc_addr can be boolean mm/lru:

Re: [PATCH] staging: delete STE RMI4 hackish driver

On Fri, Mar 18, 2016 at 10:12:15AM +0100, Linus Walleij wrote: > As of commit 62d5bdf972ebcfc99f72f734ae979713e4ca6450 > "Merge branch 'synaptics-rmi4' into next" the input subsystem > has a proper RMI4 infrastructure and touchscreen driver. > The ST Ux500 platform has been converted to use the

[PATCH 0/5] mm: make several functions return bool

This series only makes several functions return bool to improve readability, no other functional changes. Yaowei Bai (5): mm/hugetlb: is_vm_hugetlb_page can be boolean mm/memory_hotplug: is_mem_section_removable can be boolean mm/vmalloc: is_vmalloc_addr can be boolean mm/lru:

[PATCH 3/5] mm/vmalloc: is_vmalloc_addr can be boolean

This patch makes is_vmalloc_addr return bool to improve readability due to this particular function only using either one or zero as its return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/mm.h | 4 ++-- 1 file changed, 2

[PATCH 5/5] mm/mempolicy: vma_migratable can be boolean

This patch makes vma_migratable return bool due to this particular function only using either one or zero as its return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/mempolicy.h | 10 +- 1 file changed, 5 insertions(+), 5

[PATCH 3/5] mm/vmalloc: is_vmalloc_addr can be boolean

This patch makes is_vmalloc_addr return bool to improve readability due to this particular function only using either one or zero as its return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/mm.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH 5/5] mm/mempolicy: vma_migratable can be boolean

This patch makes vma_migratable return bool due to this particular function only using either one or zero as its return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/mempolicy.h | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git

[PATCH 4/5] mm/lru: is_file/active_lru can be boolean

This patch makes is_file/active_lru return bool to improve readability due to these particular functions only using either one or zero as their return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/mmzone.h | 4 ++-- 1 file changed, 2

[PATCH 4/5] mm/lru: is_file/active_lru can be boolean

This patch makes is_file/active_lru return bool to improve readability due to these particular functions only using either one or zero as their return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/mmzone.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)

[PATCH 1/5] mm/hugetlb: is_vm_hugetlb_page can be boolean

This patch makes is_vm_hugetlb_page return bool to improve readability due to this particular function only using either one or zero as its return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/hugetlb_inline.h | 6 +++--- 1 file

[PATCH 1/5] mm/hugetlb: is_vm_hugetlb_page can be boolean

This patch makes is_vm_hugetlb_page return bool to improve readability due to this particular function only using either one or zero as its return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/hugetlb_inline.h | 6 +++--- 1 file changed, 3 insertions(+), 3

Re: [PATCH] Staging: fsl-mc: Fix up bad parameters to dev_err and dev_dbg

On Fri, Mar 18, 2016 at 06:29:01PM -0700, Guenter Roeck wrote: > The first parameter to dev_dbg() and dev_err() is struct device *, > not struct device **. > > Fixes: de71daf5c839 ("Staging: fsl-mc: Replace pr_debug with dev_dbg") > Fixes: 454b0ec8bf99 ("Staging: fsl-mc: Replace pr_err with

Re: [PATCH] Staging: fsl-mc: Fix up bad parameters to dev_err and dev_dbg

On Fri, Mar 18, 2016 at 06:29:01PM -0700, Guenter Roeck wrote: > The first parameter to dev_dbg() and dev_err() is struct device *, > not struct device **. > > Fixes: de71daf5c839 ("Staging: fsl-mc: Replace pr_debug with dev_dbg") > Fixes: 454b0ec8bf99 ("Staging: fsl-mc: Replace pr_err with

Re: [PATCH] KVM: page_track: fix access to NULL slot

On 03/23/2016 12:40 AM, Paolo Bonzini wrote: This happens when doing the reboot test from virt-tests: [ 131.833653] BUG: unable to handle kernel NULL pointer dereference at (null) [ 131.842461] IP: [] kvm_page_track_is_active+0x17/0x60 [kvm] [ 131.850500] PGD 0 [ 131.852763]

Re: [PATCH] KVM: page_track: fix access to NULL slot

On 03/23/2016 12:40 AM, Paolo Bonzini wrote: This happens when doing the reboot test from virt-tests: [ 131.833653] BUG: unable to handle kernel NULL pointer dereference at (null) [ 131.842461] IP: [] kvm_page_track_is_active+0x17/0x60 [kvm] [ 131.850500] PGD 0 [ 131.852763]

linux-next: Tree for Mar 23

Hi all, Please do not add any v4.7 related material to your linux-next included trees until after v4.6-rc1 is released. Changes since 20160322: Non-merge commits (relative to Linus' tree): 1734 1504 files changed, 102964 insertions(+), 28484 deletions

linux-next: Tree for Mar 23

Hi all, Please do not add any v4.7 related material to your linux-next included trees until after v4.6-rc1 is released. Changes since 20160322: Non-merge commits (relative to Linus' tree): 1734 1504 files changed, 102964 insertions(+), 28484 deletions

[PATCH v2] cpufreq: rockchip: add driver

This driver will directly use cpufreq-dt driver as backend. As there is not a generic devicetree board file(rockchip.c) on ARM64 architecture, so remove platform_device_register_simple in rockchip.c and add a new cpufreq driver to support Rockchip SoCs. Signed-off-by: Feng Xiao

[PATCH v2] cpufreq: rockchip: add driver

This driver will directly use cpufreq-dt driver as backend. As there is not a generic devicetree board file(rockchip.c) on ARM64 architecture, so remove platform_device_register_simple in rockchip.c and add a new cpufreq driver to support Rockchip SoCs. Signed-off-by: Feng Xiao Reviewed-by:

Re: [RFC 1/4] perf kvm: Enable 'record' on powerpc

Em Tue, Mar 22, 2016 at 04:12:11PM -0300, Arnaldo Carvalho de Melo escreveu: > Em Wed, Feb 24, 2016 at 02:37:42PM +0530, Ravi Bangoria escreveu: > > 'perf kvm record' is not available on powerpc because 'perf' relies on > > the 'cycles' event (a PMU event) to profile the guest. However, for > >

Re: [RFC 1/4] perf kvm: Enable 'record' on powerpc

Em Tue, Mar 22, 2016 at 04:12:11PM -0300, Arnaldo Carvalho de Melo escreveu: > Em Wed, Feb 24, 2016 at 02:37:42PM +0530, Ravi Bangoria escreveu: > > 'perf kvm record' is not available on powerpc because 'perf' relies on > > the 'cycles' event (a PMU event) to profile the guest. However, for > >

Re: RCU stall

On Tue, Mar 22, 2016 at 04:53:26PM -0700, Bart Van Assche wrote: > On 03/22/2016 01:45 PM, Paul E. McKenney wrote: > >You are getting a soft lockup as well as an RCU CPU stall warning, so > >it looks like something is taking a very long time in blk_done_softirq(). > > > >You have multiple

Re: RCU stall

On Tue, Mar 22, 2016 at 04:53:26PM -0700, Bart Van Assche wrote: > On 03/22/2016 01:45 PM, Paul E. McKenney wrote: > >You are getting a soft lockup as well as an RCU CPU stall warning, so > >it looks like something is taking a very long time in blk_done_softirq(). > > > >You have multiple

[lkp] [chrdev] af427b8e3a: kmsg.ide-tape:Failed_to_register_chrdev_interface

FYI, we noticed the below changes on https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git chrdev-warn commit af427b8e3a4e1fc4f7e893a617acf9520cdd616c ("chrdev: allocate dynamic chardevs in all unused holes") As below, the log "ide-tape: Failed to register chrdev interface"

[lkp] [chrdev] af427b8e3a: kmsg.ide-tape:Failed_to_register_chrdev_interface

FYI, we noticed the below changes on https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git chrdev-warn commit af427b8e3a4e1fc4f7e893a617acf9520cdd616c ("chrdev: allocate dynamic chardevs in all unused holes") As below, the log "ide-tape: Failed to register chrdev interface"

[PATCH 1/2] x86/apic: remove declaration of unused hw_nmi_is_cpu_stuck

Commit 10f9014912 ("x86: Cleanup hw_nmi.c cruft") removed unused code in the hw_nmi.c file because of the redesign of the hardlockup watchdog but left declaration of hw_nmi_is_cpu_stuck in linux/nmi.h, so remvoe it. Signed-off-by: Yaowei Bai ---

[PATCH 1/2] x86/apic: remove declaration of unused hw_nmi_is_cpu_stuck

Commit 10f9014912 ("x86: Cleanup hw_nmi.c cruft") removed unused code in the hw_nmi.c file because of the redesign of the hardlockup watchdog but left declaration of hw_nmi_is_cpu_stuck in linux/nmi.h, so remvoe it. Signed-off-by: Yaowei Bai --- include/linux/nmi.h | 1 - 1 file changed, 1

  1   2   3   4   5   6   7   8   9   10   >