Re: [PATCH v4] x86/suspend: fix false positive KASAN warning on suspend/resume

On 12/02/2016 08:42 PM, Josh Poimboeuf wrote: > Resuming from a suspend operation is showing a KASAN false positive > warning: > > BUG: KASAN: stack-out-of-bounds in unwind_get_return_address+0x11d/0x130 at > addr 8803867d7878 > Read of size 8 by task pm-suspend/7774 >

Re: [PATCH v4] x86/suspend: fix false positive KASAN warning on suspend/resume

On 12/02/2016 08:42 PM, Josh Poimboeuf wrote: > Resuming from a suspend operation is showing a KASAN false positive > warning: > > BUG: KASAN: stack-out-of-bounds in unwind_get_return_address+0x11d/0x130 at > addr 8803867d7878 > Read of size 8 by task pm-suspend/7774 >

Re: [PATCH v2] lkdtm: Add tests for LIST_POISON and ZERO_SIZE_PTR

Hi Michael, [auto build test ERROR on char-misc/char-misc-testing] [also build test ERROR on v4.9-rc7] [cannot apply to next-20161202] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Michael

Re: [PATCH v2] lkdtm: Add tests for LIST_POISON and ZERO_SIZE_PTR

Hi Michael, [auto build test ERROR on char-misc/char-misc-testing] [also build test ERROR on v4.9-rc7] [cannot apply to next-20161202] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Michael

3.5%LOAN OFFER

APPLY 3.5%LOAN.pdf Description: Adobe PDF document Application Form.pdf Description: Adobe PDF document

3.5%LOAN OFFER

APPLY 3.5%LOAN.pdf Description: Adobe PDF document Application Form.pdf Description: Adobe PDF document

Re: [PATCH] hotplug: make register and unregister notifier API symmetric

Hi Michal, [auto build test ERROR on linus/master] [also build test ERROR on v4.9-rc7 next-20161202] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Michal-Hocko/hotplug-make-register

Re: [PATCH] hotplug: make register and unregister notifier API symmetric

Hi Michal, [auto build test ERROR on linus/master] [also build test ERROR on v4.9-rc7 next-20161202] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Michal-Hocko/hotplug-make-register

[x86/asm] cdfac81296: kernel_BUG_at_arch/x86/kernel/alternative.c

FYI, we noticed the following commit: commit: cdfac8129693572ef91b9e7022d6ae07f1c8cc38 ("x86/asm: Rewrite sync_core() to use IRET-to-self") https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git x86/boot in testcase: boot on test machine: qemu-system-i386 -enable-kvm -smp 2 -m 256M

[x86/asm] cdfac81296: kernel_BUG_at_arch/x86/kernel/alternative.c

FYI, we noticed the following commit: commit: cdfac8129693572ef91b9e7022d6ae07f1c8cc38 ("x86/asm: Rewrite sync_core() to use IRET-to-self") https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git x86/boot in testcase: boot on test machine: qemu-system-i386 -enable-kvm -smp 2 -m 256M

Re: [PATCH v3] PCI/ACPI: xgene: Add ECAM quirk for X-Gene PCIe controller

On Fri, Dec 2, 2016 at 3:39 PM, Bjorn Helgaas wrote: > > On Thu, Dec 01, 2016 at 11:08:23PM -0500, Jon Masters wrote: > > Hi Bjorn, Duc, Mark, > > > > I switched my brain to the on mode and went and read some specs, and a few > > tables, so here's my 2 cents on this... > > > >

Re: [PATCH v3] PCI/ACPI: xgene: Add ECAM quirk for X-Gene PCIe controller

On Fri, Dec 2, 2016 at 3:39 PM, Bjorn Helgaas wrote: > > On Thu, Dec 01, 2016 at 11:08:23PM -0500, Jon Masters wrote: > > Hi Bjorn, Duc, Mark, > > > > I switched my brain to the on mode and went and read some specs, and a few > > tables, so here's my 2 cents on this... > > > > On 12/01/2016 06:22

Re: [PATCH] staging: Replaced BUG_ON with warnings

On Sat, Dec 3, 2016 at 12:32 PM, Shilpa Puttegowda wrote: > From: Shilpa P > > Don't crash the Kernel for driver errors > > Signed-off-by: Shilpa P > --- > drivers/staging/media/bcm2048/radio-bcm2048.c | 12 ++-- > 1 file

Re: [PATCH] staging: Replaced BUG_ON with warnings

On Sat, Dec 3, 2016 at 12:32 PM, Shilpa Puttegowda wrote: > From: Shilpa P > > Don't crash the Kernel for driver errors > > Signed-off-by: Shilpa P > --- > drivers/staging/media/bcm2048/radio-bcm2048.c | 12 ++-- > 1 file changed, 10 insertions(+), 2 deletions(-) > Acked-by: Allen

[PATCH] staging: Replaced BUG_ON with warnings

From: Shilpa P Don't crash the Kernel for driver errors Signed-off-by: Shilpa P --- drivers/staging/media/bcm2048/radio-bcm2048.c | 12 ++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git

[PATCH] staging: Replaced BUG_ON with warnings

From: Shilpa P Don't crash the Kernel for driver errors Signed-off-by: Shilpa P --- drivers/staging/media/bcm2048/radio-bcm2048.c | 12 ++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/drivers/staging/media/bcm2048/radio-bcm2048.c

Re: [PATCH 2/8] x86/head: Refactor 32-bit pgtable setup

On December 2, 2016 9:49:50 PM PST, Ingo Molnar wrote: > >* Boris Ostrovsky wrote: > >> > It is tricky to do so safely, because at this stage almost nothing >of the C >> > execution environment has been set up. > >Yeah - but we do have a fair amount

Re: [PATCH 2/8] x86/head: Refactor 32-bit pgtable setup

On December 2, 2016 9:49:50 PM PST, Ingo Molnar wrote: > >* Boris Ostrovsky wrote: > >> > It is tricky to do so safely, because at this stage almost nothing >of the C >> > execution environment has been set up. > >Yeah - but we do have a fair amount of early C code though. > >> I can still give

[PATCH] btrfs: limit async_work allocation and worker func duration

Problem statement: unprivileged user who has read-write access to more than one btrfs subvolume may easily consume all kernel memory (eventually triggering oom-killer). Reproducer (./mkrmdir below essentially loops over mkdir/rmdir): [root@kteam1 ~]# cat prep.sh DEV=/dev/sdb mkfs.btrfs -f $DEV

[PATCH] btrfs: limit async_work allocation and worker func duration

Problem statement: unprivileged user who has read-write access to more than one btrfs subvolume may easily consume all kernel memory (eventually triggering oom-killer). Reproducer (./mkrmdir below essentially loops over mkdir/rmdir): [root@kteam1 ~]# cat prep.sh DEV=/dev/sdb mkfs.btrfs -f $DEV

[PATCH] Fix style issues in kernel/cpu.c

This patch fixes style issues in kernel/cpu.c such as wrapping an 80 character line, calling EXPORT_SYMBOL() immediately after a function is defined, and whitespace and spacing issues. Signed-off-by: Thomas Casey --- kernel/cpu.c | 13 - 1 file changed, 8

[PATCH] Fix style issues in kernel/cpu.c

This patch fixes style issues in kernel/cpu.c such as wrapping an 80 character line, calling EXPORT_SYMBOL() immediately after a function is defined, and whitespace and spacing issues. Signed-off-by: Thomas Casey --- kernel/cpu.c | 13 - 1 file changed, 8 insertions(+), 5

Re: [PATCH 2/8] x86/head: Refactor 32-bit pgtable setup

* Boris Ostrovsky wrote: > > It is tricky to do so safely, because at this stage almost nothing of the C > > execution environment has been set up. Yeah - but we do have a fair amount of early C code though. > I can still give it a try but I'd rather not tie it to

Re: [PATCH 2/8] x86/head: Refactor 32-bit pgtable setup

* Boris Ostrovsky wrote: > > It is tricky to do so safely, because at this stage almost nothing of the C > > execution environment has been set up. Yeah - but we do have a fair amount of early C code though. > I can still give it a try but I'd rather not tie it to this (Xen PVH) patch >

Re: [PATCH] clk: Register clkdev after setup of fixed-rate and fixed-factor clocks

On 二, 11月 29, 2016 at 01:10:54下午 -0800, Stephen Boyd wrote: > On 11/24, Xiaolong Zhang wrote: > > On 三, 11月 23, 2016 at 04:38:33下午 -0800, Stephen Boyd wrote: > > > > > We're really off track now though. Can you please point to some > > > code that needs this change? If we're using DT then we

Re: [PATCH] clk: Register clkdev after setup of fixed-rate and fixed-factor clocks

On 二, 11月 29, 2016 at 01:10:54下午 -0800, Stephen Boyd wrote: > On 11/24, Xiaolong Zhang wrote: > > On 三, 11月 23, 2016 at 04:38:33下午 -0800, Stephen Boyd wrote: > > > > > We're really off track now though. Can you please point to some > > > code that needs this change? If we're using DT then we

Re: [PATCH] hotplug: make register and unregister notifier API symmetric

Hi Michal, [auto build test ERROR on linus/master] [also build test ERROR on v4.9-rc7 next-20161202] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Michal-Hocko/hotplug-make-register

Re: [PATCH] hotplug: make register and unregister notifier API symmetric

Hi Michal, [auto build test ERROR on linus/master] [also build test ERROR on v4.9-rc7 next-20161202] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Michal-Hocko/hotplug-make-register

Re: [PATCH 1/7] vfs - merge path_is_mountpoint() and path_is_mountpoint_rcu()

FWIW, I've folded that pile into vfs.git#work.autofs. Problems: * (fixed) __path_is_mountpoint() should _not_ treat NULL from __lookup_mnt() as "nothing's mounted there" until it has checked that mount_lock hadn't been touched - mount --move on something unrelated can race with

Re: [PATCH 1/7] vfs - merge path_is_mountpoint() and path_is_mountpoint_rcu()

FWIW, I've folded that pile into vfs.git#work.autofs. Problems: * (fixed) __path_is_mountpoint() should _not_ treat NULL from __lookup_mnt() as "nothing's mounted there" until it has checked that mount_lock hadn't been touched - mount --move on something unrelated can race with

Re: [PATCH 1/3] remoteproc: qcom: mdt_loader: add include for sizes

On Tue 22 Nov 09:02 PST 2016, Stanimir Varbanov wrote: > Add linux/sizes.h to prevent build failure on non ARM architectures > as: > > CC [M] drivers/remoteproc/qcom_mdt_loader.o > In file included from include/linux/cache.h:4:0, > from include/linux/printk.h:8, >

Re: [PATCH 1/3] remoteproc: qcom: mdt_loader: add include for sizes

On Tue 22 Nov 09:02 PST 2016, Stanimir Varbanov wrote: > Add linux/sizes.h to prevent build failure on non ARM architectures > as: > > CC [M] drivers/remoteproc/qcom_mdt_loader.o > In file included from include/linux/cache.h:4:0, > from include/linux/printk.h:8, >

[PATCH] remoteproc: Remove "experimental" warning

Warning users that remoteproc and it's binary format are under development doesn't serve much of a purpose. Different drivers support different image formats and the resource table has a version field that would need to be bumped when incompatible changes are introduced. So lets drop this warning

[PATCH] remoteproc: Remove "experimental" warning

Warning users that remoteproc and it's binary format are under development doesn't serve much of a purpose. Different drivers support different image formats and the resource table has a version field that would need to be bumped when incompatible changes are introduced. So lets drop this warning

Re: [RFC, PATCH, v3.9] default exported asm symbols to zero

On Fri, 2016-12-02 at 13:40 +0100, Arnd Bergmann wrote: > With binutils-2.16 and before, a weak missing symbol was kept during the > final link, and a missing CRC for an export would lead to that CRC > being treated as zero implicitly. With binutils-2.17, the crc > symbol gets dropped, and any

Re: [RFC, PATCH, v3.9] default exported asm symbols to zero

On Fri, 2016-12-02 at 13:40 +0100, Arnd Bergmann wrote: > With binutils-2.16 and before, a weak missing symbol was kept during the > final link, and a missing CRC for an export would lead to that CRC > being treated as zero implicitly. With binutils-2.17, the crc > symbol gets dropped, and any

Re: [PATCH] blk-stat: fix a typo

On 12/02/2016 08:16 PM, Jens Axboe wrote: > On 12/02/2016 06:13 PM, Shaohua Li wrote: >> Signed-off-by: Shaohua Li >> --- >> block/blk-stat.c | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/block/blk-stat.c b/block/blk-stat.c >> index 688c958..4d01185

Re: [PATCH] blk-stat: fix a typo

On 12/02/2016 08:16 PM, Jens Axboe wrote: > On 12/02/2016 06:13 PM, Shaohua Li wrote: >> Signed-off-by: Shaohua Li >> --- >> block/blk-stat.c | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/block/blk-stat.c b/block/blk-stat.c >> index 688c958..4d01185 100644 >> ---

Re: [PATCH] Revert "Btrfs: don't delay inode ref updates during log, replay"

Whoops, the [PATCH] line should've specified more clearly: This only applies to linux-stable, 3.12.y. Sorry for any confusion. -Jeff On 12/2/16 10:21 PM, Jeff Mahoney wrote: > This reverts commit 644d10716875b24388680925d6c7502420987bfe. > > The original patch for mainline, 6f8960541b1

Re: [PATCH] Revert "Btrfs: don't delay inode ref updates during log, replay"

Whoops, the [PATCH] line should've specified more clearly: This only applies to linux-stable, 3.12.y. Sorry for any confusion. -Jeff On 12/2/16 10:21 PM, Jeff Mahoney wrote: > This reverts commit 644d10716875b24388680925d6c7502420987bfe. > > The original patch for mainline, 6f8960541b1

Re: [PATCH 2/2 v2] sched: use load_avg for selecting idlest group

On Fri, Nov 25, 2016 at 7:34 AM, Vincent Guittot wrote: > > find_idlest_group() only compares the runnable_load_avg when looking for > the least loaded group. But on fork intensive use case like hackbench > where tasks blocked quickly after the fork, this can lead to

Re: [PATCH 2/2 v2] sched: use load_avg for selecting idlest group

On Fri, Nov 25, 2016 at 7:34 AM, Vincent Guittot wrote: > > find_idlest_group() only compares the runnable_load_avg when looking for > the least loaded group. But on fork intensive use case like hackbench > where tasks blocked quickly after the fork, this can lead to selecting the > same CPU

[PATCH] Revert "Btrfs: don't delay inode ref updates during log, replay"

This reverts commit 644d10716875b24388680925d6c7502420987bfe. The original patch for mainline, 6f8960541b1 (Btrfs: don't delay inode ref updates during log replay) lists 1d52c78afbb (Btrfs: try not to ENOSPC on log replay) as the only pre-3.18 dependency, but it also depends on 67de11769bd

[PATCH] Revert "Btrfs: don't delay inode ref updates during log, replay"

This reverts commit 644d10716875b24388680925d6c7502420987bfe. The original patch for mainline, 6f8960541b1 (Btrfs: don't delay inode ref updates during log replay) lists 1d52c78afbb (Btrfs: try not to ENOSPC on log replay) as the only pre-3.18 dependency, but it also depends on 67de11769bd

Re: [PATCH] blk-stat: fix a typo

On 12/02/2016 06:13 PM, Shaohua Li wrote: > Signed-off-by: Shaohua Li > --- > block/blk-stat.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/block/blk-stat.c b/block/blk-stat.c > index 688c958..4d01185 100644 > --- a/block/blk-stat.c > +++

Re: [PATCH] blk-stat: fix a typo

On 12/02/2016 06:13 PM, Shaohua Li wrote: > Signed-off-by: Shaohua Li > --- > block/blk-stat.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/block/blk-stat.c b/block/blk-stat.c > index 688c958..4d01185 100644 > --- a/block/blk-stat.c > +++ b/block/blk-stat.c > @@

Re: [mnt] 81e3bb1b6f: BUG:sleeping_function_called_from_invalid_context_at_fs/dcache.c

kernel test robot writes: > FYI, we noticed the following commit: > > commit: 81e3bb1b6f6d84d47e773f34a14b0955e528c6eb ("mnt: Tuck mounts under > others instead of creating shadow/side mounts.") > https://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git

Re: [mnt] 81e3bb1b6f: BUG:sleeping_function_called_from_invalid_context_at_fs/dcache.c

kernel test robot writes: > FYI, we noticed the following commit: > > commit: 81e3bb1b6f6d84d47e773f34a14b0955e528c6eb ("mnt: Tuck mounts under > others instead of creating shadow/side mounts.") > https://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git > for-testing > > in

Re: [PATCH 39/39] mtd: nand: denali_dt: add compatible strings for UniPhier SoC variants

On 12/03/2016 03:41 AM, Masahiro Yamada wrote: > Hi Rob, Hi! > 2016-12-03 1:26 GMT+09:00 Rob Herring : > >>> >>> >>> (Plan A) >>> "denali,socfpga-nand" (for Altera SOCFPGA variant) >>> "denali,uniphier-nand-v1" (for old Socionext UniPhier family >>>

Re: [PATCH 39/39] mtd: nand: denali_dt: add compatible strings for UniPhier SoC variants

On 12/03/2016 03:41 AM, Masahiro Yamada wrote: > Hi Rob, Hi! > 2016-12-03 1:26 GMT+09:00 Rob Herring : > >>> >>> >>> (Plan A) >>> "denali,socfpga-nand" (for Altera SOCFPGA variant) >>> "denali,uniphier-nand-v1" (for old Socionext UniPhier family >>> variant) >>>

Re: [PATCH 39/39] mtd: nand: denali_dt: add compatible strings for UniPhier SoC variants

Hi Rob, 2016-12-03 1:26 GMT+09:00 Rob Herring : >> >> >> (Plan A) >> "denali,socfpga-nand" (for Altera SOCFPGA variant) >> "denali,uniphier-nand-v1" (for old Socionext UniPhier family variant) >> "denali,uniphier-nand-v2" (for new Socionext UniPhier

Re: [PATCH 39/39] mtd: nand: denali_dt: add compatible strings for UniPhier SoC variants

Hi Rob, 2016-12-03 1:26 GMT+09:00 Rob Herring : >> >> >> (Plan A) >> "denali,socfpga-nand" (for Altera SOCFPGA variant) >> "denali,uniphier-nand-v1" (for old Socionext UniPhier family variant) >> "denali,uniphier-nand-v2" (for new Socionext UniPhier family variant) >>

[PATCH linux-firmware 1/2] WHENCE: Add new amdgpu firmware

Missed in commit 9c011a98a94ab1320f6c073ae500ae4dc33ce838. Signed-off-by: Ben Hutchings --- Please run 'make check' before committing to catch this sort of error. Ben. WHENCE | 2 ++ 1 file changed, 2 insertions(+) diff --git a/WHENCE b/WHENCE index

[PATCH linux-firmware 1/2] WHENCE: Add new amdgpu firmware

Missed in commit 9c011a98a94ab1320f6c073ae500ae4dc33ce838. Signed-off-by: Ben Hutchings --- Please run 'make check' before committing to catch this sort of error. Ben. WHENCE | 2 ++ 1 file changed, 2 insertions(+) diff --git a/WHENCE b/WHENCE index e731c68f309d..a7fc762dff64 100644 ---

Re: [PATCH] net: wireless: realtek: constify rate_control_ops structures

On Sat, Dec 3, 2016 at 2:09 AM, Larry Finger wrote: > On 12/02/2016 03:50 AM, Bhumika Goyal wrote: >> >> The structures rate_control_ops are only passed as an argument to the >> functions ieee80211_rate_control_{register/unregister}. This argument is >> of type const,

Re: [PATCH] net: wireless: realtek: constify rate_control_ops structures

On Sat, Dec 3, 2016 at 2:09 AM, Larry Finger wrote: > On 12/02/2016 03:50 AM, Bhumika Goyal wrote: >> >> The structures rate_control_ops are only passed as an argument to the >> functions ieee80211_rate_control_{register/unregister}. This argument is >> of type const, so rate_control_ops having

[PATCH linux-firmware 2/2] WHENCE: Add new snd_intel_sst_core

Missed in commit 128052ee31f7023b07c5d65c2212abce6e52076c. Signed-off-by: Ben Hutchings --- Please run 'make check' before committing to catch this sort of error. Ben. WHENCE | 1 + 1 file changed, 1 insertion(+) diff --git a/WHENCE b/WHENCE index

[PATCH linux-firmware 2/2] WHENCE: Add new snd_intel_sst_core

Missed in commit 128052ee31f7023b07c5d65c2212abce6e52076c. Signed-off-by: Ben Hutchings --- Please run 'make check' before committing to catch this sort of error. Ben. WHENCE | 1 + 1 file changed, 1 insertion(+) diff --git a/WHENCE b/WHENCE index a7fc762dff64..d021c40c5169 100644 ---

[mnt] 81e3bb1b6f: BUG:sleeping_function_called_from_invalid_context_at_fs/dcache.c

FYI, we noticed the following commit: commit: 81e3bb1b6f6d84d47e773f34a14b0955e528c6eb ("mnt: Tuck mounts under others instead of creating shadow/side mounts.") https://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git for-testing in testcase: boot on test machine:

[mnt] 81e3bb1b6f: BUG:sleeping_function_called_from_invalid_context_at_fs/dcache.c

FYI, we noticed the following commit: commit: 81e3bb1b6f6d84d47e773f34a14b0955e528c6eb ("mnt: Tuck mounts under others instead of creating shadow/side mounts.") https://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git for-testing in testcase: boot on test machine:

[PATCH v2 2/3] locking/percpu-rwsem: Rework writer block/wake to not use wait-queues

The use of any kind of wait queue is an overkill for pcpu-rwsems. While one option would be to use the less heavy simple (swait) flavor, this is still too much for what pcpu-rwsems needs. For one, we do not care about any sort of queuing in that the only (rare) time writers (and readers, for that

[PATCH v2 2/3] locking/percpu-rwsem: Rework writer block/wake to not use wait-queues

The use of any kind of wait queue is an overkill for pcpu-rwsems. While one option would be to use the less heavy simple (swait) flavor, this is still too much for what pcpu-rwsems needs. For one, we do not care about any sort of queuing in that the only (rare) time writers (and readers, for that

Re: [PATCH v9 07/16] drivers: acpi: implement acpi_dma_configure

On Fri, Dec 2, 2016 at 4:38 PM, Lorenzo Pieralisi wrote: > Rafael, Mark, Suravee, > > On Mon, Nov 21, 2016 at 10:01:39AM +, Lorenzo Pieralisi wrote: >> On DT based systems, the of_dma_configure() API implements DMA >> configuration for a given device. On ACPI

Re: [PATCH v9 07/16] drivers: acpi: implement acpi_dma_configure

On Fri, Dec 2, 2016 at 4:38 PM, Lorenzo Pieralisi wrote: > Rafael, Mark, Suravee, > > On Mon, Nov 21, 2016 at 10:01:39AM +, Lorenzo Pieralisi wrote: >> On DT based systems, the of_dma_configure() API implements DMA >> configuration for a given device. On ACPI systems an API equivalent to >>

[PATCH] net: ethernet: ti: cpdma: use desc_read in chan_process instead of raw read

There is desc_read() macros to read desc fields, so no need to use __raw_readl(); Signed-off-by: Ivan Khoronzhuk --- Based on net-next/master drivers/net/ethernet/ti/davinci_cpdma.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] net: ethernet: ti: cpdma: use desc_read in chan_process instead of raw read

There is desc_read() macros to read desc fields, so no need to use __raw_readl(); Signed-off-by: Ivan Khoronzhuk --- Based on net-next/master drivers/net/ethernet/ti/davinci_cpdma.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/ethernet/ti/davinci_cpdma.c

Re: [PATCH v2] ACPI: Document _OSI and _REV for Linux BIOS writers

On Friday, December 02, 2016 09:14:48 PM Lukas Wunner wrote: > On Wed, Nov 30, 2016 at 11:00:30PM -0500, Len Brown wrote: > > From: Len Brown > > > > Based on a recent session at the Linux Plumber's Conference, > > we need to be more clear about how a BIOS should use _OSI >

Re: [PATCH v2] ACPI: Document _OSI and _REV for Linux BIOS writers

On Friday, December 02, 2016 09:14:48 PM Lukas Wunner wrote: > On Wed, Nov 30, 2016 at 11:00:30PM -0500, Len Brown wrote: > > From: Len Brown > > > > Based on a recent session at the Linux Plumber's Conference, > > we need to be more clear about how a BIOS should use _OSI > > to properly support

Re: include/linux/rtmutex.h: NOOP rt_mutex_destroy if !CONFIG_DEBUG_RT_MUTEXES

This seems consistent with the spirit of DEBUG_MUTEX in non-RT kernels, so hopefully this is acceptable to the RT maintainers. Reviewed-by: Andy Ritger Thanks, - Andy On Tue, Oct 25, 2016 at 07:03:51PM -0700, Alex Goins wrote: > mutex_destroy is no-op inline when

Re: include/linux/rtmutex.h: NOOP rt_mutex_destroy if !CONFIG_DEBUG_RT_MUTEXES

This seems consistent with the spirit of DEBUG_MUTEX in non-RT kernels, so hopefully this is acceptable to the RT maintainers. Reviewed-by: Andy Ritger Thanks, - Andy On Tue, Oct 25, 2016 at 07:03:51PM -0700, Alex Goins wrote: > mutex_destroy is no-op inline when DEBUG_MUTEX is not enabled.

Re: [PATCH] drm/i915: Remove instructions to file a bug report.

On Fri, Dec 2, 2016 at 5:03 PM, Matt Turner wrote: > From these instructions, users assume that /sys/class/drm/card0/error > contains all the information a developer needs to diagnose and fix a GPU > hang. > > In fact it doesn't, and we have no tools for solving them (other

Re: [PATCH] drm/i915: Remove instructions to file a bug report.

On Fri, Dec 2, 2016 at 5:03 PM, Matt Turner wrote: > From these instructions, users assume that /sys/class/drm/card0/error > contains all the information a developer needs to diagnose and fix a GPU > hang. > > In fact it doesn't, and we have no tools for solving them (other than > stabbing in the

Re: [PATCH] clk: uniphier: Fix build with gcc-4.4.

Hi Vinson, 2016-12-03 9:37 GMT+09:00 Vinson Lee : > gcc-4.4 has issues with anonymous unions in initializers. > > CC drivers/clk/uniphier/clk-uniphier-sys.o > drivers/clk/uniphier/clk-uniphier-sys.c:45: error: unknown field ‘factor’ > specified in initializer > >

Re: [PATCH] clk: uniphier: Fix build with gcc-4.4.

Hi Vinson, 2016-12-03 9:37 GMT+09:00 Vinson Lee : > gcc-4.4 has issues with anonymous unions in initializers. > > CC drivers/clk/uniphier/clk-uniphier-sys.o > drivers/clk/uniphier/clk-uniphier-sys.c:45: error: unknown field ‘factor’ > specified in initializer > > Fixes: 1574d5722636

Re: [PATCH net-next] liquidio: 'imply' ptp instead of 'select'

Hi Arnd, [auto build test ERROR on net-next/master] url: https://github.com/0day-ci/linux/commits/Arnd-Bergmann/liquidio-imply-ptp-instead-of-select/20161203-084019 config: x86_64-allmodconfig compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901 reproduce: make ARCH=x86_64 allmodconfig

Re: [PATCH net-next] liquidio: 'imply' ptp instead of 'select'

Hi Arnd, [auto build test ERROR on net-next/master] url: https://github.com/0day-ci/linux/commits/Arnd-Bergmann/liquidio-imply-ptp-instead-of-select/20161203-084019 config: x86_64-allmodconfig compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901 reproduce: make ARCH=x86_64 allmodconfig

[PATCH 20/22] staging: lustre: osc: set lock data for readahead lock

From: Jinshan Xiong If osc_io_readahead() finds a lock that belongs to the previous instance of osc_object, the lock data pointer will be null. It has to instantiate with new instance otherwise those pages won't be destroyed at lock cancel, and then finally hit the

[PATCH 20/22] staging: lustre: osc: set lock data for readahead lock

From: Jinshan Xiong If osc_io_readahead() finds a lock that belongs to the previous instance of osc_object, the lock data pointer will be null. It has to instantiate with new instance otherwise those pages won't be destroyed at lock cancel, and then finally hit the assertion in

[PATCH 14/22] staging: lustre: obd: add callback for llog_cat_process_or_fork

From: Alexander Boyko Currently llog_process_or_fork() is hard coded to always pass the function pointer llog_cat_process_cb(). Change llog_cat_process_or_fork() to pass in any function pointer which will allow us more options for llog_cat callback routines in the

[PATCH 14/22] staging: lustre: obd: add callback for llog_cat_process_or_fork

From: Alexander Boyko Currently llog_process_or_fork() is hard coded to always pass the function pointer llog_cat_process_cb(). Change llog_cat_process_or_fork() to pass in any function pointer which will allow us more options for llog_cat callback routines in the future. Signed-off-by:

[PATCH] blk-stat: fix a typo

Signed-off-by: Shaohua Li --- block/blk-stat.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/block/blk-stat.c b/block/blk-stat.c index 688c958..4d01185 100644 --- a/block/blk-stat.c +++ b/block/blk-stat.c @@ -12,7 +12,7 @@ static void

[PATCH] blk-stat: fix a typo

Signed-off-by: Shaohua Li --- block/blk-stat.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/block/blk-stat.c b/block/blk-stat.c index 688c958..4d01185 100644 --- a/block/blk-stat.c +++ b/block/blk-stat.c @@ -12,7 +12,7 @@ static void blk_stat_flush_batch(struct

Re: [PATCH] usb: dwc2: fix flags for DMA descriptor allocation in dwc2_hsotg_ep_enable

On 12/1/2016 1:02 AM, Marek Szyprowski wrote: > dwc2_hsotg_ep_enable can be called from interrupt context, so all > allocations should be done with GFP_ATOMIC flags. This fixes following > issue on ARM architecture: > > [] (unwind_backtrace) from [] (show_stack+0x10/0x14) > [] (show_stack) from

Re: [PATCH] usb: dwc2: fix flags for DMA descriptor allocation in dwc2_hsotg_ep_enable

On 12/1/2016 1:02 AM, Marek Szyprowski wrote: > dwc2_hsotg_ep_enable can be called from interrupt context, so all > allocations should be done with GFP_ATOMIC flags. This fixes following > issue on ARM architecture: > > [] (unwind_backtrace) from [] (show_stack+0x10/0x14) > [] (show_stack) from

[PATCH 07/22] staging: lustre: obdclass: lu_site_purge() to handle purge-all

From: Alex Zhuravlev if the callers wants to purge all objects, then scanning should start from the first bucket. Signed-off-by: Alex Zhuravlev Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7038 Reviewed-on:

[PATCH 07/22] staging: lustre: obdclass: lu_site_purge() to handle purge-all

From: Alex Zhuravlev if the callers wants to purge all objects, then scanning should start from the first bucket. Signed-off-by: Alex Zhuravlev Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7038 Reviewed-on: http://review.whamcloud.com/18505 Reviewed-by: Mike Pershin Reviewed-by:

Re: [RFC][PATCH 1/3] phy: phy-hi6220-usb: Wire up extconn support to hikey's phy driver

On 12/1/2016 12:12 PM, John Stultz wrote: > On Thu, Dec 1, 2016 at 12:23 AM, Kishon Vijay Abraham I wrote: >> Hi, >> >> On Wednesday 23 November 2016 09:16 AM, John Stultz wrote: >>> This wires extconn support to hikey's phy driver, and >>> connects it to the usb UDC layer via a

Re: [RFC][PATCH 1/3] phy: phy-hi6220-usb: Wire up extconn support to hikey's phy driver

On 12/1/2016 12:12 PM, John Stultz wrote: > On Thu, Dec 1, 2016 at 12:23 AM, Kishon Vijay Abraham I wrote: >> Hi, >> >> On Wednesday 23 November 2016 09:16 AM, John Stultz wrote: >>> This wires extconn support to hikey's phy driver, and >>> connects it to the usb UDC layer via a usb_phy

[PATCH 21/22] staging: lustre: remove set but unused variables

From: Yang Sheng Remove set but unused variables in nidstring.c and osc_request.c as reported by make W=1. Signed-off-by: Yang Sheng Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8378 Reviewed-on: http://review.whamcloud.com/23221 Reviewed-by:

[PATCH 17/22] staging: lustre: clio: remove mtime check in vvp_io_fault_start()

From: Bobi Jam In fault IO initialization, inode's mtime is saved, and after getting locks, when the IO is about to start, vvp_io_fault_start() checks the mtime's intactness. It's a false alarm, since the timestamp from MDS could be stale, we maintain mtime mainly on OST

[PATCH 18/22] staging: lustre: import: don't reconnect during connect interpret

From: Mikhal Pershin The import connect flags might be cleared by ptlrpc_connect_import() wrongly if there is still connect interpret function is running. Use imp_connected boolean variable to indicate that we are still interpretting connect reply and don't try to

[PATCH 21/22] staging: lustre: remove set but unused variables

From: Yang Sheng Remove set but unused variables in nidstring.c and osc_request.c as reported by make W=1. Signed-off-by: Yang Sheng Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8378 Reviewed-on: http://review.whamcloud.com/23221 Reviewed-by: Bob Glossman Reviewed-by: Emoly Liu

[PATCH 17/22] staging: lustre: clio: remove mtime check in vvp_io_fault_start()

From: Bobi Jam In fault IO initialization, inode's mtime is saved, and after getting locks, when the IO is about to start, vvp_io_fault_start() checks the mtime's intactness. It's a false alarm, since the timestamp from MDS could be stale, we maintain mtime mainly on OST objects, and if the

[PATCH 18/22] staging: lustre: import: don't reconnect during connect interpret

From: Mikhal Pershin The import connect flags might be cleared by ptlrpc_connect_import() wrongly if there is still connect interpret function is running. Use imp_connected boolean variable to indicate that we are still interpretting connect reply and don't try to reconnect until it ends.

[PATCH 16/22] staging: lustre: llite: Invoke file_update_time in page_mkwrite

From: Yang Sheng Only update file times if page_mkwrite is not set. So we need call file_update_time by ourselves. Signed-off-by: Yang Sheng Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-1118 Reviewed-on: http://review.whamcloud.com/18683

[PATCH 15/22] staging: lustre: rpc: increase bulk size

From: Jinshan Xiong To make the ptlrpc be able to size 16MB IO Signed-off-by: Jinshan Xiong Signed-off-by: Gu Zheng Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7990 Reviewed-on: http://review.whamcloud.com/19366

[PATCH 22/22] staging: lustre: libcfs: remove lnet upcall code

From: Alexander Zarochentsev Removing lnet upcall infrastructure completely as nobody uses it anymore. The upcall causes a delay before calling BUG() and might even cause a hang making getting a crash dump unreliable or containing outdated info.

[PATCH 16/22] staging: lustre: llite: Invoke file_update_time in page_mkwrite

From: Yang Sheng Only update file times if page_mkwrite is not set. So we need call file_update_time by ourselves. Signed-off-by: Yang Sheng Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-1118 Reviewed-on: http://review.whamcloud.com/18683 Reviewed-by: Andreas Dilger Reviewed-by: Niu

[PATCH 15/22] staging: lustre: rpc: increase bulk size

From: Jinshan Xiong To make the ptlrpc be able to size 16MB IO Signed-off-by: Jinshan Xiong Signed-off-by: Gu Zheng Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7990 Reviewed-on: http://review.whamcloud.com/19366 Reviewed-by: Oleg Drokin Signed-off-by: James Simmons ---

[PATCH 22/22] staging: lustre: libcfs: remove lnet upcall code

From: Alexander Zarochentsev Removing lnet upcall infrastructure completely as nobody uses it anymore. The upcall causes a delay before calling BUG() and might even cause a hang making getting a crash dump unreliable or containing outdated info. Signed-off-by: Alexander Zarochentsev

  1   2   3   4   5   6   7   8   9   10   >