[PATCH v7 4/6] dmaengine: xilinx_dma: Fix kernel doc warnings

This patch fixes the kernel doc warnings in the driver. Signed-off-by: Kedareswara rao Appana --- Changes for v7: --> New patch. drivers/dma/xilinx/xilinx_dma.c | 37 - 1 file changed, 24 insertions(+), 13 deletions(-) diff --git

[PATCH v7 4/6] dmaengine: xilinx_dma: Fix kernel doc warnings

This patch fixes the kernel doc warnings in the driver. Signed-off-by: Kedareswara rao Appana --- Changes for v7: --> New patch. drivers/dma/xilinx/xilinx_dma.c | 37 - 1 file changed, 24 insertions(+), 13 deletions(-) diff --git

[PATCH v7 3/6] dmaengine: xilinx_dma: Fix race condition in the driver for multiple descriptor scenario

As per axi dmaengine spec the software must not move the tail pointer to a location that has not been updated (next descriptor field of the h/w descriptor should always point to a valid address). When user submits multiple descriptors on the recv side, with the current driver flow the last buffer

[PATCH v7 6/6] dmaengine: xilinx_dma: Differentiate probe based on the ip type

This patch updates the probe banner info based on the ip probed. Signed-off-by: Kedareswara rao Appana --- Changes for v7: --> New patch. drivers/dma/xilinx/xilinx_dma.c | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git

[PATCH v7 3/6] dmaengine: xilinx_dma: Fix race condition in the driver for multiple descriptor scenario

As per axi dmaengine spec the software must not move the tail pointer to a location that has not been updated (next descriptor field of the h/w descriptor should always point to a valid address). When user submits multiple descriptors on the recv side, with the current driver flow the last buffer

[PATCH v7 6/6] dmaengine: xilinx_dma: Differentiate probe based on the ip type

This patch updates the probe banner info based on the ip probed. Signed-off-by: Kedareswara rao Appana --- Changes for v7: --> New patch. drivers/dma/xilinx/xilinx_dma.c | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/drivers/dma/xilinx/xilinx_dma.c

[PATCH v7 0/6] dmaengine: xilinx_dma: Bug fixes

This patch series fixes below bugs in DMA and VDMA IP's ---> Added channel idle checks in the driver before submitting the buffer descriptor to h/w. ---> Fixes bug in Multi frame sotres handling in VDMA ---> Fixes issues w.r.to multi frame descriptors submit with AXI DMA S2MM(recv) Side. --->

[PATCH v7 1/6] dmaengine: xilinx_dma: Check for channel idle state before submitting dma descriptor

Add variable for checking channel idle state to ensure that dma descriptor is not submitted when dmaengine is in progress. This will avoid the polling for a bit in the status register to know dma state in the driver hot path. Reviewed-by: Jose Abreu Signed-off-by:

[PATCH v7 0/6] dmaengine: xilinx_dma: Bug fixes

This patch series fixes below bugs in DMA and VDMA IP's ---> Added channel idle checks in the driver before submitting the buffer descriptor to h/w. ---> Fixes bug in Multi frame sotres handling in VDMA ---> Fixes issues w.r.to multi frame descriptors submit with AXI DMA S2MM(recv) Side. --->

[PATCH v7 1/6] dmaengine: xilinx_dma: Check for channel idle state before submitting dma descriptor

Add variable for checking channel idle state to ensure that dma descriptor is not submitted when dmaengine is in progress. This will avoid the polling for a bit in the status register to know dma state in the driver hot path. Reviewed-by: Jose Abreu Signed-off-by: Kedareswara rao Appana ---

Re: [PATCH] NFS: allow name_to_handle_at() to work for Amazon EFS.

On Thu, Dec 07, 2017 at 02:20:05PM +1100, NeilBrown wrote: > We can allocate in fs/notify/fdinfo.c:show_fdinfo() which is > the earliest 'notify' specific code to run. There is no > opportunity to return an error but GFP_KERNEL allocations under 1 page > never fail.. "never" * The default

Re: [PATCH] NFS: allow name_to_handle_at() to work for Amazon EFS.

On Thu, Dec 07, 2017 at 02:20:05PM +1100, NeilBrown wrote: > We can allocate in fs/notify/fdinfo.c:show_fdinfo() which is > the earliest 'notify' specific code to run. There is no > opportunity to return an error but GFP_KERNEL allocations under 1 page > never fail.. "never" * The default

Re: [PATCH v3 1/4] kaslr: add immovable_mem=nn[KMG]@ss[KMG] to specify extracting memory

On Thu, Dec 07, 2017 at 12:58:06PM +0800, Baoquan He wrote: >On 12/07/17 at 12:16pm, Dou Liyang wrote: >> Hi All, >> >> At 12/07/2017 11:56 AM, Chao Fan wrote: >> > On Thu, Dec 07, 2017 at 11:09:24AM +0800, Baoquan He wrote: >> > > On 12/07/17 at 10:53am, Chao Fan wrote: >> > > > On Wed, Dec 06,

Re: [PATCH v3 1/4] kaslr: add immovable_mem=nn[KMG]@ss[KMG] to specify extracting memory

On Thu, Dec 07, 2017 at 12:58:06PM +0800, Baoquan He wrote: >On 12/07/17 at 12:16pm, Dou Liyang wrote: >> Hi All, >> >> At 12/07/2017 11:56 AM, Chao Fan wrote: >> > On Thu, Dec 07, 2017 at 11:09:24AM +0800, Baoquan He wrote: >> > > On 12/07/17 at 10:53am, Chao Fan wrote: >> > > > On Wed, Dec 06,

[PATCH] misc: hpilo: Use SPDX-License-Identifier

From: Dhaval Shah SPDX-License-Identifier is used for the hpilo. Signed-off-by: Dhaval Shah --- drivers/misc/hpilo.c | 5 + drivers/misc/hpilo.h | 5 + 2 files changed, 2 insertions(+), 8 deletions(-) diff --git

[PATCH] misc: hpilo: Use SPDX-License-Identifier

From: Dhaval Shah SPDX-License-Identifier is used for the hpilo. Signed-off-by: Dhaval Shah --- drivers/misc/hpilo.c | 5 + drivers/misc/hpilo.h | 5 + 2 files changed, 2 insertions(+), 8 deletions(-) diff --git a/drivers/misc/hpilo.c b/drivers/misc/hpilo.c index

[PATCH] usb: phy: Factor out the usb charger initialization

Factor out the guts of usb charger initialization into usb_charger_init() function, to make the usb_add_extcon() only do the extcon related things. Meanwhile we also should initialize the USB charger before registering the extcon device, in case the extcon notification was issued earlier than usb

[PATCH] usb: phy: Factor out the usb charger initialization

Factor out the guts of usb charger initialization into usb_charger_init() function, to make the usb_add_extcon() only do the extcon related things. Meanwhile we also should initialize the USB charger before registering the extcon device, in case the extcon notification was issued earlier than usb

Re: [PATCH] doc: convert printk-formats.txt to rst

On Wed, Dec 06, 2017 at 04:39:58PM -0800, Randy Dunlap wrote: > On 12/06/2017 01:16 PM, Tobin C. Harding wrote: > > On Wed, Dec 06, 2017 at 10:18:49AM -0800, Randy Dunlap wrote: > > > > Thanks for your comments Randy. > > > > >>> Documentation/index.rst| 10 + > >>>

Re: [PATCH] doc: convert printk-formats.txt to rst

On Wed, Dec 06, 2017 at 04:39:58PM -0800, Randy Dunlap wrote: > On 12/06/2017 01:16 PM, Tobin C. Harding wrote: > > On Wed, Dec 06, 2017 at 10:18:49AM -0800, Randy Dunlap wrote: > > > > Thanks for your comments Randy. > > > > >>> Documentation/index.rst| 10 + > >>>

linux-next: Tree for Dec 7

Hi all, Changes since 20171206: New tree: kvms390-fixes The vfs tree gained conflicts against the bpf and netfilter trees. The printk tree gained a new build failure so I used the tree from next-20171206 with a reverted commit. The netfilter-next tree gained a conflict against the netfilter

linux-next: Tree for Dec 7

Hi all, Changes since 20171206: New tree: kvms390-fixes The vfs tree gained conflicts against the bpf and netfilter trees. The printk tree gained a new build failure so I used the tree from next-20171206 with a reverted commit. The netfilter-next tree gained a conflict against the netfilter

Re: [PATCH v3] scripts: leaking_addresses: add support for 32-bit kernel addresses

On Thu, Dec 07, 2017 at 09:41:58AM +0530, kaiwan.billimo...@gmail.com wrote: > On Thu, 2017-12-07 at 10:01 +1100, Tobin C. Harding wrote: > > On Wed, Dec 06, 2017 at 05:21:30PM +0530, kaiwan.billimo...@gmail.com wrote: > > > On Wed, 2017-12-06 at 15:04 +1100, Tobin C. Harding wrote: > > > > > > >

Re: [PATCH v3] scripts: leaking_addresses: add support for 32-bit kernel addresses

On Thu, Dec 07, 2017 at 09:41:58AM +0530, kaiwan.billimo...@gmail.com wrote: > On Thu, 2017-12-07 at 10:01 +1100, Tobin C. Harding wrote: > > On Wed, Dec 06, 2017 at 05:21:30PM +0530, kaiwan.billimo...@gmail.com wrote: > > > On Wed, 2017-12-06 at 15:04 +1100, Tobin C. Harding wrote: > > > > > > >

Re: [PATCH V11 4/5] vsprintf: add printk specifier %px

On Wed, Dec 06, 2017 at 05:45:37PM +0900, Sergey Senozhatsky wrote: > On (12/06/17 09:32), Geert Uytterhoeven wrote: > [..] > > >> show_fault_oops(struct pt_regs *regs, unsigned long error_code, > > >> unsigned long address) > > >> ... > > >> printk(KERN_CONT " at %p\n",

Re: [PATCH V11 4/5] vsprintf: add printk specifier %px

On Wed, Dec 06, 2017 at 05:45:37PM +0900, Sergey Senozhatsky wrote: > On (12/06/17 09:32), Geert Uytterhoeven wrote: > [..] > > >> show_fault_oops(struct pt_regs *regs, unsigned long error_code, > > >> unsigned long address) > > >> ... > > >> printk(KERN_CONT " at %p\n",

Re: [PATCH v3 3/6] cpufreq: schedutil: update CFS util only if used

On 30-11-17, 15:57, Patrick Bellasi wrote: > Yes, that's a pretty trivial update with a confusing changelog. > > If we think it's worth to keep (and correct as well) I'll update the > commit message. We also need to update the commit log based on feedback from Vikram on V2. Which said that the

Re: [PATCH v3 3/6] cpufreq: schedutil: update CFS util only if used

On 30-11-17, 15:57, Patrick Bellasi wrote: > Yes, that's a pretty trivial update with a confusing changelog. > > If we think it's worth to keep (and correct as well) I'll update the > commit message. We also need to update the commit log based on feedback from Vikram on V2. Which said that the

Re: [PATCH] cpufreq: longhaul: Set transition_delay_us to 20 ms

> > 3 was not reliable. > > > > I created root cron job > > @reboot sleep 120; /sbin/reboot > > > > and by the evening it was dead again. > > > > Will try 5 tomorrow. > > Lets make it similar to what it was before my original patch modified > it, to avoid all corner cases. > > Please

Re: [PATCH] cpufreq: longhaul: Set transition_delay_us to 20 ms

> > 3 was not reliable. > > > > I created root cron job > > @reboot sleep 120; /sbin/reboot > > > > and by the evening it was dead again. > > > > Will try 5 tomorrow. > > Lets make it similar to what it was before my original patch modified > it, to avoid all corner cases. > > Please

Re: [PATCH V11 4/5] vsprintf: add printk specifier %px

On Wed, Dec 06, 2017 at 09:32:14AM +0100, Geert Uytterhoeven wrote: > Hi Linus, > > On Wed, Dec 6, 2017 at 2:59 AM, Linus Torvalds > wrote: > > On Tue, Dec 5, 2017 at 5:36 PM, Sergey Senozhatsky > > wrote: > >> I see some %p-s

Re: [PATCH V11 4/5] vsprintf: add printk specifier %px

On Wed, Dec 06, 2017 at 09:32:14AM +0100, Geert Uytterhoeven wrote: > Hi Linus, > > On Wed, Dec 6, 2017 at 2:59 AM, Linus Torvalds > wrote: > > On Tue, Dec 5, 2017 at 5:36 PM, Sergey Senozhatsky > > wrote: > >> I see some %p-s being used in _supposedly_ important output, > >> like

Re: [PATCH v3 2/6] cpufreq: schedutil: ensure max frequency while running RT/DL tasks

On 30-11-17, 11:47, Patrick Bellasi wrote: > diff --git a/kernel/sched/cpufreq_schedutil.c > b/kernel/sched/cpufreq_schedutil.c > index 67339ccb5595..448f49de5335 100644 > --- a/kernel/sched/cpufreq_schedutil.c > +++ b/kernel/sched/cpufreq_schedutil.c > @@ -262,6 +262,7 @@ static void

Re: [PATCH v3 2/6] cpufreq: schedutil: ensure max frequency while running RT/DL tasks

On 30-11-17, 11:47, Patrick Bellasi wrote: > diff --git a/kernel/sched/cpufreq_schedutil.c > b/kernel/sched/cpufreq_schedutil.c > index 67339ccb5595..448f49de5335 100644 > --- a/kernel/sched/cpufreq_schedutil.c > +++ b/kernel/sched/cpufreq_schedutil.c > @@ -262,6 +262,7 @@ static void

Re: [PATCH v3 1/6] cpufreq: schedutil: reset sg_cpus's flags at IDLE enter

On 30-11-17, 11:47, Patrick Bellasi wrote: > diff --git a/include/linux/sched/cpufreq.h b/include/linux/sched/cpufreq.h > index d1ad3d825561..bb5f778db023 100644 > --- a/include/linux/sched/cpufreq.h > +++ b/include/linux/sched/cpufreq.h > @@ -11,6 +11,7 @@ > #define SCHED_CPUFREQ_RT (1U <<

Re: [PATCH v4 9/9] drm/i915: Implement HDCP for DisplayPort

Thanks for handling the reauth req from downstream. you might want to fix the missed single occurance of "//" On Thursday 07 December 2017 05:30 AM, Sean Paul wrote: This patch adds HDCP support for DisplayPort connectors by implementing the intel_hdcp_shim. Most of this is straightforward

Re: [PATCH v3 1/6] cpufreq: schedutil: reset sg_cpus's flags at IDLE enter

On 30-11-17, 11:47, Patrick Bellasi wrote: > diff --git a/include/linux/sched/cpufreq.h b/include/linux/sched/cpufreq.h > index d1ad3d825561..bb5f778db023 100644 > --- a/include/linux/sched/cpufreq.h > +++ b/include/linux/sched/cpufreq.h > @@ -11,6 +11,7 @@ > #define SCHED_CPUFREQ_RT (1U <<

Re: [PATCH v4 9/9] drm/i915: Implement HDCP for DisplayPort

Thanks for handling the reauth req from downstream. you might want to fix the missed single occurance of "//" On Thursday 07 December 2017 05:30 AM, Sean Paul wrote: This patch adds HDCP support for DisplayPort connectors by implementing the intel_hdcp_shim. Most of this is straightforward

Re: [PATCH v3 1/4] kaslr: add immovable_mem=nn[KMG]@ss[KMG] to specify extracting memory

On 12/07/17 at 12:16pm, Dou Liyang wrote: > Hi All, > > At 12/07/2017 11:56 AM, Chao Fan wrote: > > On Thu, Dec 07, 2017 at 11:09:24AM +0800, Baoquan He wrote: > > > On 12/07/17 at 10:53am, Chao Fan wrote: > > > > On Wed, Dec 06, 2017 at 05:35:57PM +0800, Baoquan He wrote: > > > > > Hi Chao, > >

Re: [PATCH v3 1/4] kaslr: add immovable_mem=nn[KMG]@ss[KMG] to specify extracting memory

On 12/07/17 at 12:16pm, Dou Liyang wrote: > Hi All, > > At 12/07/2017 11:56 AM, Chao Fan wrote: > > On Thu, Dec 07, 2017 at 11:09:24AM +0800, Baoquan He wrote: > > > On 12/07/17 at 10:53am, Chao Fan wrote: > > > > On Wed, Dec 06, 2017 at 05:35:57PM +0800, Baoquan He wrote: > > > > > Hi Chao, > >

Re: [PATCH 0/5] perf-probe: Improve probing on versioned symbols

Hi Masami, On 12/06/2017 08:36 AM, Masami Hiramatsu wrote: > [4/5] Find versioned symbol from map without wildcard. >This allows user to specify a symbol without version >suffix nor wildcard. Anyway, at this point we have >no way to specify version suffix, because parser >

Re: [PATCH 0/5] perf-probe: Improve probing on versioned symbols

Hi Masami, On 12/06/2017 08:36 AM, Masami Hiramatsu wrote: > [4/5] Find versioned symbol from map without wildcard. >This allows user to specify a symbol without version >suffix nor wildcard. Anyway, at this point we have >no way to specify version suffix, because parser >

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

s/scsi/scsi_mod.ko] undefined! > > > > > > Caused by commit > > > > > > ac90420f17c9 ("scsi: core: Ensure that the SCSI error handler gets > > > woken up") > > > > > > I have used the scsi-mkp tree from next-20171206 for tod

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

; > > > > > Caused by commit > > > > > > ac90420f17c9 ("scsi: core: Ensure that the SCSI error handler gets > > > woken up") > > > > > > I have used the scsi-mkp tree from next-20171206 for today. > > >

[PATCH] usb: dwc3: of-simple: set dev_pm_ops

dwc3_of_simple_dev_pm_ops has never been used since the initial support by commit 16adc674d0d6 ("usb: dwc3: add generic OF glue layer"). I guess it just missed to set .pm struct member. Signed-off-by: Masahiro Yamada --- drivers/usb/dwc3/dwc3-of-simple.c | 1 +

[PATCH] usb: dwc3: of-simple: set dev_pm_ops

dwc3_of_simple_dev_pm_ops has never been used since the initial support by commit 16adc674d0d6 ("usb: dwc3: add generic OF glue layer"). I guess it just missed to set .pm struct member. Signed-off-by: Masahiro Yamada --- drivers/usb/dwc3/dwc3-of-simple.c | 1 + 1 file changed, 1 insertion(+)

Re: [PATCH] cpufreq: longhaul: Set transition_delay_us to 20 ms

On 06-12-17, 20:21, Meelis Roos wrote: > 3 was not reliable. > > I created root cron job > @reboot sleep 120; /sbin/reboot > > and by the evening it was dead again. > > Will try 5 tomorrow. Lets make it similar to what it was before my original patch modified it, to avoid all corner

Re: [PATCH] cpufreq: longhaul: Set transition_delay_us to 20 ms

On 06-12-17, 20:21, Meelis Roos wrote: > 3 was not reliable. > > I created root cron job > @reboot sleep 120; /sbin/reboot > > and by the evening it was dead again. > > Will try 5 tomorrow. Lets make it similar to what it was before my original patch modified it, to avoid all corner

Re: [PATCH] watchdog: hpwdt: fix unused variable warning

On 12/06/2017 01:02 PM, Arnd Bergmann wrote: The new hpwdt_my_nmi() function is used conditionally, which produces a harmless warning in some configurations: drivers/watchdog/hpwdt.c:478:12: error: 'hpwdt_my_nmi' defined but not used [-Werror=unused-function] This moves it inside of the

Re: [PATCH] watchdog: hpwdt: fix unused variable warning

On 12/06/2017 01:02 PM, Arnd Bergmann wrote: The new hpwdt_my_nmi() function is used conditionally, which produces a harmless warning in some configurations: drivers/watchdog/hpwdt.c:478:12: error: 'hpwdt_my_nmi' defined but not used [-Werror=unused-function] This moves it inside of the

[PATCH 3/5] leaking_addresses: add range check for vsyscall memory

Currently script checks only first and last address in the vsyscall memory range. We can do better than this. When checking for false positives against $match, convert $match to a hexadecimal value then check if it lies within the range of vsyscall addresses. Signed-off-by: Tobin C. Harding

[PATCH 3/5] leaking_addresses: add range check for vsyscall memory

Currently script checks only first and last address in the vsyscall memory range. We can do better than this. When checking for false positives against $match, convert $match to a hexadecimal value then check if it lies within the range of vsyscall addresses. Signed-off-by: Tobin C. Harding ---

[PATCH 5/5] leaking_addresses: add support for 5 page table levels

Currently script only supports 4 page table levels because of the way the kernel address regular expression is crafted. We can do better than this. Using previously added support for kernel configuration options we can get the number of page table levels defined by CONFIG_PGTABLE_LEVELS. Using

[PATCH 5/5] leaking_addresses: add support for 5 page table levels

Currently script only supports 4 page table levels because of the way the kernel address regular expression is crafted. We can do better than this. Using previously added support for kernel configuration options we can get the number of page table levels defined by CONFIG_PGTABLE_LEVELS. Using

[PATCH 4/5] leaking_addresses: add support for kernel config file

Features that rely on the ability to get kernel configuration options are ready to be implemented in script. In preparation for this we can add support for kernel config options as a separate patch to ease review. Add support for locating and parsing kernel configuration file. Signed-off-by:

[PATCH 1/5] leaking_addresses: remove command examples

Currently help output includes command examples. These were cute when we first started development of this script but are unnecessary. Remove command examples. Signed-off-by: Tobin C. Harding --- scripts/leaking_addresses.pl | 11 --- 1 file changed, 11 deletions(-)

[PATCH 0/5] leaking_addresses: support 5 page table level

This set adds support for 5 page table levels on x86_64. Patch 1 and 2 are clean up. Patch 3 adds checking vsyscall memory region instead of just first and last address. Patch 4 adds support for locating and parsing the current kernel config file. It feels like this may be re-inventing the

[PATCH 2/5] leaking_addresses: indent dependant options

A number of the command line options to script are dependant on the option --input-raw being set. If we indent these options it makes explicit this dependency. Indent options dependant on --raw-input. Signed-off-by: Tobin C. Harding --- scripts/leaking_addresses.pl | 16

[PATCH 4/5] leaking_addresses: add support for kernel config file

Features that rely on the ability to get kernel configuration options are ready to be implemented in script. In preparation for this we can add support for kernel config options as a separate patch to ease review. Add support for locating and parsing kernel configuration file. Signed-off-by:

[PATCH 1/5] leaking_addresses: remove command examples

Currently help output includes command examples. These were cute when we first started development of this script but are unnecessary. Remove command examples. Signed-off-by: Tobin C. Harding --- scripts/leaking_addresses.pl | 11 --- 1 file changed, 11 deletions(-) diff --git

[PATCH 0/5] leaking_addresses: support 5 page table level

This set adds support for 5 page table levels on x86_64. Patch 1 and 2 are clean up. Patch 3 adds checking vsyscall memory region instead of just first and last address. Patch 4 adds support for locating and parsing the current kernel config file. It feels like this may be re-inventing the

[PATCH 2/5] leaking_addresses: indent dependant options

A number of the command line options to script are dependant on the option --input-raw being set. If we indent these options it makes explicit this dependency. Indent options dependant on --raw-input. Signed-off-by: Tobin C. Harding --- scripts/leaking_addresses.pl | 16 1

Re: [PATCH v4] leaking_addresses: add support for x86 32-bit kernel addresses

On Thu, Dec 07, 2017 at 08:47:36AM +0530, kaiwan.billimo...@gmail.com wrote: > Currently, leaking_addresses.pl only supports scanning 64 bit > architectures. This is due to how the regular expressions are formed. We > can do better than this. 32 architectures can be supported if we take > into

Re: [PATCH v4] leaking_addresses: add support for x86 32-bit kernel addresses

On Thu, Dec 07, 2017 at 08:47:36AM +0530, kaiwan.billimo...@gmail.com wrote: > Currently, leaking_addresses.pl only supports scanning 64 bit > architectures. This is due to how the regular expressions are formed. We > can do better than this. 32 architectures can be supported if we take > into

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

he SCSI error handler gets woken > > up") > > > > I have used the scsi-mkp tree from next-20171206 for today. > > Does that mean I'm the first one who added RCU code to the SCSI core? The only other uses of init_rcu_head() are in drivers/iommu/intel-svm.c and kernel/irq/irqdesc.c. destroy_rcu_head() appears to not be used anywhere ... -- Cheers, Stephen Rothwell

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

gt; > ERROR: "init_rcu_head" [drivers/scsi/scsi_mod.ko] undefined! > > ERROR: "destroy_rcu_head" [drivers/scsi/scsi_mod.ko] undefined! > > > > Caused by commit > > > > ac90420f17c9 ("scsi: core: Ensure that the SCSI error handler get

Re: [PATCH v3 1/4] kaslr: add immovable_mem=nn[KMG]@ss[KMG] to specify extracting memory

Hi All, At 12/07/2017 11:56 AM, Chao Fan wrote: On Thu, Dec 07, 2017 at 11:09:24AM +0800, Baoquan He wrote: On 12/07/17 at 10:53am, Chao Fan wrote: On Wed, Dec 06, 2017 at 05:35:57PM +0800, Baoquan He wrote: Hi Chao, Yes, now the code looks much better than the last version. On 12/05/17 at

Re: [PATCH v3 1/4] kaslr: add immovable_mem=nn[KMG]@ss[KMG] to specify extracting memory

Hi All, At 12/07/2017 11:56 AM, Chao Fan wrote: On Thu, Dec 07, 2017 at 11:09:24AM +0800, Baoquan He wrote: On 12/07/17 at 10:53am, Chao Fan wrote: On Wed, Dec 06, 2017 at 05:35:57PM +0800, Baoquan He wrote: Hi Chao, Yes, now the code looks much better than the last version. On 12/05/17 at

Re: [PATCH v3] scripts: leaking_addresses: add support for 32-bit kernel addresses

On Thu, 2017-12-07 at 10:01 +1100, Tobin C. Harding wrote: > On Wed, Dec 06, 2017 at 05:21:30PM +0530, kaiwan.billimo...@gmail.com wrote: > > On Wed, 2017-12-06 at 15:04 +1100, Tobin C. Harding wrote: > > > > > Sure, lets try for a generic ver! > > Cool. > > > Thanks for your help on this.. >

Re: [PATCH v3] scripts: leaking_addresses: add support for 32-bit kernel addresses

On Thu, 2017-12-07 at 10:01 +1100, Tobin C. Harding wrote: > On Wed, Dec 06, 2017 at 05:21:30PM +0530, kaiwan.billimo...@gmail.com wrote: > > On Wed, 2017-12-06 at 15:04 +1100, Tobin C. Harding wrote: > > > > > Sure, lets try for a generic ver! > > Cool. > > > Thanks for your help on this.. >

Re: [PATCH] docs: add documentation on printing kernel addresses

On Wed, Dec 06, 2017 at 04:43:40PM -0800, Kees Cook wrote: > On Wed, Dec 6, 2017 at 4:26 PM, Tobin C. Harding wrote: > > Hashing addresses printed with printk specifier %p was implemented > > recently. During development a number of issues were raised regarding > > leaking kernel

Re: [PATCH] docs: add documentation on printing kernel addresses

On Wed, Dec 06, 2017 at 04:43:40PM -0800, Kees Cook wrote: > On Wed, Dec 6, 2017 at 4:26 PM, Tobin C. Harding wrote: > > Hashing addresses printed with printk specifier %p was implemented > > recently. During development a number of issues were raised regarding > > leaking kernel addresses to

Re: [PATCH] NFS: allow name_to_handle_at() to work for Amazon EFS.

On Thu, Dec 7, 2017 at 5:20 AM, NeilBrown wrote: > On Wed, Dec 06 2017, Linus Torvalds wrote: > >> On Thu, Nov 30, 2017 at 12:56 PM, NeilBrown wrote: >>> >>> -/* limit the handle size to NFSv4 handle size now */ >>> -#define MAX_HANDLE_SZ 128 >>> +/* Must be

Re: [PATCH] NFS: allow name_to_handle_at() to work for Amazon EFS.

On Thu, Dec 7, 2017 at 5:20 AM, NeilBrown wrote: > On Wed, Dec 06 2017, Linus Torvalds wrote: > >> On Thu, Nov 30, 2017 at 12:56 PM, NeilBrown wrote: >>> >>> -/* limit the handle size to NFSv4 handle size now */ >>> -#define MAX_HANDLE_SZ 128 >>> +/* Must be larger than NFSv4 file handle, but

Re: [PATCH v3 10/15] ARM: dts: sun8i: a83t: Add display pipeline

On Tue, Dec 5, 2017 at 11:10 PM, Maxime Ripard wrote: > The display pipeline on the A83T is mainly composed of the mixers and > TCONs, plus various encoders. > > Let's add the first mixer and TCON to the DTSI since the only board I have > can use only the LVDS

Re: [PATCH v3 10/15] ARM: dts: sun8i: a83t: Add display pipeline

On Tue, Dec 5, 2017 at 11:10 PM, Maxime Ripard wrote: > The display pipeline on the A83T is mainly composed of the mixers and > TCONs, plus various encoders. > > Let's add the first mixer and TCON to the DTSI since the only board I have > can use only the LVDS output on the first TCON. The other

Re: [PATCH RESEND v3 4/4] MIPS: Loongson64: Load platform device during boot

Hi Jiaxun, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.15-rc2 next-20171206] [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

Re: [PATCH RESEND v3 4/4] MIPS: Loongson64: Load platform device during boot

Hi Jiaxun, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.15-rc2 next-20171206] [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

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

drivers/scsi/scsi_mod.ko] undefined! > > Caused by commit > > ac90420f17c9 ("scsi: core: Ensure that the SCSI error handler gets woken > up") > > I have used the scsi-mkp tree from next-20171206 for today. Does that mean I'm the first one who added RCU code to

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

drivers/scsi/scsi_mod.ko] undefined! > > Caused by commit > > ac90420f17c9 ("scsi: core: Ensure that the SCSI error handler gets woken > up") > > I have used the scsi-mkp tree from next-20171206 for today. Does that mean I'm the first one who added RCU code to

Re: [PATCH v3 03/15] dt-bindings: display: sun4i-drm: Add LVDS properties

On Tue, Dec 5, 2017 at 11:10 PM, Maxime Ripard wrote: > Some clocks and resets supposed to drive the LVDS logic in the display > engine have been overlooked when the driver was first introduced. > > Add those additional resources to the binding, and we'll deal

Re: [PATCH v3 03/15] dt-bindings: display: sun4i-drm: Add LVDS properties

On Tue, Dec 5, 2017 at 11:10 PM, Maxime Ripard wrote: > Some clocks and resets supposed to drive the LVDS logic in the display > engine have been overlooked when the driver was first introduced. > > Add those additional resources to the binding, and we'll deal with the ABI > stability in the

Re: [PATCH v3 08/21] fpga: add Intel FPGA DFL PCIe device

On Wed, Dec 06, 2017 at 09:34:14AM +, David Laight wrote: > From: Wu Hao > > Sent: 05 December 2017 03:34 > ... > > > I don't see anything Intel specific here. This could all be named dfl-* > > > > The maybe some device specific things, e.g Intel FPGA devices supported by > > this > >

Re: [PATCH v3 08/21] fpga: add Intel FPGA DFL PCIe device

On Wed, Dec 06, 2017 at 09:34:14AM +, David Laight wrote: > From: Wu Hao > > Sent: 05 December 2017 03:34 > ... > > > I don't see anything Intel specific here. This could all be named dfl-* > > > > The maybe some device specific things, e.g Intel FPGA devices supported by > > this > >

linux-next: build failure after merge of the scsi-mkp tree

("scsi: core: Ensure that the SCSI error handler gets woken up") I have used the scsi-mkp tree from next-20171206 for today. -- Cheers, Stephen Rothwell

linux-next: build failure after merge of the scsi-mkp tree

("scsi: core: Ensure that the SCSI error handler gets woken up") I have used the scsi-mkp tree from next-20171206 for today. -- Cheers, Stephen Rothwell

Re: [PATCH v3 1/4] kaslr: add immovable_mem=nn[KMG]@ss[KMG] to specify extracting memory

On Thu, Dec 07, 2017 at 11:09:24AM +0800, Baoquan He wrote: >On 12/07/17 at 10:53am, Chao Fan wrote: >> On Wed, Dec 06, 2017 at 05:35:57PM +0800, Baoquan He wrote: >> >Hi Chao, >> > >> >Yes, now the code looks much better than the last version. >> > >> >On 12/05/17 at 04:51pm, Chao Fan wrote: >>

Re: [PATCH v3 1/4] kaslr: add immovable_mem=nn[KMG]@ss[KMG] to specify extracting memory

On Thu, Dec 07, 2017 at 11:09:24AM +0800, Baoquan He wrote: >On 12/07/17 at 10:53am, Chao Fan wrote: >> On Wed, Dec 06, 2017 at 05:35:57PM +0800, Baoquan He wrote: >> >Hi Chao, >> > >> >Yes, now the code looks much better than the last version. >> > >> >On 12/05/17 at 04:51pm, Chao Fan wrote: >>

RE: [PATCH 2/2] staging: fsl-mc: do not print error in case of defer probe error

> -Original Message- > From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: Wednesday, December 06, 2017 16:46 > To: Nipun Gupta > Cc: Laurentiu Tudor ; stuyo...@gmail.com; Bharat > Bhushan ; cakt...@gmail.com; >

RE: [PATCH 2/2] staging: fsl-mc: do not print error in case of defer probe error

> -Original Message- > From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: Wednesday, December 06, 2017 16:46 > To: Nipun Gupta > Cc: Laurentiu Tudor ; stuyo...@gmail.com; Bharat > Bhushan ; cakt...@gmail.com; > bretth...@gmail.com; a...@arndb.de; de...@driverdev.osuosl.org;

RE: [PATCH] [linux][master][v1] devicetree: misc: Add binding for logicoreIP xlnx,vcu

> -Original Message- > From: Rob Herring [mailto:r...@kernel.org] > Sent: Wednesday, December 06, 2017 1:49 PM > To: Dhaval Rajeshbhai Shah > Cc: mark.rutl...@arm.com; devicet...@vger.kernel.org; linux- > ker...@vger.kernel.org; michal.si...@xilinx.com; Hyun Kwon >

RE: [PATCH] [linux][master][v1] devicetree: misc: Add binding for logicoreIP xlnx,vcu

> -Original Message- > From: Rob Herring [mailto:r...@kernel.org] > Sent: Wednesday, December 06, 2017 1:49 PM > To: Dhaval Rajeshbhai Shah > Cc: mark.rutl...@arm.com; devicet...@vger.kernel.org; linux- > ker...@vger.kernel.org; michal.si...@xilinx.com; Hyun Kwon > ; Dhaval Rajeshbhai

Re: [PATCH v3 04/15] dt-bindings: display: sun4i-drm: Add A83T pipeline

On Thu, Dec 7, 2017 at 5:59 AM, Rob Herring wrote: > On Tue, Dec 05, 2017 at 04:10:16PM +0100, Maxime Ripard wrote: >> The A83T has two video pipelines in parallel that looks quite similar to >> the other SoCs. >> >> The video planes are handled through a controller called the

Re: [PATCH v3 04/15] dt-bindings: display: sun4i-drm: Add A83T pipeline

On Thu, Dec 7, 2017 at 5:59 AM, Rob Herring wrote: > On Tue, Dec 05, 2017 at 04:10:16PM +0100, Maxime Ripard wrote: >> The A83T has two video pipelines in parallel that looks quite similar to >> the other SoCs. >> >> The video planes are handled through a controller called the mixer, and the >>

Re: [PATCH 3/3] tools/perf/jvmti: generate correct debug information for inlined code

Hi, On Wed, Nov 29, 2017 at 8:27 AM, Ben Gainey wrote: > On Wed, 2017-11-29 at 05:02 -0800, Stephane Eranian wrote: >> On Thu, Nov 23, 2017 at 7:22 AM, Arnaldo Carvalho de Melo >> wrote: >> > >> > Em Wed, Nov 22, 2017 at 06:25:41PM -0600, Kim Phillips

Re: [PATCH v3 14/15] ARM: dts: sun8i: a711: Reinstate the PMIC compatible

On Tue, Dec 5, 2017 at 11:10 PM, Maxime Ripard wrote: > When we added the regulator support in commit 90c5d7cdae64 ("ARM: dts: > sun8i: a711: Add regulator support"), we also dropped the PMIC's > compatible. Since it's not in the PMIC DTSI, unlike most other PMIC

Re: [PATCH 3/3] tools/perf/jvmti: generate correct debug information for inlined code

Hi, On Wed, Nov 29, 2017 at 8:27 AM, Ben Gainey wrote: > On Wed, 2017-11-29 at 05:02 -0800, Stephane Eranian wrote: >> On Thu, Nov 23, 2017 at 7:22 AM, Arnaldo Carvalho de Melo >> wrote: >> > >> > Em Wed, Nov 22, 2017 at 06:25:41PM -0600, Kim Phillips escreveu: >> > > From: Ben Gainey >> > >

Re: [PATCH v3 14/15] ARM: dts: sun8i: a711: Reinstate the PMIC compatible

On Tue, Dec 5, 2017 at 11:10 PM, Maxime Ripard wrote: > When we added the regulator support in commit 90c5d7cdae64 ("ARM: dts: > sun8i: a711: Add regulator support"), we also dropped the PMIC's > compatible. Since it's not in the PMIC DTSI, unlike most other PMIC > DTSI, it obviously wasn't

Re: [PATCH 2/2] arm64: allwinner: a64: bananapi-m64: add usb otg

On Thu, Dec 7, 2017 at 1:51 AM, Jagan Teki wrote: > usb otg on bananapi-m64 has configured with USB-ID with PH9 > and USB-DRVVBUS attached with dcdc1 regulatort. That is not how you read the schematic... Intersecting lines that are tied together will have a dot

Re: [PATCH 2/2] arm64: allwinner: a64: bananapi-m64: add usb otg

On Thu, Dec 7, 2017 at 1:51 AM, Jagan Teki wrote: > usb otg on bananapi-m64 has configured with USB-ID with PH9 > and USB-DRVVBUS attached with dcdc1 regulatort. That is not how you read the schematic... Intersecting lines that are tied together will have a dot representing the connection. The

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