[PATCH 1/2] rtc: omap: Fix selecting external osc

From: Lokesh Vutla RTC can be clocked from an external 32KHz oscillator, or from the Peripheral PLL. The RTC has an internal oscillator buffer to support direct operation with a crystal. | Device

[PATCH 1/2] rtc: omap: Fix selecting external osc

From: Lokesh Vutla RTC can be clocked from an external 32KHz oscillator, or from the Peripheral PLL. The RTC has an internal oscillator buffer to support direct operation with a crystal. | Device - |

[PATCH 2/2] rtc: omap: prevent disabling of clock/module during suspend

From: Tero Kristo If RTC is running from an internal clock source, the RTC module can't be disabled; otherwise it stops ticking completely. Current suspend handler implementation disables the clock/module unconditionally, instead fix this by disabling the clock only if we are

[PATCH 2/2] rtc: omap: prevent disabling of clock/module during suspend

From: Tero Kristo If RTC is running from an internal clock source, the RTC module can't be disabled; otherwise it stops ticking completely. Current suspend handler implementation disables the clock/module unconditionally, instead fix this by disabling the clock only if we are running on external

Re: [PATCH] net: avoid uninitialized variable

On 2016/10/27 12:02, Gao Feng wrote: > On Thu, Oct 27, 2016 at 11:56 AM, zhongjiang wrote: >> From: zhong jiang >> >> when I compiler the newest kernel, I hit the following error with >> Werror=may-uninitalized. >> >> net/core/flow_dissector.c: In

Re: [PATCH] net: avoid uninitialized variable

On 2016/10/27 12:02, Gao Feng wrote: > On Thu, Oct 27, 2016 at 11:56 AM, zhongjiang wrote: >> From: zhong jiang >> >> when I compiler the newest kernel, I hit the following error with >> Werror=may-uninitalized. >> >> net/core/flow_dissector.c: In function ?._skb_flow_dissect? >>

stm32-usart.c:undefined reference to `bad_dma_ops'

Hi Alexandre, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 9fe68cad6e74967b88d0c6aeca7d9cd6b6e91942 commit: 3489187204eb75e5635d8836babfd0a18be613f4 serial: stm32: adding dma support date: 5 weeks ago config:

stm32-usart.c:undefined reference to `bad_dma_ops'

Hi Alexandre, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 9fe68cad6e74967b88d0c6aeca7d9cd6b6e91942 commit: 3489187204eb75e5635d8836babfd0a18be613f4 serial: stm32: adding dma support date: 5 weeks ago config:

RE: [PATCH 2/3] usb: dwc3: host: Do not use dma_set_coherent_mask

>From: Arnd Bergmann [mailto:a...@arndb.de] >On Tuesday, October 25, 2016 4:26:27 PM CEST Sriram Dash wrote: >> Do not require dma_set_coherent_mask for hcd >> >> Signed-off-by: Arnd Bergmann > >Aside from the comments I had for patch 3, you are doing two different things >here: >

RE: [PATCH 2/3] usb: dwc3: host: Do not use dma_set_coherent_mask

>From: Arnd Bergmann [mailto:a...@arndb.de] >On Tuesday, October 25, 2016 4:26:27 PM CEST Sriram Dash wrote: >> Do not require dma_set_coherent_mask for hcd >> >> Signed-off-by: Arnd Bergmann > >Aside from the comments I had for patch 3, you are doing two different things >here: > >> diff --git

Re: [PATCH] pci: Don't set RCB bit in LNKCTL if the upstream bridge hasn't

On 10/26/2016 09:43 PM, Bjorn Helgaas wrote: > Hi Johannes, > > On Wed, Oct 26, 2016 at 03:53:34PM +0200, Johannes Thumshirn wrote: >> The Read Completion Boundary bit must only be set on a device or endpoint if >> it is set on the upstream bridge. >> >> Fixes: 7a1562d4f ("PCI: Apply _HPX Link

Re: [PATCH] pci: Don't set RCB bit in LNKCTL if the upstream bridge hasn't

On 10/26/2016 09:43 PM, Bjorn Helgaas wrote: > Hi Johannes, > > On Wed, Oct 26, 2016 at 03:53:34PM +0200, Johannes Thumshirn wrote: >> The Read Completion Boundary bit must only be set on a device or endpoint if >> it is set on the upstream bridge. >> >> Fixes: 7a1562d4f ("PCI: Apply _HPX Link

Re: bio linked list corruption.

On Tue, Oct 25, 2016 at 08:27:52PM -0400, Dave Jones wrote: > DaveC: Do these look like real problems, or is this more "looks like > random memory corruption" ? It's been a while since I did some stress > testing on XFS, so these might not be new.. > > XFS: Assertion failed: oldlen > newlen,

Re: bio linked list corruption.

On Tue, Oct 25, 2016 at 08:27:52PM -0400, Dave Jones wrote: > DaveC: Do these look like real problems, or is this more "looks like > random memory corruption" ? It's been a while since I did some stress > testing on XFS, so these might not be new.. > > XFS: Assertion failed: oldlen > newlen,

Re: linux-next: Tree for Oct 26 (crypto/acompress.ko)

Hi, On Wed, Oct 26, 2016 at 07:54:00PM -0400, Paul Gortmaker wrote: > So, no EXPORT_SYMBOL, and any .config which has ACOMP2=m will fail. I sent a patch for this: https://patchwork.kernel.org/patch/9396503/ Regards, -- Giovanni

Re: linux-next: Tree for Oct 26 (crypto/acompress.ko)

Hi, On Wed, Oct 26, 2016 at 07:54:00PM -0400, Paul Gortmaker wrote: > So, no EXPORT_SYMBOL, and any .config which has ACOMP2=m will fail. I sent a patch for this: https://patchwork.kernel.org/patch/9396503/ Regards, -- Giovanni

Re: [PATCH 4.8 000/140] 4.8.5-stable review

On Wed, Oct 26, 2016 at 02:49:41PM -0700, Guenter Roeck wrote: > On Wed, Oct 26, 2016 at 02:21:00PM +0200, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.8.5 release. > > There are 140 patches in this series, all will be posted as a response > > to this one.

Re: [PATCH 4.8 000/140] 4.8.5-stable review

On Wed, Oct 26, 2016 at 12:44:58PM -0600, Shuah Khan wrote: > On 10/26/2016 06:21 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.8.5 release. > > There are 140 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [PATCH 4.8 000/140] 4.8.5-stable review

On Wed, Oct 26, 2016 at 02:49:41PM -0700, Guenter Roeck wrote: > On Wed, Oct 26, 2016 at 02:21:00PM +0200, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.8.5 release. > > There are 140 patches in this series, all will be posted as a response > > to this one.

Re: [PATCH 4.8 000/140] 4.8.5-stable review

On Wed, Oct 26, 2016 at 12:44:58PM -0600, Shuah Khan wrote: > On 10/26/2016 06:21 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.8.5 release. > > There are 140 patches in this series, all will be posted as a response > > to this one. If anyone has any

ATTENZIONE;

ATTENZIONE; La cassetta postale ha superato il limite di archiviazione, che è 5 GB come definiti dall'amministratore, che è attualmente in esecuzione su 10.9GB, non si può essere in grado di inviare o ricevere nuovi messaggi fino a ri-convalidare la tua mailbox. Per rinnovare la vostra casella

ATTENZIONE;

ATTENZIONE; La cassetta postale ha superato il limite di archiviazione, che è 5 GB come definiti dall'amministratore, che è attualmente in esecuzione su 10.9GB, non si può essere in grado di inviare o ricevere nuovi messaggi fino a ri-convalidare la tua mailbox. Per rinnovare la vostra casella

RE: [v12, 5/8] soc: fsl: add GUTS driver for QorIQ platforms

Hi Scott, > -Original Message- > From: Scott Wood [mailto:o...@buserror.net] > Sent: Thursday, October 27, 2016 1:06 AM > To: Y.B. Lu; linux-...@vger.kernel.org; ulf.hans...@linaro.org; Arnd > Bergmann > Cc: linuxppc-...@lists.ozlabs.org; devicet...@vger.kernel.org; linux-arm- >

RE: [v12, 5/8] soc: fsl: add GUTS driver for QorIQ platforms

Hi Scott, > -Original Message- > From: Scott Wood [mailto:o...@buserror.net] > Sent: Thursday, October 27, 2016 1:06 AM > To: Y.B. Lu; linux-...@vger.kernel.org; ulf.hans...@linaro.org; Arnd > Bergmann > Cc: linuxppc-...@lists.ozlabs.org; devicet...@vger.kernel.org; linux-arm- >

Re: [PATCH v2 2/3] use a nocache copy for bvecs and kvecs in copy_from_iter_nocache()

On Wed, Oct 26, 2016 at 10:50:20AM -0500, Brian Boylston wrote: > Update copy_from_iter_nocache() to use memcpy_nocache() > for bvecs and kvecs. > > Cc: Ross Zwisler > Cc: Thomas Gleixner > Cc: Ingo Molnar > Cc: "H. Peter

Re: [PATCH v2 2/3] use a nocache copy for bvecs and kvecs in copy_from_iter_nocache()

On Wed, Oct 26, 2016 at 10:50:20AM -0500, Brian Boylston wrote: > Update copy_from_iter_nocache() to use memcpy_nocache() > for bvecs and kvecs. > > Cc: Ross Zwisler > Cc: Thomas Gleixner > Cc: Ingo Molnar > Cc: "H. Peter Anvin" > Cc: > Cc: Al Viro > Cc: Dan Williams > Signed-off-by: Brian

[PATCH v6 1/2] x86/msr: Add write msr notrace

From: Wanpeng Li Add write msr notrace, it will be used by later patch. Suggested-by: Peter Zijlstra Suggested-by: Paolo Bonzini Cc: Ingo Molnar Cc: Mike Galbraith Cc: Peter Zijlstra

[PATCH v6 2/2] x86/apic: x2apic write eoi msr notrace

From: Wanpeng Li | RCU used illegally from idle CPU! | rcu_scheduler_active = 1, debug_locks = 0 | RCU used illegally from extended quiescent state! | no locks held by swapper/1/0. | | [] do_trace_write_msr+0x135/0x140 | [] native_write_msr+0x20/0x30 | []

[PATCH v6 1/2] x86/msr: Add write msr notrace

From: Wanpeng Li Add write msr notrace, it will be used by later patch. Suggested-by: Peter Zijlstra Suggested-by: Paolo Bonzini Cc: Ingo Molnar Cc: Mike Galbraith Cc: Peter Zijlstra Cc: Thomas Gleixner Cc: Paolo Bonzini Cc: Borislav Petkov Signed-off-by: Wanpeng Li ---

[PATCH v6 2/2] x86/apic: x2apic write eoi msr notrace

From: Wanpeng Li | RCU used illegally from idle CPU! | rcu_scheduler_active = 1, debug_locks = 0 | RCU used illegally from extended quiescent state! | no locks held by swapper/1/0. | | [] do_trace_write_msr+0x135/0x140 | [] native_write_msr+0x20/0x30 | [] native_apic_msr_eoi_write+0x1d/0x30

Re: [RFC 0/8] Define coherent device memory node

On 10/26/2016 09:32 PM, Jerome Glisse wrote: > On Wed, Oct 26, 2016 at 04:43:10PM +0530, Anshuman Khandual wrote: >> On 10/26/2016 12:22 AM, Jerome Glisse wrote: >>> On Tue, Oct 25, 2016 at 11:01:08PM +0530, Aneesh Kumar K.V wrote: Jerome Glisse writes: > On Tue,

[PATCH v6 0/2] x86/apic: x2apic write eoi msr notrace

| RCU used illegally from idle CPU! | rcu_scheduler_active = 1, debug_locks = 0 | RCU used illegally from extended quiescent state! | no locks held by swapper/1/0. | | [] do_trace_write_msr+0x135/0x140 | [] native_write_msr+0x20/0x30 | [] native_apic_msr_eoi_write+0x1d/0x30 | []

Re: [RFC 0/8] Define coherent device memory node

On 10/26/2016 09:32 PM, Jerome Glisse wrote: > On Wed, Oct 26, 2016 at 04:43:10PM +0530, Anshuman Khandual wrote: >> On 10/26/2016 12:22 AM, Jerome Glisse wrote: >>> On Tue, Oct 25, 2016 at 11:01:08PM +0530, Aneesh Kumar K.V wrote: Jerome Glisse writes: > On Tue, Oct 25, 2016 at

[PATCH v6 0/2] x86/apic: x2apic write eoi msr notrace

| RCU used illegally from idle CPU! | rcu_scheduler_active = 1, debug_locks = 0 | RCU used illegally from extended quiescent state! | no locks held by swapper/1/0. | | [] do_trace_write_msr+0x135/0x140 | [] native_write_msr+0x20/0x30 | [] native_apic_msr_eoi_write+0x1d/0x30 | []

[GIT PULL] Keys fixes

Please pull these fixes from David Howells: (1) Fix a buffer overflow when displaying /proc/keys [CVE-2016-7042]. (2) Fix broken initialisation in the big_key implementation that can result in an oops. (3) Make big_key depend on having a random number generator available in

[GIT PULL] Keys fixes

Please pull these fixes from David Howells: (1) Fix a buffer overflow when displaying /proc/keys [CVE-2016-7042]. (2) Fix broken initialisation in the big_key implementation that can result in an oops. (3) Make big_key depend on having a random number generator available in

Re: [PATCH] video: backlight: pwm_bl: Initialize fb_bl_on[x] and use_count during pwm_backlight_probe()

Hi Jingoo, > On Monday, October 24, 2016, Lukasz Majewski wrote: > > > > Hi Jingoo, > > > > > On Saturday, October 22, 2016, Lukasz Majewski wrote: > > > > > > > > The commit: a55944ca82d287ca099ca90413af857af9086773 has posed > > > > some extra > > Please add the 'subject' of patch as below.

Re: [PATCH] video: backlight: pwm_bl: Initialize fb_bl_on[x] and use_count during pwm_backlight_probe()

Hi Jingoo, > On Monday, October 24, 2016, Lukasz Majewski wrote: > > > > Hi Jingoo, > > > > > On Saturday, October 22, 2016, Lukasz Majewski wrote: > > > > > > > > The commit: a55944ca82d287ca099ca90413af857af9086773 has posed > > > > some extra > > Please add the 'subject' of patch as below.

Re: [PATCH] net: avoid uninitialized variable

On Thu, Oct 27, 2016 at 11:56 AM, zhongjiang wrote: > From: zhong jiang > > when I compiler the newest kernel, I hit the following error with > Werror=may-uninitalized. > > net/core/flow_dissector.c: In function ?._skb_flow_dissect? >

Re: [PATCH] net: avoid uninitialized variable

On Thu, Oct 27, 2016 at 11:56 AM, zhongjiang wrote: > From: zhong jiang > > when I compiler the newest kernel, I hit the following error with > Werror=may-uninitalized. > > net/core/flow_dissector.c: In function ?._skb_flow_dissect? > include/uapi/linux/swab.h:100:46: error: ?.lan?.may be used

[PATCH] net: avoid uninitialized variable

From: zhong jiang when I compiler the newest kernel, I hit the following error with Werror=may-uninitalized. net/core/flow_dissector.c: In function ?._skb_flow_dissect? include/uapi/linux/swab.h:100:46: error: ?.lan?.may be used uninitialized in this function

[PATCH] net: avoid uninitialized variable

From: zhong jiang when I compiler the newest kernel, I hit the following error with Werror=may-uninitalized. net/core/flow_dissector.c: In function ?._skb_flow_dissect? include/uapi/linux/swab.h:100:46: error: ?.lan?.may be used uninitialized in this function [-Werror=maybe-uninitialized]

Re: [PATCH 2/2] arm64/numa: support HAVE_MEMORYLESS_NODES

On 2016/10/27 2:36, Will Deacon wrote: > On Tue, Oct 25, 2016 at 10:59:18AM +0800, Zhen Lei wrote: >> Some numa nodes may have no memory. For example: >> 1) a node has no memory bank plugged. >> 2) a node has no memory bank slots. >> >> To ensure percpu variable areas and numa control blocks of

Re: [PATCH 2/2] arm64/numa: support HAVE_MEMORYLESS_NODES

On 2016/10/27 2:36, Will Deacon wrote: > On Tue, Oct 25, 2016 at 10:59:18AM +0800, Zhen Lei wrote: >> Some numa nodes may have no memory. For example: >> 1) a node has no memory bank plugged. >> 2) a node has no memory bank slots. >> >> To ensure percpu variable areas and numa control blocks of

[PATCH V3] mfd: wm8994-core: Don't use managed regulator bulk get API

The kernel WARNs and then crashes today if wm8994_device_init() fails after calling devm_regulator_bulk_get(). That happens because there are multiple devices involved here and the order in which resources are freed isn't correct. The regulators are added as children of wm8994->dev.

[PATCH V3] mfd: wm8994-core: Don't use managed regulator bulk get API

The kernel WARNs and then crashes today if wm8994_device_init() fails after calling devm_regulator_bulk_get(). That happens because there are multiple devices involved here and the order in which resources are freed isn't correct. The regulators are added as children of wm8994->dev.

Re: [PATCH] cpufreq: dt: add Socionext UniPhier SoCs support

On 27-10-16, 01:41, Masahiro Yamada wrote: > Add compatible strings for Pro5, PXs2, LD6b, LD11, LD20 SoCs to use > the generic cpufreq driver. > > Signed-off-by: Masahiro Yamada > --- > > drivers/cpufreq/cpufreq-dt-platdev.c | 6 ++ > 1 file changed, 6

Re: [PATCH] cpufreq: dt: add Socionext UniPhier SoCs support

On 27-10-16, 01:41, Masahiro Yamada wrote: > Add compatible strings for Pro5, PXs2, LD6b, LD11, LD20 SoCs to use > the generic cpufreq driver. > > Signed-off-by: Masahiro Yamada > --- > > drivers/cpufreq/cpufreq-dt-platdev.c | 6 ++ > 1 file changed, 6 insertions(+) Acked-by: Viresh Kumar

Re: [PATCH 1/2] ARM: dts: uniphier: add CPU clocks and OPP table for Pro5 SoC

On 27-10-16, 01:37, Masahiro Yamada wrote: > Add a CPU clock to every CPU node and a CPU OPP table to use the > generic cpufreq driver. > > Signed-off-by: Masahiro Yamada > --- > > arch/arm/boot/dts/uniphier-pro5.dtsi | 74 >

Re: [PATCH 1/2] ARM: dts: uniphier: add CPU clocks and OPP table for Pro5 SoC

On 27-10-16, 01:37, Masahiro Yamada wrote: > Add a CPU clock to every CPU node and a CPU OPP table to use the > generic cpufreq driver. > > Signed-off-by: Masahiro Yamada > --- > > arch/arm/boot/dts/uniphier-pro5.dtsi | 74 > > 1 file changed, 74

Re: [PATCH v2 3/4] usb: musb: da8xx: Add DT support for the DA8xx driver

On 10/26/2016 10:03 AM, Alexandre Bailon wrote: From: Petr Kulhavy This adds DT support for TI DA8xx/OMAP-L1x/AM17xx/AM18xx MUSB driver Signed-off-by: Petr Kulhavy Signed-off-by: Alexandre Bailon --- drivers/usb/musb/da8xx.c | 47

Re: [PATCH v2 2/4] usb: musb: core: added helper function for parsing DT

On 10/26/2016 10:03 AM, Alexandre Bailon wrote: From: Petr Kulhavy This adds the function musb_get_mode() to get the DT property "dr_mode" Signed-off-by: Petr Kulhavy Acked-by: Sergei Shtylyov Signed-off-by: Alexandre Bailon

Re: [PATCH v2 3/4] usb: musb: da8xx: Add DT support for the DA8xx driver

On 10/26/2016 10:03 AM, Alexandre Bailon wrote: From: Petr Kulhavy This adds DT support for TI DA8xx/OMAP-L1x/AM17xx/AM18xx MUSB driver Signed-off-by: Petr Kulhavy Signed-off-by: Alexandre Bailon --- drivers/usb/musb/da8xx.c | 47 +++ 1 file

Re: [PATCH v2 2/4] usb: musb: core: added helper function for parsing DT

On 10/26/2016 10:03 AM, Alexandre Bailon wrote: From: Petr Kulhavy This adds the function musb_get_mode() to get the DT property "dr_mode" Signed-off-by: Petr Kulhavy Acked-by: Sergei Shtylyov Signed-off-by: Alexandre Bailon --- drivers/usb/musb/musb_core.c | 19 +++

linux-next: Tree for Oct 27

Hi all, There will probably be no linux-next releases next week while I attend the Kernel Summit. Changes since 20161026: The akpm-current tree still had its build failures for which I applied 2 patches. Non-merge commits (relative to Linus' tree): 2802 3583 files changed, 220238 insertions

linux-next: Tree for Oct 27

Hi all, There will probably be no linux-next releases next week while I attend the Kernel Summit. Changes since 20161026: The akpm-current tree still had its build failures for which I applied 2 patches. Non-merge commits (relative to Linus' tree): 2802 3583 files changed, 220238 insertions

Re: [PATCH v5] x86/msr: Add write msr notrace to avoid the debug codes splash

2016-10-26 19:50 GMT+08:00 Borislav Petkov : > On Wed, Oct 26, 2016 at 07:35:26PM +0800, Wanpeng Li wrote: >> From: Wanpeng Li >> >> As Peterz pointed out: >> >> | The thing is, many many smp_reschedule_interrupt() invocations don't >> | actually execute

Re: [PATCH v5] x86/msr: Add write msr notrace to avoid the debug codes splash

2016-10-26 19:50 GMT+08:00 Borislav Petkov : > On Wed, Oct 26, 2016 at 07:35:26PM +0800, Wanpeng Li wrote: >> From: Wanpeng Li >> >> As Peterz pointed out: >> >> | The thing is, many many smp_reschedule_interrupt() invocations don't >> | actually execute anything much at all and are only send to

Re: [PATCH v3 1/1] kthread: allocate kthread structure using kmalloc

On Wed, Oct 26, 2016 at 04:14:00PM +0200, Oleg Nesterov wrote: > +/* > + * TODO: kill it and use to_kthread(). But we still need the users > + * like kthread_stop() which has to sync with the exiting kthread. > + */ > static struct kthread *to_live_kthread(struct task_struct *k) Now that the

Re: [PATCH v2 3/4] input: Deprecate real timestamps beyond year 2106

On Mon, Oct 17, 2016 at 08:27:32PM -0700, Deepa Dinamani wrote: > struct timeval is not y2038 safe. > All usage of timeval in the kernel will be replaced by > y2038 safe structures. > > struct input_event maintains time for each input event. > Real time timestamps are not ideal for input as this

Re: [PATCH v3 1/1] kthread: allocate kthread structure using kmalloc

On Wed, Oct 26, 2016 at 04:14:00PM +0200, Oleg Nesterov wrote: > +/* > + * TODO: kill it and use to_kthread(). But we still need the users > + * like kthread_stop() which has to sync with the exiting kthread. > + */ > static struct kthread *to_live_kthread(struct task_struct *k) Now that the

Re: [PATCH v2 3/4] input: Deprecate real timestamps beyond year 2106

On Mon, Oct 17, 2016 at 08:27:32PM -0700, Deepa Dinamani wrote: > struct timeval is not y2038 safe. > All usage of timeval in the kernel will be replaced by > y2038 safe structures. > > struct input_event maintains time for each input event. > Real time timestamps are not ideal for input as this

Re: [PATCH 6/8] autofs - use path_is_mountpoint() to fix unreliable d_mountpoint() checks

On Thu, 2016-10-27 at 03:17 +0100, Al Viro wrote: > On Tue, Oct 11, 2016 at 01:34:18PM +0800, Ian Kent wrote: > > > > + path = file->f_path; > > + > >   /* > >    * An empty directory in an autofs file system is always a > >    * mount point. The daemon must have failed to mount this > >

Re: [PATCH 6/8] autofs - use path_is_mountpoint() to fix unreliable d_mountpoint() checks

On Thu, 2016-10-27 at 03:17 +0100, Al Viro wrote: > On Tue, Oct 11, 2016 at 01:34:18PM +0800, Ian Kent wrote: > > > > + path = file->f_path; > > + > >   /* > >    * An empty directory in an autofs file system is always a > >    * mount point. The daemon must have failed to mount this > >

Re: [PATCH 6/5] KVM: x86: fix periodic lapic timer with hrtimers

2016-10-26 22:01 GMT+08:00 Radim Krčmář : > 2016-10-26 14:08+0800, Wanpeng Li: >> 2016-10-26 14:02 GMT+08:00 Wanpeng Li : >>> 2016-10-25 19:43 GMT+08:00 Radim Krčmář : I will have some comments, because it would be nicer if it

Re: [PATCH 6/5] KVM: x86: fix periodic lapic timer with hrtimers

2016-10-26 22:01 GMT+08:00 Radim Krčmář : > 2016-10-26 14:08+0800, Wanpeng Li: >> 2016-10-26 14:02 GMT+08:00 Wanpeng Li : >>> 2016-10-25 19:43 GMT+08:00 Radim Krčmář : I will have some comments, because it would be nicer if it measured the latency ... expected_expiration is not computed

Re: [PATCH 1/8] vfs - change d_manage() to take a struct path

On Thu, 2016-10-27 at 03:11 +0100, Al Viro wrote: > On Fri, Oct 21, 2016 at 07:39:36AM +0800, Ian Kent wrote: > > > > > Maybe Al has been too busy to comment, he has been on the Cc from the start. > That's... a very mild version of what's been going on.  Let's just say that > the last few weeks

Re: [PATCH 1/8] vfs - change d_manage() to take a struct path

On Thu, 2016-10-27 at 03:11 +0100, Al Viro wrote: > On Fri, Oct 21, 2016 at 07:39:36AM +0800, Ian Kent wrote: > > > > > Maybe Al has been too busy to comment, he has been on the Cc from the start. > That's... a very mild version of what's been going on.  Let's just say that > the last few weeks

Re: [PATCH 1/2] mm/memblock: prepare a capability to support memblock near alloc

On 2016/10/26 17:31, Michal Hocko wrote: > On Wed 26-10-16 11:10:44, Leizhen (ThunderTown) wrote: >> >> >> On 2016/10/25 21:23, Michal Hocko wrote: >>> On Tue 25-10-16 10:59:17, Zhen Lei wrote: If HAVE_MEMORYLESS_NODES is selected, and some memoryless numa nodes are actually exist. The

Re: [PATCH 1/2] mm/memblock: prepare a capability to support memblock near alloc

On 2016/10/26 17:31, Michal Hocko wrote: > On Wed 26-10-16 11:10:44, Leizhen (ThunderTown) wrote: >> >> >> On 2016/10/25 21:23, Michal Hocko wrote: >>> On Tue 25-10-16 10:59:17, Zhen Lei wrote: If HAVE_MEMORYLESS_NODES is selected, and some memoryless numa nodes are actually exist. The

Re: [PATCH v2 2/5] kconfig: introduce the "suggest" keyword

On Thu, 27 Oct 2016, Paul Bolle wrote: > On Tue, 2016-10-25 at 22:28 -0400, Nicolas Pitre wrote: > > Similar to "imply" but with no added restrictions on the target symbol's > > value. Useful for providing a default value to another symbol. > > > > Suggested by Edward Cree. > > > >

Re: [PATCH v2 2/5] kconfig: introduce the "suggest" keyword

On Thu, 27 Oct 2016, Paul Bolle wrote: > On Tue, 2016-10-25 at 22:28 -0400, Nicolas Pitre wrote: > > Similar to "imply" but with no added restrictions on the target symbol's > > value. Useful for providing a default value to another symbol. > > > > Suggested by Edward Cree. > > > >

Re: [PATCH v2 3/4] input: Deprecate real timestamps beyond year 2106

Hi Deepa, On Mon, Oct 17, 2016 at 08:27:32PM -0700, Deepa Dinamani wrote: > struct timeval is not y2038 safe. > All usage of timeval in the kernel will be replaced by > y2038 safe structures. > > struct input_event maintains time for each input event. > Real time timestamps are not ideal for

Re: [PATCH v2 3/4] input: Deprecate real timestamps beyond year 2106

Hi Deepa, On Mon, Oct 17, 2016 at 08:27:32PM -0700, Deepa Dinamani wrote: > struct timeval is not y2038 safe. > All usage of timeval in the kernel will be replaced by > y2038 safe structures. > > struct input_event maintains time for each input event. > Real time timestamps are not ideal for

[PATCH v4] drm/mediatek: fixed the calc method of data rate per lane

Tune dsi frame rate by pixel clock, dsi add some extra signal (i.e. Tlpx, Ths-prepare, Ths-zero, Ths-trail,Ths-exit) when enter and exit LP mode, those signals will cause h-time larger than normal and reduce FPS. So need to multiply a coefficient to offset the extra signal's effect.

[PATCH v4] drm/mediatek: fixed the calc method of data rate per lane

Tune dsi frame rate by pixel clock, dsi add some extra signal (i.e. Tlpx, Ths-prepare, Ths-zero, Ths-trail,Ths-exit) when enter and exit LP mode, those signals will cause h-time larger than normal and reduce FPS. So need to multiply a coefficient to offset the extra signal's effect.

Re: [PATCH 6/8] autofs - use path_is_mountpoint() to fix unreliable d_mountpoint() checks

On Tue, Oct 11, 2016 at 01:34:18PM +0800, Ian Kent wrote: > + path = file->f_path; > + > /* >* An empty directory in an autofs file system is always a >* mount point. The daemon must have failed to mount this > @@ -123,7 +126,7 @@ static int autofs4_dir_open(struct inode

Re: [PATCH 6/8] autofs - use path_is_mountpoint() to fix unreliable d_mountpoint() checks

On Tue, Oct 11, 2016 at 01:34:18PM +0800, Ian Kent wrote: > + path = file->f_path; > + > /* >* An empty directory in an autofs file system is always a >* mount point. The daemon must have failed to mount this > @@ -123,7 +126,7 @@ static int autofs4_dir_open(struct inode

Re: [PATCH 1/8] vfs - change d_manage() to take a struct path

On Fri, Oct 21, 2016 at 07:39:36AM +0800, Ian Kent wrote: > Maybe Al has been too busy to comment, he has been on the Cc from the start. That's... a very mild version of what's been going on. Let's just say that the last few weeks had been really interesting. Not that the shit has settled, but

Re: [PATCH 6/5] KVM: x86: fix periodic lapic timer with hrtimers

2016-10-26 21:32 GMT+08:00 Radim Krčmář : > 2016-10-26 14:02+0800, Wanpeng Li: >> 2016-10-25 19:43 GMT+08:00 Radim Krčmář : >>> 2016-10-25 07:39+0800, Wanpeng Li: 2016-10-24 23:27 GMT+08:00 Radim Krčmář : > 2016-10-24 17:09+0200,

Re: [PATCH 1/8] vfs - change d_manage() to take a struct path

On Fri, Oct 21, 2016 at 07:39:36AM +0800, Ian Kent wrote: > Maybe Al has been too busy to comment, he has been on the Cc from the start. That's... a very mild version of what's been going on. Let's just say that the last few weeks had been really interesting. Not that the shit has settled, but

Re: [PATCH 6/5] KVM: x86: fix periodic lapic timer with hrtimers

2016-10-26 21:32 GMT+08:00 Radim Krčmář : > 2016-10-26 14:02+0800, Wanpeng Li: >> 2016-10-25 19:43 GMT+08:00 Radim Krčmář : >>> 2016-10-25 07:39+0800, Wanpeng Li: 2016-10-24 23:27 GMT+08:00 Radim Krčmář : > 2016-10-24 17:09+0200, Paolo Bonzini: >> On 24/10/2016 17:03, Radim Krčmář

Re: [PATCH] USB: OHCI: make ohci-da8xx a separate driver

On 10/26/2016 04:08 PM, ahas...@baylibre.com wrote: From: Manjunath Goudar Separate the Davinci OHCI host controller driver from ohci-hcd host code so that it can be built as a separate driver module. This work is part of enabling multi-platform kernels on ARM

Re: [PATCH] USB: OHCI: make ohci-da8xx a separate driver

On 10/26/2016 04:08 PM, ahas...@baylibre.com wrote: From: Manjunath Goudar Separate the Davinci OHCI host controller driver from ohci-hcd host code so that it can be built as a separate driver module. This work is part of enabling multi-platform kernels on ARM Signed-off-by: Manjunath Goudar

Re: [PATCH v2 00/11] mpt3sas driver Enhancements and

> "Suganath" == Suganath Prabu S > writes: Suganath> Here is the change list: Posting 11 patches for mpt3sas driver Suganath> enhancements and few fixes. Suganath> * Added Device ID's for SAS35 devices and updated MPI Suganath> Header.

Re: [PATCH v2 00/11] mpt3sas driver Enhancements and

> "Suganath" == Suganath Prabu S > writes: Suganath> Here is the change list: Posting 11 patches for mpt3sas driver Suganath> enhancements and few fixes. Suganath> * Added Device ID's for SAS35 devices and updated MPI Suganath> Header. Suganath> * Support "EEDP Escape flag" for

Re: [PATCH v2 2/4] input: evdev: Replace timeval with timespec64

On Mon, Oct 17, 2016 at 08:27:31PM -0700, Deepa Dinamani wrote: > struct timeval is not y2038 safe. > > All references to timeval in the kernel will be replaced > by y2038 safe structures. > Replace all references to timeval with y2038 safe > struct timespec64 here. > > struct input_event will

Re: [PATCH v2 2/4] input: evdev: Replace timeval with timespec64

On Mon, Oct 17, 2016 at 08:27:31PM -0700, Deepa Dinamani wrote: > struct timeval is not y2038 safe. > > All references to timeval in the kernel will be replaced > by y2038 safe structures. > Replace all references to timeval with y2038 safe > struct timespec64 here. > > struct input_event will

Re: [lkp] [x86/platform/UV] 71854cb812: will-it-scale.per_thread_ops -2.3% regression

On 10/25, Thomas Gleixner wrote: >On Tue, 25 Oct 2016, kernel test robot wrote: >> FYI, we noticed a -2.3% regression of will-it-scale.per_thread_ops due to >> commit: >> >> commit 71854cb812ec23bfe5f63d52217e6b9e6cb901f5 ("x86/platform/UV: Fix >> support for EFI_OLD_MEMMAP after BIOS callback

Re: [lkp] [x86/platform/UV] 71854cb812: will-it-scale.per_thread_ops -2.3% regression

On 10/25, Thomas Gleixner wrote: >On Tue, 25 Oct 2016, kernel test robot wrote: >> FYI, we noticed a -2.3% regression of will-it-scale.per_thread_ops due to >> commit: >> >> commit 71854cb812ec23bfe5f63d52217e6b9e6cb901f5 ("x86/platform/UV: Fix >> support for EFI_OLD_MEMMAP after BIOS callback

cygnus-pcm.c:undefined reference to `bad_dma_ops'

Hi Mark, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 9fe68cad6e74967b88d0c6aeca7d9cd6b6e91942 commit: 3ceeda1cbee9f93bb5537c9b840d1f7e767d7c01 Merge remote-tracking branches 'asoc/topic/cs53l30',

cygnus-pcm.c:undefined reference to `bad_dma_ops'

Hi Mark, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 9fe68cad6e74967b88d0c6aeca7d9cd6b6e91942 commit: 3ceeda1cbee9f93bb5537c9b840d1f7e767d7c01 Merge remote-tracking branches 'asoc/topic/cs53l30',

Re: [PATCH v2 1/4] uinput: Add ioctl for using monotonic/ boot times

On Mon, Oct 17, 2016 at 08:27:30PM -0700, Deepa Dinamani wrote: > struct timeval which is part of struct input_event to > maintain the event times is not y2038 safe. > > Real time timestamps are also not ideal for input_event > as this time can go backwards as noted in the patch > a80b83b7b8 by

Re: [PATCH v2 1/4] uinput: Add ioctl for using monotonic/ boot times

On Mon, Oct 17, 2016 at 08:27:30PM -0700, Deepa Dinamani wrote: > struct timeval which is part of struct input_event to > maintain the event times is not y2038 safe. > > Real time timestamps are also not ideal for input_event > as this time can go backwards as noted in the patch > a80b83b7b8 by

Re: [PATCH] advansys: fix build warning for PCI=n

> "Arnd" == Arnd Bergmann writes: Arnd> The advansys probe function tries to handle both ISA and PCI Arnd> cases, each hidden in an #ifdef when unused. This leads to a Arnd> warning indicating that when PCI is disabled we could be using Arnd> uninitialized data: Arnd>

Re: [PATCH] advansys: fix build warning for PCI=n

> "Arnd" == Arnd Bergmann writes: Arnd> The advansys probe function tries to handle both ISA and PCI Arnd> cases, each hidden in an #ifdef when unused. This leads to a Arnd> warning indicating that when PCI is disabled we could be using Arnd> uninitialized data: Arnd>

[ANNOUNCE] 3.10.104-rt116

Dear RT Folks, I'm pleased to announce the 3.10.104-rt116 stable release. This release is just an update to the new stable 3.10.104 version and no RT specific changes have been made. You can get this release via the git tree at:

[ANNOUNCE] 3.2.83-rt120

Dear RT Folks, I'm pleased to announce the 3.2.83-rt120 stable release. This release is just an update to the new stable 3.2.83 version and no RT specific changes have been made. You can get this release via the git tree at:

[ANNOUNCE] 3.10.104-rt116

Dear RT Folks, I'm pleased to announce the 3.10.104-rt116 stable release. This release is just an update to the new stable 3.10.104 version and no RT specific changes have been made. You can get this release via the git tree at:

[ANNOUNCE] 3.2.83-rt120

Dear RT Folks, I'm pleased to announce the 3.2.83-rt120 stable release. This release is just an update to the new stable 3.2.83 version and no RT specific changes have been made. You can get this release via the git tree at:

  1   2   3   4   5   6   7   8   9   10   >