RE: [PATCH v2 1/5] ramoops: use persistent_ram_free() instead of kfree() for freeing prz

Hi, > -Original Message- > From: keesc...@google.com [mailto:keesc...@google.com] On Behalf Of Kees > Cook > Sent: Friday, July 29, 2016 4:35 AM > To: 岩松信洋 / IWAMATSU，NOBUHIRO > Cc: Anton Vorontsov; Colin Cross; Tony Luck; LKML; Hiraku Toyooka; Mark > Salyzyn; 阿口誠司 / AGUCHI，SEIJI >

RE: [PATCH v2 1/5] ramoops: use persistent_ram_free() instead of kfree() for freeing prz

Hi, > -Original Message- > From: keesc...@google.com [mailto:keesc...@google.com] On Behalf Of Kees > Cook > Sent: Friday, July 29, 2016 4:35 AM > To: 岩松信洋 / IWAMATSU，NOBUHIRO > Cc: Anton Vorontsov; Colin Cross; Tony Luck; LKML; Hiraku Toyooka; Mark > Salyzyn; 阿口誠司 / AGUCHI，SEIJI >

Re: [PATCH] regulator: axp20x: support AXP813 variant

On Thu, 28 Jul 2016 22:19:44 +0200 Maxime Ripard wrote: > > Documentation/devicetree/bindings/mfd/axp20x.txt | 32 - > > drivers/mfd/axp20x-rsb.c | 1 + > > drivers/mfd/axp20x.c | 3 + > >

Re: [PATCH] regulator: axp20x: support AXP813 variant

On Thu, 28 Jul 2016 22:19:44 +0200 Maxime Ripard wrote: > > Documentation/devicetree/bindings/mfd/axp20x.txt | 32 - > > drivers/mfd/axp20x-rsb.c | 1 + > > drivers/mfd/axp20x.c | 3 + > > drivers/regulator/axp20x-regulator.c

Re: [PATCH 00/13] arm64: Allwinner A64 support based on sunxi-ng

On Thu, 28 Jul 2016 22:07:05 +0200 Maxime Ripard wrote: > > > Let me know what you think, > > > > I don't see the interest to have common code for 32bits and 64bits. > > The clock driver of a SoC will never evolve, so, it is simpler to > > copy the source

Re: [PATCH 00/13] arm64: Allwinner A64 support based on sunxi-ng

On Thu, 28 Jul 2016 22:07:05 +0200 Maxime Ripard wrote: > > > Let me know what you think, > > > > I don't see the interest to have common code for 32bits and 64bits. > > The clock driver of a SoC will never evolve, so, it is simpler to > > copy the source common with the H3 into a clean A64

Re: Build failure in linux mainline when building arcv2 images

Hi Guenter, On 07/28/2016 08:23 PM, Guenter Roeck wrote: > Hi Vineet, > > Mainline fails to build arcv2 images with the following error. > > {standard input}: Assembler messages: > {standard input}:19174: Error: Instruction with long immediate data in delay > slot > make[2]: ***

Re: Build failure in linux mainline when building arcv2 images

Hi Guenter, On 07/28/2016 08:23 PM, Guenter Roeck wrote: > Hi Vineet, > > Mainline fails to build arcv2 images with the following error. > > {standard input}: Assembler messages: > {standard input}:19174: Error: Instruction with long immediate data in delay > slot > make[2]: ***

Re: [PATCH v2 4/4] ARM: OMAP2+: omap_device: fix crash on omap_device removal

On 07/28/16 20:50, Grygorii Strashko wrote: > Below call chain causes system crash when OMAP device is > removed by calling of_platform_depopulate()/device_del(): Should you swap 3 <-> 4 in the series? Currently patch 3 will introduce the crash you are fixing in patch 4... > > device_del() > -

Re: [PATCH v2 4/4] ARM: OMAP2+: omap_device: fix crash on omap_device removal

On 07/28/16 20:50, Grygorii Strashko wrote: > Below call chain causes system crash when OMAP device is > removed by calling of_platform_depopulate()/device_del(): Should you swap 3 <-> 4 in the series? Currently patch 3 will introduce the crash you are fixing in patch 4... > > device_del() > -

linux-next: Tree for Jul 29

Hi all, Please do not add material destined for v4.9 to your linux-next included branches until after v4.8-rc1 has been released. Changes since 20160728: The vfs tree gained a build failure due to an interaction with Linus' tree. I applied a merge fix patch. The drm tree gained a conflict

linux-next: Tree for Jul 29

Hi all, Please do not add material destined for v4.9 to your linux-next included branches until after v4.8-rc1 has been released. Changes since 20160728: The vfs tree gained a build failure due to an interaction with Linus' tree. I applied a merge fix patch. The drm tree gained a conflict

RE: [PATCH] ACPICA: cleanup method properly on error

Hi, Vegard > From: linux-acpi-ow...@vger.kernel.org [mailto:linux-acpi- > ow...@vger.kernel.org] On Behalf Of Vegard Nossum > Subject: [PATCH] ACPICA: cleanup method properly on error > > If the call to acpi_ds_init_aml_walk() fails, then we have to undo the > walk state push done by

RE: [PATCH] ACPICA: cleanup method properly on error

Hi, Vegard > From: linux-acpi-ow...@vger.kernel.org [mailto:linux-acpi- > ow...@vger.kernel.org] On Behalf Of Vegard Nossum > Subject: [PATCH] ACPICA: cleanup method properly on error > > If the call to acpi_ds_init_aml_walk() fails, then we have to undo the > walk state push done by

Re: [PATCH] sparc64 mm: Fix base TSB sizing when hugetlb pages are used

From: Mike Kravetz Date: Fri, 15 Jul 2016 13:08:42 -0700 > do_sparc64_fault() calculates both the base and huge page RSS sizes and > uses this information in calls to tsb_grow(). The calculation for base > page TSB size is not correct if the task uses hugetlb pages.

Re: [PATCH] sparc64 mm: Fix base TSB sizing when hugetlb pages are used

From: Mike Kravetz Date: Fri, 15 Jul 2016 13:08:42 -0700 > do_sparc64_fault() calculates both the base and huge page RSS sizes and > uses this information in calls to tsb_grow(). The calculation for base > page TSB size is not correct if the task uses hugetlb pages. hugetlb > pages are not

[PATCH 2/3] mpt3sas: Eliminate dead sleep_flag code

With the exception of a single call to wait_for_doorbell_int(), all this conditional sleeping code is dead. So delete it. Signed-off-by: Calvin Owens --- drivers/scsi/mpt3sas/mpt3sas_base.c | 241 +-- drivers/scsi/mpt3sas/mpt3sas_base.h

[PATCH 2/3] mpt3sas: Eliminate dead sleep_flag code

With the exception of a single call to wait_for_doorbell_int(), all this conditional sleeping code is dead. So delete it. Signed-off-by: Calvin Owens --- drivers/scsi/mpt3sas/mpt3sas_base.c | 241 +-- drivers/scsi/mpt3sas/mpt3sas_base.h | 6 +-

[PATCH 1/3] mpt3sas: Eliminate conditional locking in mpt3sas_scsih_issue_tm()

This flag that conditionally acquires the mutex is confusing and prone to bugginess: refactor it into two separate function calls, and make the unlocked one complain if it's called outside the mutex. Signed-off-by: Calvin Owens --- drivers/scsi/mpt3sas/mpt3sas_base.h | 16

[PATCH 3/3] mpt3sas: Fix warnings exposed by W=1

Trivial non-functional changes for a couple annoying things: 1) Functions local to files are not declared static, which is frustrating when reading the code because it's non-obvious at first glance what's actually called from other files. 2) Set-but-unused variables abound, presumably to

[PATCH 1/3] mpt3sas: Eliminate conditional locking in mpt3sas_scsih_issue_tm()

This flag that conditionally acquires the mutex is confusing and prone to bugginess: refactor it into two separate function calls, and make the unlocked one complain if it's called outside the mutex. Signed-off-by: Calvin Owens --- drivers/scsi/mpt3sas/mpt3sas_base.h | 16 +++--

[PATCH 3/3] mpt3sas: Fix warnings exposed by W=1

Trivial non-functional changes for a couple annoying things: 1) Functions local to files are not declared static, which is frustrating when reading the code because it's non-obvious at first glance what's actually called from other files. 2) Set-but-unused variables abound, presumably to

RE: [PATCH] ACPI / button: remove pointer to old lid_sysfs on unbind

Hi, Benjamin > From: linux-acpi-ow...@vger.kernel.org [mailto:linux-acpi- > ow...@vger.kernel.org] On Behalf Of Benjamin Tissoires > Subject: [PATCH] ACPI / button: remove pointer to old lid_sysfs on unbind > > When we removed the procfs dir on error or if the driver is > unbound, the two

RE: [PATCH] ACPI / button: remove pointer to old lid_sysfs on unbind

Hi, Benjamin > From: linux-acpi-ow...@vger.kernel.org [mailto:linux-acpi- > ow...@vger.kernel.org] On Behalf Of Benjamin Tissoires > Subject: [PATCH] ACPI / button: remove pointer to old lid_sysfs on unbind > > When we removed the procfs dir on error or if the driver is > unbound, the two

Re: [Regression?] fib_rules: Added NLM_F_EXCL support to fib_nl_newrule breaks Android userspace

From: John Stultz Date: Thu, 28 Jul 2016 21:18:16 -0700 > After moving my HiKey tree to pre-v4.8-rc, I noticed when using > Android that I was getting routing errors after toggling networking on > and off (or entering suspend). Wifi associated, but I got some > rounting

[PATCH 5/5] mmc: sdhci-of-arasan: add power domain support

We should enable power domain once provided. Otherwise we take risk of bus err as it's maybe in off state before probing. Signed-off-by: Shawn Lin --- drivers/mmc/host/sdhci-of-arasan.c | 10 ++ 1 file changed, 10 insertions(+) diff --git

[PATCH 1/5] Documentation: mmc: synopsys-dw-mshc: add power domain description

This patch adds power domain as a optional property for dw_mmc. We should handle the power domain if available as it's in off state dut to the policy of power-saving after booting up. Otherwise dw_mmc can not be accessed. Signed-off-by: Shawn Lin ---

Re: [Regression?] fib_rules: Added NLM_F_EXCL support to fib_nl_newrule breaks Android userspace

From: John Stultz Date: Thu, 28 Jul 2016 21:18:16 -0700 > After moving my HiKey tree to pre-v4.8-rc, I noticed when using > Android that I was getting routing errors after toggling networking on > and off (or entering suspend). Wifi associated, but I got some > rounting errors in the logcat the

[PATCH 5/5] mmc: sdhci-of-arasan: add power domain support

We should enable power domain once provided. Otherwise we take risk of bus err as it's maybe in off state before probing. Signed-off-by: Shawn Lin --- drivers/mmc/host/sdhci-of-arasan.c | 10 ++ 1 file changed, 10 insertions(+) diff --git a/drivers/mmc/host/sdhci-of-arasan.c

[PATCH 1/5] Documentation: mmc: synopsys-dw-mshc: add power domain description

This patch adds power domain as a optional property for dw_mmc. We should handle the power domain if available as it's in off state dut to the policy of power-saving after booting up. Otherwise dw_mmc can not be accessed. Signed-off-by: Shawn Lin ---

[PATCH 2/5] Documentation: mmc: sdhci-of-arasan: add power domain description

This patch adds power domain as a optional property for sdhci-of-arasan. We should handle the power domain if available as it's in off state due to the policy of power-saving after booting up. Otherwise controller can not be accessed. Signed-off-by: Shawn Lin ---

[PATCH 2/5] Documentation: mmc: sdhci-of-arasan: add power domain description

This patch adds power domain as a optional property for sdhci-of-arasan. We should handle the power domain if available as it's in off state due to the policy of power-saving after booting up. Otherwise controller can not be accessed. Signed-off-by: Shawn Lin ---

[PATCH 3/5] arm64: dts: rockchip: Provide power-domains for sd/sdio/emmc controllers

We add these two properties as we need to enable it manually in case of been turned off by pd code if not referenced. We can't take risk of it, so let's do it. Signed-off-by: Shawn Lin --- arch/arm64/boot/dts/rockchip/rk3399.dtsi | 3 +++ 1 file changed, 3

[PATCH 4/5] mmc: dw_mmc: add power domain support

We should enable power domain once provided. Otherwise we take risk of bus err as it's maybe in off state before probing. Signed-off-by: Shawn Lin --- drivers/mmc/host/dw_mmc.c | 11 +++ 1 file changed, 11 insertions(+) diff --git a/drivers/mmc/host/dw_mmc.c

[PATCH 3/5] arm64: dts: rockchip: Provide power-domains for sd/sdio/emmc controllers

We add these two properties as we need to enable it manually in case of been turned off by pd code if not referenced. We can't take risk of it, so let's do it. Signed-off-by: Shawn Lin --- arch/arm64/boot/dts/rockchip/rk3399.dtsi | 3 +++ 1 file changed, 3 insertions(+) diff --git

[PATCH 4/5] mmc: dw_mmc: add power domain support

We should enable power domain once provided. Otherwise we take risk of bus err as it's maybe in off state before probing. Signed-off-by: Shawn Lin --- drivers/mmc/host/dw_mmc.c | 11 +++ 1 file changed, 11 insertions(+) diff --git a/drivers/mmc/host/dw_mmc.c

[PATCH 0/5] Add power domain support for dw_mmc/sdhci-of-arasan

We need to enable the power domain manually while probing as the power policy will turn off the pd which is not referenced. Otherwise we may take risk of breaking kernel once Feng Xiao land the rockchip pd relate stuff. So, let's do it in advance. This pachset is based on the latest

[Regression?] fib_rules: Added NLM_F_EXCL support to fib_nl_newrule breaks Android userspace

After moving my HiKey tree to pre-v4.8-rc, I noticed when using Android that I was getting routing errors after toggling networking on and off (or entering suspend). Wifi associated, but I got some rounting errors in the logcat the connection manager wouldn't detect a valid network. Not being

Re: linux-next: build failure after merge of the vfs tree

On Fri, Jul 29, 2016 at 11:19:38AM +1000, Stephen Rothwell wrote: > --- > fs/fuse/dir.c| 2 +- > fs/fuse/fuse_i.h | 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) > > diff --git a/fs/fuse/dir.c b/fs/fuse/dir.c > index f910578e51ba..c47b7780ce37 100644 > --- a/fs/fuse/dir.c > +++

[PATCH 0/5] Add power domain support for dw_mmc/sdhci-of-arasan

We need to enable the power domain manually while probing as the power policy will turn off the pd which is not referenced. Otherwise we may take risk of breaking kernel once Feng Xiao land the rockchip pd relate stuff. So, let's do it in advance. This pachset is based on the latest

[Regression?] fib_rules: Added NLM_F_EXCL support to fib_nl_newrule breaks Android userspace

After moving my HiKey tree to pre-v4.8-rc, I noticed when using Android that I was getting routing errors after toggling networking on and off (or entering suspend). Wifi associated, but I got some rounting errors in the logcat the connection manager wouldn't detect a valid network. Not being

Re: linux-next: build failure after merge of the vfs tree

On Fri, Jul 29, 2016 at 11:19:38AM +1000, Stephen Rothwell wrote: > --- > fs/fuse/dir.c| 2 +- > fs/fuse/fuse_i.h | 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) > > diff --git a/fs/fuse/dir.c b/fs/fuse/dir.c > index f910578e51ba..c47b7780ce37 100644 > --- a/fs/fuse/dir.c > +++

RE: [PATCH 1/1] EDAC, sb_edac: Fix channel reporting on Knights Landing

On Saturday, July 23, 2016 1:45 AM, Lukasz Odzioba wrote: > On Intel Xeon Phi Knights Landing processor family the channels > of memory controller have untypical arrangement - MC0 is mapped to > CH3,4,5 and MC1 is mapped to CH0,1,2. This causes EDAC driver to > report the channel name incorrectly.

RE: [PATCH 1/1] EDAC, sb_edac: Fix channel reporting on Knights Landing

On Saturday, July 23, 2016 1:45 AM, Lukasz Odzioba wrote: > On Intel Xeon Phi Knights Landing processor family the channels > of memory controller have untypical arrangement - MC0 is mapped to > CH3,4,5 and MC1 is mapped to CH0,1,2. This causes EDAC driver to > report the channel name incorrectly.

linux-next: manual merge of the akpm-current tree with the tip tree

Hi Andrew, Today's linux-next merge of the akpm-current tree got a conflict in: arch/x86/include/asm/thread_info.h between commit: 609c19a385c8 ("x86/ptrace: Stop setting TS_COMPAT in ptrace code") from the tip tree and commit: 58f9594bd42f ("signal: consolidate

linux-next: manual merge of the akpm-current tree with the tip tree

Hi Andrew, Today's linux-next merge of the akpm-current tree got a conflict in: arch/x86/include/asm/thread_info.h between commit: 609c19a385c8 ("x86/ptrace: Stop setting TS_COMPAT in ptrace code") from the tip tree and commit: 58f9594bd42f ("signal: consolidate

Re: [PATCH v2 2/2] sparc64: Fix pagetable freeing for hugepage regions

From: Nitin Gupta Date: Thu, 23 Jun 2016 15:05:36 -0700 > 8M pages now allocate page tables till PMD level only. > So, when freeing page table for 8M hugepage backed region, > make sure we don't try to access non-existent PTE level. > > Signed-off-by: Nitin Gupta

RE: [PATCH v2] perf sched: fix wrong conversion of task state

Hi Hiramatsu-san, On 2016/7/28, 2016 8:43, Masami Hiramatsu wrote: > Hmm, this includes several fixes and enhancements. > 1. Use first bit of the state instead of state itself (critical bug to avoid crash?) > 2. Check the range of the array and return '?' if out (minor bug, it can access data

Re: [PATCH v2 2/2] sparc64: Fix pagetable freeing for hugepage regions

From: Nitin Gupta Date: Thu, 23 Jun 2016 15:05:36 -0700 > 8M pages now allocate page tables till PMD level only. > So, when freeing page table for 8M hugepage backed region, > make sure we don't try to access non-existent PTE level. > > Signed-off-by: Nitin Gupta The manner in which you have

RE: [PATCH v2] perf sched: fix wrong conversion of task state

Hi Hiramatsu-san, On 2016/7/28, 2016 8:43, Masami Hiramatsu wrote: > Hmm, this includes several fixes and enhancements. > 1. Use first bit of the state instead of state itself (critical bug to avoid crash?) > 2. Check the range of the array and return '?' if out (minor bug, it can access data

[PATCH v3] perf sched: fix wrong conversion of task state

sched_out_state() converts the prev_state u64 bitmask to a char in a wrong way, which may cause invalid memory access. TASK_STATE_TO_CHAR_STR should also be fixed to adapt current kernel's sched.h. Signed-off-by: Tomoki Sekiyama Cc: Jiri Olsa

[PATCH v3] perf sched: fix wrong conversion of task state

sched_out_state() converts the prev_state u64 bitmask to a char in a wrong way, which may cause invalid memory access. TASK_STATE_TO_CHAR_STR should also be fixed to adapt current kernel's sched.h. Signed-off-by: Tomoki Sekiyama Cc: Jiri Olsa Cc: David Ahern Cc: Namhyung Kim Cc: Peter

[PATCH] cxl: replace loop with for_each_child_of_node(), remove unneeded of_node_put()

Rewrite the cxl_guest_init_afu() loop in cxl_of_probe() to use for_each_child_of_node() rather than a hand-coded for loop. Remove the useless of_node_put(afu_np) call after the loop, where it's guaranteed that afu_np == NULL. Reported-by: SF Markus Elfring

[PATCH] cxl: replace loop with for_each_child_of_node(), remove unneeded of_node_put()

Rewrite the cxl_guest_init_afu() loop in cxl_of_probe() to use for_each_child_of_node() rather than a hand-coded for loop. Remove the useless of_node_put(afu_np) call after the loop, where it's guaranteed that afu_np == NULL. Reported-by: SF Markus Elfring Reported-by: Julia Lawall

Re: [PATCH V6 3/9] irqdomain: Don't set type when mapping an IRQ

Hi. I noticed my board would not work any more when pulling recent updates. I did "git-bisect" and I found the following commit is it. commit 1e2a7d78499ec8859d2b469051b7b80bad3b08aa Author: Jon Hunter Date: Tue Jun 7 16:12:28 2016 +0100 irqdomain: Don't set

Re: [PATCH V6 3/9] irqdomain: Don't set type when mapping an IRQ

Hi. I noticed my board would not work any more when pulling recent updates. I did "git-bisect" and I found the following commit is it. commit 1e2a7d78499ec8859d2b469051b7b80bad3b08aa Author: Jon Hunter Date: Tue Jun 7 16:12:28 2016 +0100 irqdomain: Don't set type when mapping an IRQ

Re: [PATCH 0/3] new feature: monitoring page cache events

On Thu, Jul 28, 2016 at 02:02:45PM -0700, Dave Hansen wrote: > On 07/25/2016 08:47 PM, George Amvrosiadis wrote: > > 21 files changed, 2424 insertions(+), 1 deletion(-) > > I like the idea, but yikes, that's a lot of code. > > Have you considered using or augmenting the kernel's existing

Re: [PATCH 0/3] new feature: monitoring page cache events

On Thu, Jul 28, 2016 at 02:02:45PM -0700, Dave Hansen wrote: > On 07/25/2016 08:47 PM, George Amvrosiadis wrote: > > 21 files changed, 2424 insertions(+), 1 deletion(-) > > I like the idea, but yikes, that's a lot of code. > > Have you considered using or augmenting the kernel's existing

Re: [PATCH 2/2] mmc: dw_mmc: remove the deprecated "supports-highspeed" property

Hi Shawn, On 07/29/2016 11:44 AM, Shawn Lin wrote: > 在 2016/7/28 17:55, Jaehoon Chung 写道: >> Remvoe the deprecated "supports-highspeed" property. >> DWMMC controller will not use this property anymore. >> > > We had set up a flag day to remove these deprecated property > long time agao. > > It

Re: [PATCH 2/2] mmc: dw_mmc: remove the deprecated "supports-highspeed" property

Hi Shawn, On 07/29/2016 11:44 AM, Shawn Lin wrote: > 在 2016/7/28 17:55, Jaehoon Chung 写道: >> Remvoe the deprecated "supports-highspeed" property. >> DWMMC controller will not use this property anymore. >> > > We had set up a flag day to remove these deprecated property > long time agao. > > It

Re: [PATCH] mm: move swap-in anonymous page into active list

On Fri, Jul 29, 2016 at 12:25:40PM +0900, Minchan Kim wrote: > Every swap-in anonymous page starts from inactive lru list's head. > It should be activated unconditionally when VM decide to reclaim > because page table entry for the page always usually has marked > accessed bit. Thus, their window

Re: [PATCH] mm: move swap-in anonymous page into active list

On Fri, Jul 29, 2016 at 12:25:40PM +0900, Minchan Kim wrote: > Every swap-in anonymous page starts from inactive lru list's head. > It should be activated unconditionally when VM decide to reclaim > because page table entry for the page always usually has marked > accessed bit. Thus, their window

[PATCH] mm: move swap-in anonymous page into active list

Every swap-in anonymous page starts from inactive lru list's head. It should be activated unconditionally when VM decide to reclaim because page table entry for the page always usually has marked accessed bit. Thus, their window size for getting a new referece is 2 * NR_inactive + NR_active while

[PATCH] mm: move swap-in anonymous page into active list

Every swap-in anonymous page starts from inactive lru list's head. It should be activated unconditionally when VM decide to reclaim because page table entry for the page always usually has marked accessed bit. Thus, their window size for getting a new referece is 2 * NR_inactive + NR_active while

Build failure in linux mainline when building arcv2 images

Hi Vineet, Mainline fails to build arcv2 images with the following error. {standard input}: Assembler messages: {standard input}:19174: Error: Instruction with long immediate data in delay slot make[2]: *** [block/cfq-iosched.o] Error 1 Bisect points to commit 9a7f38c42c2 ("cfq-iosched:

[PATCH 1/2] Documentation: kdump: update maxcpus to nr_cpus

Parameter nr_cpus is used to bring up a SMP dump-capture kernel, instead of the old parameter maxcpus. This commit update it in Documentation/kdump/kdump.txt. Signed-off-by: Zhou Wenjian --- Documentation/kdump/kdump.txt | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH 2/2] Documentation: kdump: add description of bringing up SMP dump-capture kernel

SMP dump-capture kernel is useful to improve the performance of kdump in some cases. So add the description of bringing up SMP dump-capture kernel. Signed-off-by: Zhou Wenjian --- Documentation/kdump/kdump.txt | 6 ++ 1 file changed, 6 insertions(+) diff --git

[PATCH 1/2] Documentation: kdump: update maxcpus to nr_cpus

Parameter nr_cpus is used to bring up a SMP dump-capture kernel, instead of the old parameter maxcpus. This commit update it in Documentation/kdump/kdump.txt. Signed-off-by: Zhou Wenjian --- Documentation/kdump/kdump.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 2/2] Documentation: kdump: add description of bringing up SMP dump-capture kernel

SMP dump-capture kernel is useful to improve the performance of kdump in some cases. So add the description of bringing up SMP dump-capture kernel. Signed-off-by: Zhou Wenjian --- Documentation/kdump/kdump.txt | 6 ++ 1 file changed, 6 insertions(+) diff --git

Build failure in linux mainline when building arcv2 images

Hi Vineet, Mainline fails to build arcv2 images with the following error. {standard input}: Assembler messages: {standard input}:19174: Error: Instruction with long immediate data in delay slot make[2]: *** [block/cfq-iosched.o] Error 1 Bisect points to commit 9a7f38c42c2 ("cfq-iosched:

[PATCH v5] virtio: new feature to detect IOMMU device quirk

The interaction between virtio and IOMMUs is messy. On most systems with virtio, physical addresses match bus addresses, and it doesn't particularly matter which one we use to program the device. On some systems, including Xen and any system with a physical device that speaks virtio behind a

[PATCH v5] virtio: new feature to detect IOMMU device quirk

The interaction between virtio and IOMMUs is messy. On most systems with virtio, physical addresses match bus addresses, and it doesn't particularly matter which one we use to program the device. On some systems, including Xen and any system with a physical device that speaks virtio behind a

Re: [PATCH v3 2/2] tpm: add driver for cr50 on SPI

On Thu, Jul 28, 2016 at 05:17:06PM -0600, Jason Gunthorpe wrote: > On Thu, Jul 28, 2016 at 04:01:41PM -0700, Dmitry Torokhov wrote: > > > > + u8 tx_buf[MAX_SPI_FRAMESIZE]; > > > + u8 rx_buf[MAX_SPI_FRAMESIZE]; > > > > Both of these need to be annotated as "cacheline_aligned" since we > > eye

Re: [PATCH v3 2/2] tpm: add driver for cr50 on SPI

On Thu, Jul 28, 2016 at 05:17:06PM -0600, Jason Gunthorpe wrote: > On Thu, Jul 28, 2016 at 04:01:41PM -0700, Dmitry Torokhov wrote: > > > > + u8 tx_buf[MAX_SPI_FRAMESIZE]; > > > + u8 rx_buf[MAX_SPI_FRAMESIZE]; > > > > Both of these need to be annotated as "cacheline_aligned" since we > > eye

[PATCH] tpm: fix cacheline alignment for DMA-able buffers

Annotate buffers used in spi transactions as cacheline_aligned to use in DMA transfers. Signed-off-by: Andrey Pronin --- drivers/char/tpm/st33zp24/spi.c | 4 ++-- drivers/char/tpm/tpm_tis_spi.c | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git

[PATCH] tpm: fix cacheline alignment for DMA-able buffers

Annotate buffers used in spi transactions as cacheline_aligned to use in DMA transfers. Signed-off-by: Andrey Pronin --- drivers/char/tpm/st33zp24/spi.c | 4 ++-- drivers/char/tpm/tpm_tis_spi.c | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git

Re: [RFC] can we use vmalloc to alloc thread stack if compaction failed

On Thu, Jul 28, 2016 at 08:07:51AM -0700, Andy Lutomirski wrote: > On Thu, Jul 28, 2016 at 3:51 AM, Xishi Qiu wrote: > > On 2016/7/28 17:43, Michal Hocko wrote: > > > >> On Thu 28-07-16 16:45:06, Xishi Qiu wrote: > >>> On 2016/7/28 15:58, Michal Hocko wrote: > >>> > On

Re: [RFC] can we use vmalloc to alloc thread stack if compaction failed

On Thu, Jul 28, 2016 at 08:07:51AM -0700, Andy Lutomirski wrote: > On Thu, Jul 28, 2016 at 3:51 AM, Xishi Qiu wrote: > > On 2016/7/28 17:43, Michal Hocko wrote: > > > >> On Thu 28-07-16 16:45:06, Xishi Qiu wrote: > >>> On 2016/7/28 15:58, Michal Hocko wrote: > >>> > On Thu 28-07-16 15:41:53,

[PATCH v8 1/2] Documentation: bindings: add dt doc for Rockchip PCIe controller

This patch adds a binding that describes the Rockchip PCIe controller found on Rockchip SoCs PCIe interface. Signed-off-by: Shawn Lin Acked-by: Rob Herring Reviewed-by: Brian Norris --- Changes in v8: - add Brian's

[PATCH v8 2/2] PCI: Rockchip: Add Rockchip PCIe controller support

This patch adds Rockchip PCIe controller support found on RK3399 Soc platform. Signed-off-by: Shawn Lin Reviewed-by: Brian Norris --- Changes in v8: - fix all the comments suggested by Bjorn Helgaas in v7[1] [1]

[PATCH v8 1/2] Documentation: bindings: add dt doc for Rockchip PCIe controller

This patch adds a binding that describes the Rockchip PCIe controller found on Rockchip SoCs PCIe interface. Signed-off-by: Shawn Lin Acked-by: Rob Herring Reviewed-by: Brian Norris --- Changes in v8: - add Brian's review-tag Changes in v7: - move optional properties ahead of interrupt

[PATCH v8 2/2] PCI: Rockchip: Add Rockchip PCIe controller support

This patch adds Rockchip PCIe controller support found on RK3399 Soc platform. Signed-off-by: Shawn Lin Reviewed-by: Brian Norris --- Changes in v8: - fix all the comments suggested by Bjorn Helgaas in v7[1] [1] https://patchwork.kernel.org/patch/9233887/ - enable bandwith interrupt for

Re: [PATCH 2/2] mmc: dw_mmc: remove the deprecated "supports-highspeed" property

在 2016/7/28 17:55, Jaehoon Chung 写道: Remvoe the deprecated "supports-highspeed" property. DWMMC controller will not use this property anymore. We had set up a flag day to remove these deprecated property long time agao. It doesn't *break* old dtb which may(not ?) still boot up new kernel

Re: [PATCH 2/2] mmc: dw_mmc: remove the deprecated "supports-highspeed" property

在 2016/7/28 17:55, Jaehoon Chung 写道: Remvoe the deprecated "supports-highspeed" property. DWMMC controller will not use this property anymore. We had set up a flag day to remove these deprecated property long time agao. It doesn't *break* old dtb which may(not ?) still boot up new kernel

[PATCH] lkdtm: Fix targets for objcopy usage

The targets for lkdtm's objcopy were missing which caused them to always be rebuilt. This corrects the problem. Additionally, commit f8fa70f392fa ("arm64: localise Image objcopy flags") has landed now, so this removes the work-around for the global OBJCOPY flag setting. Reported-by: Linus

Re: warning: calling ‘__builtin_return_address’ with a nonzero argument is unsafe

On Thu, 28 Jul 2016 18:25:33 -0700 Linus Torvalds wrote: > I tried something like that, but the CFLAGS games the tracing code > does made my thing result in > > kernel/trace/Makefile:20: *** Recursive variable 'KBUILD_CFLAGS' > references itself (eventually).

[PATCH] lkdtm: Fix targets for objcopy usage

The targets for lkdtm's objcopy were missing which caused them to always be rebuilt. This corrects the problem. Additionally, commit f8fa70f392fa ("arm64: localise Image objcopy flags") has landed now, so this removes the work-around for the global OBJCOPY flag setting. Reported-by: Linus

Re: warning: calling ‘__builtin_return_address’ with a nonzero argument is unsafe

On Thu, 28 Jul 2016 18:25:33 -0700 Linus Torvalds wrote: > I tried something like that, but the CFLAGS games the tracing code > does made my thing result in > > kernel/trace/Makefile:20: *** Recursive variable 'KBUILD_CFLAGS' > references itself (eventually). Stop. > > but yes, if you have

Re: [PATCH] perf sched: fix wrong conversion of task state

On 2016/07/28 23:26、David Ahern wrote: >> But that means we cannot handle preemption correctly as far as >> sched:sched_switch >> event uses TASK_STATE_MAX to mark preempted tasks. >> >> Should we stop using TASK_STATE_MAX for preempted tasks in ftrace and >> use (1 << 63) or something that

Re: [PATCH] perf sched: fix wrong conversion of task state

On 2016/07/28 23:26、David Ahern wrote: >> But that means we cannot handle preemption correctly as far as >> sched:sched_switch >> event uses TASK_STATE_MAX to mark preempted tasks. >> >> Should we stop using TASK_STATE_MAX for preempted tasks in ftrace and >> use (1 << 63) or something that

Re: [PATCH v11] acpi, apei, arm64: APEI initial support for aarch64.

Hi Suzuki, On 28 July 2016 at 17:39, Suzuki K Poulose wrote: > On 27/07/16 18:29, fu@linaro.org wrote: >> >> From: Tomasz Nowicki >> >> This commit provides APEI arch-specific bits for aarch64 >> >> Meanwhile, >> (1)add a new subfunction

Re: [PATCH v11] acpi, apei, arm64: APEI initial support for aarch64.

Hi Suzuki, On 28 July 2016 at 17:39, Suzuki K Poulose wrote: > On 27/07/16 18:29, fu@linaro.org wrote: >> >> From: Tomasz Nowicki >> >> This commit provides APEI arch-specific bits for aarch64 >> >> Meanwhile, >> (1)add a new subfunction "hest_ia32_init" for >> "acpi_disable_cmcff" which is

Re: [PATCH v3 1/6] binding-doc: power: pwrseq-generic: add binding doc for generic power sequence library

On Wed, Jul 20, 2016 at 05:40:24PM +0800, Peter Chen wrote: > Add binding doc for generic power sequence library. > > Signed-off-by: Peter Chen > Acked-by: Philipp Zabel > --- > .../bindings/power/pwrseq/pwrseq-generic.txt | 48 >

Re: [PATCH v3 1/6] binding-doc: power: pwrseq-generic: add binding doc for generic power sequence library

On Wed, Jul 20, 2016 at 05:40:24PM +0800, Peter Chen wrote: > Add binding doc for generic power sequence library. > > Signed-off-by: Peter Chen > Acked-by: Philipp Zabel > --- > .../bindings/power/pwrseq/pwrseq-generic.txt | 48 > ++ > 1 file changed, 48

Re: [tip:smp/hotplug 5/6] arch/x86/xen/enlighten.c:1522:2: error: implicit declaration of function 'xen_pvh_early_cpu_init'

On 07/28/2016 12:14 PM, kbuild test robot wrote: tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git smp/hotplug head: c713c8cb2055f5f3b32ee4315be589177a2658cc commit: 854e9fa5a56a9771fad4701a427e4844d2cbade1 [5/6] xen/x86: Define stubs for xen_smp_intr_init/xen_smp_intr_free

Re: [tip:smp/hotplug 5/6] arch/x86/xen/enlighten.c:1522:2: error: implicit declaration of function 'xen_pvh_early_cpu_init'

On 07/28/2016 12:14 PM, kbuild test robot wrote: tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git smp/hotplug head: c713c8cb2055f5f3b32ee4315be589177a2658cc commit: 854e9fa5a56a9771fad4701a427e4844d2cbade1 [5/6] xen/x86: Define stubs for xen_smp_intr_init/xen_smp_intr_free

[PATCH v4 0/2] tpm: add driver for cr50 on SPI

This patchset adds support for H1 Secure Microcontroller running Cr50 firmware. It implements several functions, including TPM-like functionality, and communicates over SPI using the FIFO protocol described in the PTP Spec, section 6. H1 is a proprietary chip that the Chrome OS team is

[PATCH v4 0/2] tpm: add driver for cr50 on SPI

This patchset adds support for H1 Secure Microcontroller running Cr50 firmware. It implements several functions, including TPM-like functionality, and communicates over SPI using the FIFO protocol described in the PTP Spec, section 6. H1 is a proprietary chip that the Chrome OS team is

[PATCH v4 2/2] tpm: add driver for cr50 on SPI

Add TPM2.0 PTP FIFO compatible SPI interface for chips with Cr50 firmware. The firmware running on the currently supported H1 Secure Microcontroller requires a special driver to handle its specifics: - need to ensure a certain delay between spi transactions, or else the chip may miss some part

[PATCH v4 2/2] tpm: add driver for cr50 on SPI

Add TPM2.0 PTP FIFO compatible SPI interface for chips with Cr50 firmware. The firmware running on the currently supported H1 Secure Microcontroller requires a special driver to handle its specifics: - need to ensure a certain delay between spi transactions, or else the chip may miss some part

  1   2   3   4   5   6   7   8   9   10   >