Re: [PATCH] x86/PCI: apply the AMD window fixup on resume as well

On Tue, Jan 16, 2018 at 10:43:17AM +0100, Christian König wrote: > We need to reprogram the register content during resume. > > Signed-off-by: Christian König > Reported-by: Tom St Denis Applied to for-linus for v4.15, thanks. > --- >

Re: [PATCH] x86/PCI: apply the AMD window fixup on resume as well

On Tue, Jan 16, 2018 at 10:43:17AM +0100, Christian König wrote: > We need to reprogram the register content during resume. > > Signed-off-by: Christian König > Reported-by: Tom St Denis Applied to for-linus for v4.15, thanks. > --- > arch/x86/pci/fixup.c | 32

Re: [PATCH] modpost: Remove trailing semicolon

On Tue, Jan 16, 2018 at 5:21 AM, Luis de Bethencourt wrote: > The trailing semicolon is an empty statement that does no operation. > Removing it since it doesn't do anything. > > Signed-off-by: Luis de Bethencourt Yup, good. Signed-off-by: Kees Cook

Re: [PATCH] modpost: Remove trailing semicolon

On Tue, Jan 16, 2018 at 5:21 AM, Luis de Bethencourt wrote: > The trailing semicolon is an empty statement that does no operation. > Removing it since it doesn't do anything. > > Signed-off-by: Luis de Bethencourt Yup, good. Signed-off-by: Kees Cook -Kees > --- > > Hi, > > After fixing the

[PATCH] ide: remove duplicated assignment to 'cursg'

From: Colin Ian King Pointer cursg is initialized to cmd->cursg and again re-assigned the same value a few lines later, hence the second assignment is redundant and can be removed. Cleans up clang warning: drivers/ide/ide-taskfile.c:229:22: warning: Value stored to

[PATCH] ide: remove duplicated assignment to 'cursg'

From: Colin Ian King Pointer cursg is initialized to cmd->cursg and again re-assigned the same value a few lines later, hence the second assignment is redundant and can be removed. Cleans up clang warning: drivers/ide/ide-taskfile.c:229:22: warning: Value stored to 'cursg' during its

[PATCH] proc: fix coredump vs read /proc/*/stat race

do_task_stat() accesses IP and SP of a task without bumping reference count of a stack (which became an entity with independent lifetime at some point). Steps to reproduce: #include #include #include #include #include #include #include #include int main(void) {

[PATCH] proc: fix coredump vs read /proc/*/stat race

do_task_stat() accesses IP and SP of a task without bumping reference count of a stack (which became an entity with independent lifetime at some point). Steps to reproduce: #include #include #include #include #include #include #include #include int main(void) {

Re: [PATCH] vxlan: Fix trailing semicolon

On Tue, 16 Jan 2018 15:03:32 + Luis de Bethencourt wrote: > The trailing semicolon is an empty statement that does no operation. > It is completely stripped out by the compiler. Removing it since it doesn't do > anything. > > Signed-off-by: Luis de Bethencourt

Re: [PATCH] vxlan: Fix trailing semicolon

On Tue, 16 Jan 2018 15:03:32 + Luis de Bethencourt wrote: > The trailing semicolon is an empty statement that does no operation. > It is completely stripped out by the compiler. Removing it since it doesn't do > anything. > > Signed-off-by: Luis de Bethencourt > --- > > Hi, > > An other

Re: [PATCH 4.14 053/118] Revert "Revert "xfrm: Fix stack-out-of-bounds read in xfrm_state_find.""

On Tue, Jan 16, 2018 at 10:32:38AM -0500, David Miller wrote: > From: Steffen Klassert > Date: Tue, 16 Jan 2018 07:33:39 +0100 > > > Maybe you started to look again into this because Nicolas Dichtel > > (Cced) asked to queue this patch on Jan 5, the patch was

Re: [PATCH 4.14 053/118] Revert "Revert "xfrm: Fix stack-out-of-bounds read in xfrm_state_find.""

On Tue, Jan 16, 2018 at 10:32:38AM -0500, David Miller wrote: > From: Steffen Klassert > Date: Tue, 16 Jan 2018 07:33:39 +0100 > > > Maybe you started to look again into this because Nicolas Dichtel > > (Cced) asked to queue this patch on Jan 5, the patch was already > > in the stable tree (Jan

[PATCH] i2c-stm32f4: remove redundant initialization of pointer reg

From: Colin Ian King The pointer reg is assigned a value that is never read, it is later overwritten with a new value, hence the redundant initialization can be removed. Cleans up clang warning: drivers/i2c/busses/i2c-stm32f4.c:352:16: warning: Value stored to 'reg'

[PATCH] i2c-stm32f4: remove redundant initialization of pointer reg

From: Colin Ian King The pointer reg is assigned a value that is never read, it is later overwritten with a new value, hence the redundant initialization can be removed. Cleans up clang warning: drivers/i2c/busses/i2c-stm32f4.c:352:16: warning: Value stored to 'reg' during its initialization is

[PATCH v2] staging: fsl-mc: Convert documentation to rst format

Update the doc file to comply with the rst format. It's not integrated into the documentation build structure yet, since it's still located in drivers/staging. Signed-off-by: Ioana Radulescu --- v2: patch generated with -M option .../staging/fsl-mc/{README.txt =>

[PATCH v2] staging: fsl-mc: Convert documentation to rst format

Update the doc file to comply with the rst format. It's not integrated into the documentation build structure yet, since it's still located in drivers/staging. Signed-off-by: Ioana Radulescu --- v2: patch generated with -M option .../staging/fsl-mc/{README.txt => overview.rst}| 655

Re: kmem_cache_attr (was Re: [PATCH 04/36] usercopy: Prepare for usercopy whitelisting)

On Tue, Jan 16, 2018 at 10:54:27AM -0600, Christopher Lameter wrote: > On Tue, 16 Jan 2018, Matthew Wilcox wrote: > > > I think that's a good thing! /proc/slabinfo really starts to get grotty > > above 16 bytes. I'd like to chop off "_cache" from the name of every > > single slab! If

Re: kmem_cache_attr (was Re: [PATCH 04/36] usercopy: Prepare for usercopy whitelisting)

On Tue, Jan 16, 2018 at 10:54:27AM -0600, Christopher Lameter wrote: > On Tue, 16 Jan 2018, Matthew Wilcox wrote: > > > I think that's a good thing! /proc/slabinfo really starts to get grotty > > above 16 bytes. I'd like to chop off "_cache" from the name of every > > single slab! If

Re: [PATCH] PCI: Add Marvell 9128 to DMA alias quirks

On Tue, Jan 16, 2018 at 10:05:26AM -0700, Alex Williamson wrote: > This is the original device generating bug 42679, from which many > other Marvell DMA alias quirks have been sourced, but we didn't have > positive confirmation of the fix on 9128 until now. > > Link:

Re: [PATCH] PCI: Add Marvell 9128 to DMA alias quirks

On Tue, Jan 16, 2018 at 10:05:26AM -0700, Alex Williamson wrote: > This is the original device generating bug 42679, from which many > other Marvell DMA alias quirks have been sourced, but we didn't have > positive confirmation of the fix on 9128 until now. > > Link:

Re: [PATCH v3 0/3] tracing: Fix the parser when processing strings w/ or w/o terminated '\0'

On Tue, 16 Jan 2018 17:02:27 +0800 changbin...@intel.com wrote: > From: Changbin Du > > I found there are some problems in the tracing parser when I investiage the > root > cause of issues mentioned in below patch. > https://patchwork.kernel.org/patch/10132953/ I pulled

Re: [PATCH v3 0/3] tracing: Fix the parser when processing strings w/ or w/o terminated '\0'

On Tue, 16 Jan 2018 17:02:27 +0800 changbin...@intel.com wrote: > From: Changbin Du > > I found there are some problems in the tracing parser when I investiage the > root > cause of issues mentioned in below patch. > https://patchwork.kernel.org/patch/10132953/ I pulled in your patches and

Re: [PATCH v3] firmware: qcom: scm: Fix incorrect of_node_put calls in scm_init

Hi Loys, Bjorn, On Tue, Jan 16, 2018 at 08:45:49AM -0800, Bjorn Andersson wrote: > On Fri 15 Dec 05:40 PST 2017, Loys Ollivier wrote: > > > When using other platform architectures, in the init of the qcom_scm > > driver, of_node_put is called on /firmware if no qcom dt is found. > > This results

Re: [PATCH v3] firmware: qcom: scm: Fix incorrect of_node_put calls in scm_init

Hi Loys, Bjorn, On Tue, Jan 16, 2018 at 08:45:49AM -0800, Bjorn Andersson wrote: > On Fri 15 Dec 05:40 PST 2017, Loys Ollivier wrote: > > > When using other platform architectures, in the init of the qcom_scm > > driver, of_node_put is called on /firmware if no qcom dt is found. > > This results

Re: [PATCH 08/11] signal/arm: Document conflicts with SI_USER and SIGFPE

On Mon, Jan 15, 2018 at 05:49:47PM +, Russell King - ARM Linux wrote: > On Thu, Jan 11, 2018 at 06:59:37PM -0600, Eric W. Biederman wrote: > > Setting si_code to 0 results in a userspace seeing an si_code of 0. > > This is the same si_code as SI_USER. Posix and common sense requires > > that

Re: [PATCH 08/11] signal/arm: Document conflicts with SI_USER and SIGFPE

On Mon, Jan 15, 2018 at 05:49:47PM +, Russell King - ARM Linux wrote: > On Thu, Jan 11, 2018 at 06:59:37PM -0600, Eric W. Biederman wrote: > > Setting si_code to 0 results in a userspace seeing an si_code of 0. > > This is the same si_code as SI_USER. Posix and common sense requires > > that

Re: [PATCH 1/3] KVM: VMX: introduce alloc_loaded_vmcs

On 16/01/2018 18:27, David Hildenbrand wrote: > On 16.01.2018 17:52, Paolo Bonzini wrote: >> Group together the calls to alloc_vmcs and loaded_vmcs_init. Soon we'll also >> allocate an MSR bitmap there. >> >> Signed-off-by: Paolo Bonzini >> --- >> arch/x86/kvm/vmx.c | 36

Re: [PATCH 1/3] KVM: VMX: introduce alloc_loaded_vmcs

On 16/01/2018 18:27, David Hildenbrand wrote: > On 16.01.2018 17:52, Paolo Bonzini wrote: >> Group together the calls to alloc_vmcs and loaded_vmcs_init. Soon we'll also >> allocate an MSR bitmap there. >> >> Signed-off-by: Paolo Bonzini >> --- >> arch/x86/kvm/vmx.c | 36

[PATCH] HID: logitech-hidpp: remove duplicated assignment to 'hidpp'

From: Colin Ian King Pointer hidpp is being assigned twice with the same value, remove the second occurrance as it is redundant. Cleans up clang warning: drivers/hid/hid-logitech-hidpp.c:177:23: warning: Value stored to 'hidpp' during its initialization is never read

[PATCH] HID: logitech-hidpp: remove duplicated assignment to 'hidpp'

From: Colin Ian King Pointer hidpp is being assigned twice with the same value, remove the second occurrance as it is redundant. Cleans up clang warning: drivers/hid/hid-logitech-hidpp.c:177:23: warning: Value stored to 'hidpp' during its initialization is never read Signed-off-by: Colin Ian

Re: [PATCH] workqueue: Handle race between wake up and rebind

Hello, Neeraj. On Mon, Jan 15, 2018 at 02:08:12PM +0530, Neeraj Upadhyay wrote: > - kworker/0:0 gets chance to run on cpu1; while processing > a work, it goes to sleep. However, it does not decrement > pool->nr_running. This is because WORKER_REBOUND (NOT_ > RUNNING) flag was cleared, when

Re: [PATCH] workqueue: Handle race between wake up and rebind

Hello, Neeraj. On Mon, Jan 15, 2018 at 02:08:12PM +0530, Neeraj Upadhyay wrote: > - kworker/0:0 gets chance to run on cpu1; while processing > a work, it goes to sleep. However, it does not decrement > pool->nr_running. This is because WORKER_REBOUND (NOT_ > RUNNING) flag was cleared, when

Re: [PATCH 06/16] x86/mm/ldt: Reserve high address-space range for the LDT

On 01/16/2018 12:31 PM, Peter Zijlstra wrote: > On Tue, Jan 16, 2018 at 06:13:43PM +0100, Joerg Roedel wrote: >> Hi Peter, >> >> On Tue, Jan 16, 2018 at 05:52:13PM +0100, Peter Zijlstra wrote: >>> On Tue, Jan 16, 2018 at 05:36:49PM +0100, Joerg Roedel wrote: From: Joerg Roedel

Re: [PATCH 06/16] x86/mm/ldt: Reserve high address-space range for the LDT

On 01/16/2018 12:31 PM, Peter Zijlstra wrote: > On Tue, Jan 16, 2018 at 06:13:43PM +0100, Joerg Roedel wrote: >> Hi Peter, >> >> On Tue, Jan 16, 2018 at 05:52:13PM +0100, Peter Zijlstra wrote: >>> On Tue, Jan 16, 2018 at 05:36:49PM +0100, Joerg Roedel wrote: From: Joerg Roedel

Re: what trees/branches to test on syzbot

On Tue, Jan 16, 2018 at 11:02:17AM -0600, Eric W. Biederman wrote: > Dmitry Vyukov writes: > > > On Tue, Jan 16, 2018 at 10:45 AM, Guenter Roeck wrote: > >> On Mon, Jan 15, 2018 at 11:51 PM, Dmitry Vyukov wrote: > >>> Hello, > >>> >

Re: what trees/branches to test on syzbot

On Tue, Jan 16, 2018 at 11:02:17AM -0600, Eric W. Biederman wrote: > Dmitry Vyukov writes: > > > On Tue, Jan 16, 2018 at 10:45 AM, Guenter Roeck wrote: > >> On Mon, Jan 15, 2018 at 11:51 PM, Dmitry Vyukov wrote: > >>> Hello, > >>> > >>> Several people proposed that linux-next should not be

Re: [PATCH] crypto: mxs-dcp: Add empty hash export and import

On 16.01.2018 17:56, Marek Vasut wrote: > On 01/16/2018 05:16 PM, Kamil Konieczny wrote: >> Crypto framework will require async hash export/import, so add empty >> functions to prevent OOPS. > > Shouldn't this be handled on the subsystem level with some > > if (foo->bar) > foo->bar(); > >

Re: [PATCH] crypto: mxs-dcp: Add empty hash export and import

On 16.01.2018 17:56, Marek Vasut wrote: > On 01/16/2018 05:16 PM, Kamil Konieczny wrote: >> Crypto framework will require async hash export/import, so add empty >> functions to prevent OOPS. > > Shouldn't this be handled on the subsystem level with some > > if (foo->bar) > foo->bar(); > >

Re: [mm 4.15-rc8] Random oopses under memory pressure.

Linus Torvalds wrote: > On Mon, Jan 15, 2018 at 5:15 PM, Tetsuo Handa > wrote: > > > > I can't reproduce this with CONFIG_FLATMEM=y . But I'm not sure whether > > we are hitting a bug in CONFIG_SPARSEMEM=y code, for the bug is highly > > timing dependent. > >

Re: [mm 4.15-rc8] Random oopses under memory pressure.

Linus Torvalds wrote: > On Mon, Jan 15, 2018 at 5:15 PM, Tetsuo Handa > wrote: > > > > I can't reproduce this with CONFIG_FLATMEM=y . But I'm not sure whether > > we are hitting a bug in CONFIG_SPARSEMEM=y code, for the bug is highly > > timing dependent. > > Hmm. Maybe. But sparsemem really

Re: [PATCH 06/16] x86/mm/ldt: Reserve high address-space range for the LDT

On Tue, Jan 16, 2018 at 06:13:43PM +0100, Joerg Roedel wrote: > Hi Peter, > > On Tue, Jan 16, 2018 at 05:52:13PM +0100, Peter Zijlstra wrote: > > On Tue, Jan 16, 2018 at 05:36:49PM +0100, Joerg Roedel wrote: > > > From: Joerg Roedel > > > > > > Reserve 2MB/4MB of address space

Re: [PATCH 06/16] x86/mm/ldt: Reserve high address-space range for the LDT

On Tue, Jan 16, 2018 at 06:13:43PM +0100, Joerg Roedel wrote: > Hi Peter, > > On Tue, Jan 16, 2018 at 05:52:13PM +0100, Peter Zijlstra wrote: > > On Tue, Jan 16, 2018 at 05:36:49PM +0100, Joerg Roedel wrote: > > > From: Joerg Roedel > > > > > > Reserve 2MB/4MB of address space for mapping the

Re: [PATCH v3 1/3] trace-cmd: Make read_proc() to return int status via OUT arg

On Tue, 16 Jan 2018 09:47:42 +0200 "Vladislav Valtchev (VMware)" wrote: > diff --git a/trace-stack.c b/trace-stack.c > index aa79ae3..c1058ca 100644 > --- a/trace-stack.c > +++ b/trace-stack.c > @@ -20,6 +20,7 @@ > #include > #include > #include > +#include >

Re: [PATCH v3 1/3] trace-cmd: Make read_proc() to return int status via OUT arg

On Tue, 16 Jan 2018 09:47:42 +0200 "Vladislav Valtchev (VMware)" wrote: > diff --git a/trace-stack.c b/trace-stack.c > index aa79ae3..c1058ca 100644 > --- a/trace-stack.c > +++ b/trace-stack.c > @@ -20,6 +20,7 @@ > #include > #include > #include > +#include > #include > #include >

Re: [PATCH] soc: xilinx: xlnx_vcu: Use bitwise & rather than logical && on clkoutdiv

Quoting Michal Simek : On 16.1.2018 15:22, Dhaval Rajeshbhai Shah wrote: Hi, -Original Message- From: Gustavo A. R. Silva [mailto:garsi...@embeddedor.com] Sent: Monday, January 15, 2018 11:15 AM To: Michal Simek ; Dhaval Rajeshbhai

Re: [PATCH] soc: xilinx: xlnx_vcu: Use bitwise & rather than logical && on clkoutdiv

Quoting Michal Simek : On 16.1.2018 15:22, Dhaval Rajeshbhai Shah wrote: Hi, -Original Message- From: Gustavo A. R. Silva [mailto:garsi...@embeddedor.com] Sent: Monday, January 15, 2018 11:15 AM To: Michal Simek ; Dhaval Rajeshbhai Shah Cc: linux-arm-ker...@lists.infradead.org;

Re: [PATCH] [RESEND] vmwgfx: use monotonic event timestamps

Hi, Arnd, Sinclair's on paternal leave and I thought this patch was already in drm-next. My bad. Dave, is it too late to pull this in for the next merge window? /Thomas On 01/16/2018 06:18 PM, Arnd Bergmann wrote: DRM_VMW_EVENT_FENCE_SIGNALED (struct drm_vmw_event_fence) and

Re: [PATCH] [RESEND] vmwgfx: use monotonic event timestamps

Hi, Arnd, Sinclair's on paternal leave and I thought this patch was already in drm-next. My bad. Dave, is it too late to pull this in for the next merge window? /Thomas On 01/16/2018 06:18 PM, Arnd Bergmann wrote: DRM_VMW_EVENT_FENCE_SIGNALED (struct drm_vmw_event_fence) and

Re: [PATCH 1/3] KVM: VMX: introduce alloc_loaded_vmcs

On 16.01.2018 17:52, Paolo Bonzini wrote: > Group together the calls to alloc_vmcs and loaded_vmcs_init. Soon we'll also > allocate an MSR bitmap there. > > Signed-off-by: Paolo Bonzini > --- > arch/x86/kvm/vmx.c | 36 ++-- > 1 file changed,

Re: [PATCH 1/3] KVM: VMX: introduce alloc_loaded_vmcs

On 16.01.2018 17:52, Paolo Bonzini wrote: > Group together the calls to alloc_vmcs and loaded_vmcs_init. Soon we'll also > allocate an MSR bitmap there. > > Signed-off-by: Paolo Bonzini > --- > arch/x86/kvm/vmx.c | 36 ++-- > 1 file changed, 22 insertions(+), 14

Re: [PATCH] crypto: mxs-dcp: Add empty hash export and import

Hi Kamil, On Tue, Jan 16, 2018 at 2:16 PM, Kamil Konieczny wrote: > Crypto framework will require async hash export/import, so add empty > functions to prevent OOPS. Which Oops exactly are you getting? Just booted 4.14.13 and the mxs-dcp driver does not even

Re: [PATCH] crypto: mxs-dcp: Add empty hash export and import

Hi Kamil, On Tue, Jan 16, 2018 at 2:16 PM, Kamil Konieczny wrote: > Crypto framework will require async hash export/import, so add empty > functions to prevent OOPS. Which Oops exactly are you getting? Just booted 4.14.13 and the mxs-dcp driver does not even probe successfully: [2.455404]

Re: [PATCH 2/4] dt-bindings: at24: add compatible for nxp,se97b

2018-01-16 17:06 GMT+01:00 Peter Rosin : > The datasheet talks about the chip being an spd, but the chip is writable > so atmel,24c02 is more appropriate as fallback. > > Signed-off-by: Peter Rosin > --- > Documentation/devicetree/bindings/eeprom/at24.txt | 1 +

Re: [PATCH 2/4] dt-bindings: at24: add compatible for nxp,se97b

2018-01-16 17:06 GMT+01:00 Peter Rosin : > The datasheet talks about the chip being an spd, but the chip is writable > so atmel,24c02 is more appropriate as fallback. > > Signed-off-by: Peter Rosin > --- > Documentation/devicetree/bindings/eeprom/at24.txt | 1 + > 1 file changed, 1 insertion(+)

Re: [PATCH 1/4] dt-bindings: at24: sort manufacturers alphabetically

2018-01-16 17:06 GMT+01:00 Peter Rosin : > Makes them easier to find. > > Signed-off-by: Peter Rosin > --- > Documentation/devicetree/bindings/eeprom/at24.txt | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git

Re: [PATCH 1/4] dt-bindings: at24: sort manufacturers alphabetically

2018-01-16 17:06 GMT+01:00 Peter Rosin : > Makes them easier to find. > > Signed-off-by: Peter Rosin > --- > Documentation/devicetree/bindings/eeprom/at24.txt | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Documentation/devicetree/bindings/eeprom/at24.txt >

RE: [PATCH v2] x86/microcode/intel: Extend BDW late-loading with LLC size check

> I'll look for someone who can confirm the 2.5MB/core detail. Ok ... re-read the erratum. The 2.5MB/core is clear. The E5+E7 is clear. No mention of the platform ID, but Jia is dropping that part. Boris ... what specific questions remain? -Tony

RE: [PATCH v2] x86/microcode/intel: Extend BDW late-loading with LLC size check

> I'll look for someone who can confirm the 2.5MB/core detail. Ok ... re-read the erratum. The 2.5MB/core is clear. The E5+E7 is clear. No mention of the platform ID, but Jia is dropping that part. Boris ... what specific questions remain? -Tony

Re: [PATCH 07/11] signal/arm64: Document conflicts with SI_USER and SIGFPE, SIGTRAP, SIGBUS

On Mon, Jan 15, 2018 at 11:23:03AM -0600, Eric W. Biederman wrote: > Dave Martin writes: > > > On Thu, Jan 11, 2018 at 06:59:36PM -0600, Eric W. Biederman wrote: > >> Setting si_code to 0 results in a userspace seeing an si_code of 0. > >> This is the same si_code as

Re: [PATCH 07/11] signal/arm64: Document conflicts with SI_USER and SIGFPE, SIGTRAP, SIGBUS

On Mon, Jan 15, 2018 at 11:23:03AM -0600, Eric W. Biederman wrote: > Dave Martin writes: > > > On Thu, Jan 11, 2018 at 06:59:36PM -0600, Eric W. Biederman wrote: > >> Setting si_code to 0 results in a userspace seeing an si_code of 0. > >> This is the same si_code as SI_USER. Posix and common

Re: [RFT PATCH v3 4/6] uvcvideo: queue: Simplify spin-lock usage

Hi Kieran, Thank you for the patch. On Friday, 12 January 2018 11:19:26 EET Kieran Bingham wrote: > Both uvc_start_streaming(), and uvc_stop_streaming() are called from > userspace context. As such, they do not need to save the IRQ state, and > can use spin_lock_irq() and spin_unlock_irq()

Re: [RFT PATCH v3 4/6] uvcvideo: queue: Simplify spin-lock usage

Hi Kieran, Thank you for the patch. On Friday, 12 January 2018 11:19:26 EET Kieran Bingham wrote: > Both uvc_start_streaming(), and uvc_stop_streaming() are called from > userspace context. As such, they do not need to save the IRQ state, and > can use spin_lock_irq() and spin_unlock_irq()

Re: [PATCH v5 12/44] clk: davinci: Add platform information for TI DA850 PSC

On 01/16/2018 08:00 AM, Sekhar Nori wrote: On Monday 08 January 2018 07:47 AM, David Lechner wrote: +void __init da850_psc_clk_init(void __iomem *psc0, void __iomem *psc1) +{ + struct clk_onecell_data *clk_data; + + clk_data = davinci_psc_register_clocks(psc0, da850_psc0_info, 16);

Re: [PATCH v5 12/44] clk: davinci: Add platform information for TI DA850 PSC

On 01/16/2018 08:00 AM, Sekhar Nori wrote: On Monday 08 January 2018 07:47 AM, David Lechner wrote: +void __init da850_psc_clk_init(void __iomem *psc0, void __iomem *psc1) +{ + struct clk_onecell_data *clk_data; + + clk_data = davinci_psc_register_clocks(psc0, da850_psc0_info, 16);

Re: [PATCH v5 3/9] v4l: platform: Add Renesas CEU driver

Hi Hans, On Tue, Jan 16, 2018 at 10:46:42AM +0100, Hans Verkuil wrote: > Hi Jacopo, > > Sorry for the late review, but here is finally is. > > BTW, can you provide the v4l2-compliance output (ideally with the -f option) > in the cover letter for v6? Sure, it was attacched to v3 I guess, since

Re: [PATCH v5 3/9] v4l: platform: Add Renesas CEU driver

Hi Hans, On Tue, Jan 16, 2018 at 10:46:42AM +0100, Hans Verkuil wrote: > Hi Jacopo, > > Sorry for the late review, but here is finally is. > > BTW, can you provide the v4l2-compliance output (ideally with the -f option) > in the cover letter for v6? Sure, it was attacched to v3 I guess, since

Re: [PATCH v3 1/3] trace-cmd: Make read_proc() to return int status via OUT arg

On Tue, 16 Jan 2018 09:47:42 +0200 "Vladislav Valtchev (VMware)" wrote: > + errno = 0; > + > + /* Read an integer from buf ignoring any non-digit trailing characters. > */ > + num = strtol(buf, NULL, 10); > + > + /* strtol() returned 0: we have to

[PATCH] [RESEND] vmwgfx: use monotonic event timestamps

DRM_VMW_EVENT_FENCE_SIGNALED (struct drm_vmw_event_fence) and DRM_EVENT_VBLANK (struct drm_event_vblank) pass timestamps in 32-bit seconds/microseconds format. As of commit c61eef726a78 ("drm: add support for monotonic vblank timestamps"), other DRM drivers use monotonic times for

Re: [PATCH v3 1/3] trace-cmd: Make read_proc() to return int status via OUT arg

On Tue, 16 Jan 2018 09:47:42 +0200 "Vladislav Valtchev (VMware)" wrote: > + errno = 0; > + > + /* Read an integer from buf ignoring any non-digit trailing characters. > */ > + num = strtol(buf, NULL, 10); > + > + /* strtol() returned 0: we have to check for errors */ > + if

[PATCH] [RESEND] vmwgfx: use monotonic event timestamps

DRM_VMW_EVENT_FENCE_SIGNALED (struct drm_vmw_event_fence) and DRM_EVENT_VBLANK (struct drm_event_vblank) pass timestamps in 32-bit seconds/microseconds format. As of commit c61eef726a78 ("drm: add support for monotonic vblank timestamps"), other DRM drivers use monotonic times for

Re: [PATCH v2] net/core: Increase default optmem_max limit

With the new Linux Kernel Crypto API User Space Interface and its underlying AF_ALG socket, the current default value for `net.core.optmem_max` can be exhausted pretty quick when using asynchronous IO; on 32 bit systems it is not even enough for sending about 10 IOVECs at once to the socket

Re: [PATCH v2] net/core: Increase default optmem_max limit

With the new Linux Kernel Crypto API User Space Interface and its underlying AF_ALG socket, the current default value for `net.core.optmem_max` can be exhausted pretty quick when using asynchronous IO; on 32 bit systems it is not even enough for sending about 10 IOVECs at once to the socket

Re: [RFC 0/6] Enlightened VMCS support for KVM on Hyper-V

2018-01-15 18:30+0100, Vitaly Kuznetsov: > Early RFC. I'll refer to this patchset in my DevConf/FOSDEM > presentations. > > When running nested KVM on Hyper-V it's possible to use so called > 'Enlightened VMCS' and do normal memory reads/writes instead of > doing VMWRITE/VMREAD instructions.

Re: [RFC 0/6] Enlightened VMCS support for KVM on Hyper-V

2018-01-15 18:30+0100, Vitaly Kuznetsov: > Early RFC. I'll refer to this patchset in my DevConf/FOSDEM > presentations. > > When running nested KVM on Hyper-V it's possible to use so called > 'Enlightened VMCS' and do normal memory reads/writes instead of > doing VMWRITE/VMREAD instructions.

Re: [PATCH v5 11/44] clk: davinci: Add platform information for TI DA830 PSC

On 01/16/2018 07:38 AM, Sekhar Nori wrote: On Monday 08 January 2018 07:47 AM, David Lechner wrote: This adds platform-specific declarations for the PSC clocks on TI DA830/ OMAP-L137/AM17XX SoCs. Signed-off-by: David Lechner --- drivers/clk/davinci/Makefile| 1 +

Re: [PATCH v5 11/44] clk: davinci: Add platform information for TI DA830 PSC

On 01/16/2018 07:38 AM, Sekhar Nori wrote: On Monday 08 January 2018 07:47 AM, David Lechner wrote: This adds platform-specific declarations for the PSC clocks on TI DA830/ OMAP-L137/AM17XX SoCs. Signed-off-by: David Lechner --- drivers/clk/davinci/Makefile| 1 +

[PATCH] nfs/super: check NFS_CAP_ACLS instead of the NFS version

This sets MS_POSIXACL only if ACL support is really enabled, instead of always setting MS_POSIXACL if the NFS protocol version theoretically supports ACL. The code comment says "We will [apply the umask] ourselves", but that happens in posix_acl_create() only if the kernel has POSIX ACL support.

[PATCH] nfs/super: check NFS_CAP_ACLS instead of the NFS version

This sets MS_POSIXACL only if ACL support is really enabled, instead of always setting MS_POSIXACL if the NFS protocol version theoretically supports ACL. The code comment says "We will [apply the umask] ourselves", but that happens in posix_acl_create() only if the kernel has POSIX ACL support.

[PATCH] pps: parport: use timespec64 instead of timespec

getnstimeofday() is deprecated, so I'm converting this to use ktime_get_real_ts64() as a safe replacement. I considered using ktime_get_real() instead, but since the algorithm here depends on the exact timing, I decided to introduce fewer changes and leave the code that determines the nanoseconds

[PATCH] pps: parport: use timespec64 instead of timespec

getnstimeofday() is deprecated, so I'm converting this to use ktime_get_real_ts64() as a safe replacement. I considered using ktime_get_real() instead, but since the algorithm here depends on the exact timing, I decided to introduce fewer changes and leave the code that determines the nanoseconds

[PATCH v2] net/core: Increase default optmem_max limit

[PATCH v2] net/core: Increase default optmem_max limit

Re: [PATCH 06/16] x86/mm/ldt: Reserve high address-space range for the LDT

Hi Peter, On Tue, Jan 16, 2018 at 05:52:13PM +0100, Peter Zijlstra wrote: > On Tue, Jan 16, 2018 at 05:36:49PM +0100, Joerg Roedel wrote: > > From: Joerg Roedel > > > > Reserve 2MB/4MB of address space for mapping the LDT to > > user-space. > > LDT is 64k, we need 2 per CPU,

Re: [PATCH 06/16] x86/mm/ldt: Reserve high address-space range for the LDT

Hi Peter, On Tue, Jan 16, 2018 at 05:52:13PM +0100, Peter Zijlstra wrote: > On Tue, Jan 16, 2018 at 05:36:49PM +0100, Joerg Roedel wrote: > > From: Joerg Roedel > > > > Reserve 2MB/4MB of address space for mapping the LDT to > > user-space. > > LDT is 64k, we need 2 per CPU, and NR_CPUS <= 64

Re: [PATCH v16 07/10] drm/panel: Use backlight_enable/disable helpers

Den 16.01.2018 11.35, skrev Meghana Madhyastha: Use backlight_enable/disable helpers instead of changing the property and calling backlight_update_status for cleaner and simpler code and also to avoid repetitions. Signed-off-by: Meghana Madhyastha ---

Re: [PATCH v16 07/10] drm/panel: Use backlight_enable/disable helpers

Den 16.01.2018 11.35, skrev Meghana Madhyastha: Use backlight_enable/disable helpers instead of changing the property and calling backlight_update_status for cleaner and simpler code and also to avoid repetitions. Signed-off-by: Meghana Madhyastha ---

Re: [PATCH] ARM: make memzero optimization smarter

On Tue, 16 Jan 2018, Arnd Bergmann wrote: > While testing with a gcc-8.0.0 snapshot, I ran into a harmless > build warning: > > In file included from include/linux/string.h:18:0, >... > from drivers/net/ethernet/hisilicon/hns/hns_ethtool.c:10: >

Re: [PATCH] ARM: make memzero optimization smarter

On Tue, 16 Jan 2018, Arnd Bergmann wrote: > While testing with a gcc-8.0.0 snapshot, I ran into a harmless > build warning: > > In file included from include/linux/string.h:18:0, >... > from drivers/net/ethernet/hisilicon/hns/hns_ethtool.c:10: >

Re: [PATCH 5/8] [media] omap3isp: support 64-bit version of omap3isp_stat_data

On Tue, Dec 5, 2017 at 1:41 AM, Laurent Pinchart wrote: > Hi Arnd, > > Thank you for the patch. > > I'll try to review this without too much delay. In the meantime, I'm CC'ing > Sakari Ailus who might be faster than me :-) Hi Laurent and Sakari, I stumbled

Re: [PATCH 5/8] [media] omap3isp: support 64-bit version of omap3isp_stat_data

On Tue, Dec 5, 2017 at 1:41 AM, Laurent Pinchart wrote: > Hi Arnd, > > Thank you for the patch. > > I'll try to review this without too much delay. In the meantime, I'm CC'ing > Sakari Ailus who might be faster than me :-) Hi Laurent and Sakari, I stumbled over this while cleaning out my

Re: [PATCH v16 09/10] drm/panel: Use of_find_backlight helper

Den 16.01.2018 11.36, skrev Meghana Madhyastha: Replace of_find_backlight_by_node and of the code around it with of_find_backlight helper to avoid repetition of code. Signed-off-by: Meghana Madhyastha --- drivers/gpu/drm/panel/panel-innolux-p079zca.c | 10

Re: [PATCH v16 09/10] drm/panel: Use of_find_backlight helper

Den 16.01.2018 11.36, skrev Meghana Madhyastha: Replace of_find_backlight_by_node and of the code around it with of_find_backlight helper to avoid repetition of code. Signed-off-by: Meghana Madhyastha --- drivers/gpu/drm/panel/panel-innolux-p079zca.c | 10 +++---

Re: [PATCH] bnxt_en: don't update cpr->rx_bytes with uninitialized length len

On Tue, Jan 16, 2018 at 2:22 AM, Colin King wrote: > From: Colin Ian King > > Currently in the cases where cmp_type == CMP_TYPE_RX_L2_TPA_START_CMP or > CMP_TYPE_RX_L2_TPA_END_CMP the exit path updates cpr->rx_bytes with an > uninitialized

Re: [PATCH] bnxt_en: don't update cpr->rx_bytes with uninitialized length len

On Tue, Jan 16, 2018 at 2:22 AM, Colin King wrote: > From: Colin Ian King > > Currently in the cases where cmp_type == CMP_TYPE_RX_L2_TPA_START_CMP or > CMP_TYPE_RX_L2_TPA_END_CMP the exit path updates cpr->rx_bytes with an > uninitialized length len. Fix this by adding a new exit path that

[PATCH] PCI: Add Marvell 9128 to DMA alias quirks

This is the original device generating bug 42679, from which many other Marvell DMA alias quirks have been sourced, but we didn't have positive confirmation of the fix on 9128 until now. Link: https://bugzilla.kernel.org/show_bug.cgi?id=42679 Link: https://www.spinics.net/lists/kvm/msg161459.html

[PATCH] PCI: Add Marvell 9128 to DMA alias quirks

This is the original device generating bug 42679, from which many other Marvell DMA alias quirks have been sourced, but we didn't have positive confirmation of the fix on 9128 until now. Link: https://bugzilla.kernel.org/show_bug.cgi?id=42679 Link: https://www.spinics.net/lists/kvm/msg161459.html

Re: what trees/branches to test on syzbot

Dmitry Vyukov writes: > On Tue, Jan 16, 2018 at 10:45 AM, Guenter Roeck wrote: >> On Mon, Jan 15, 2018 at 11:51 PM, Dmitry Vyukov wrote: >>> Hello, >>> >>> Several people proposed that linux-next should not be tested on >>> syzbot.

Re: what trees/branches to test on syzbot

Dmitry Vyukov writes: > On Tue, Jan 16, 2018 at 10:45 AM, Guenter Roeck wrote: >> On Mon, Jan 15, 2018 at 11:51 PM, Dmitry Vyukov wrote: >>> Hello, >>> >>> Several people proposed that linux-next should not be tested on >>> syzbot. While some people suggested that it needs to test as many >>>

Re: [PATCH v16 06/10] drm/tinydrm: Call devres version of of_find_backlight

Den 16.01.2018 11.34, skrev Meghana Madhyastha: Call devm_of_find_backlight (the devres version) instead of of_find_backlight. Signed-off-by: Meghana Madhyastha --- drivers/gpu/drm/tinydrm/mi0283qt.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

Re: [PATCH v16 06/10] drm/tinydrm: Call devres version of of_find_backlight

Den 16.01.2018 11.34, skrev Meghana Madhyastha: Call devm_of_find_backlight (the devres version) instead of of_find_backlight. Signed-off-by: Meghana Madhyastha --- drivers/gpu/drm/tinydrm/mi0283qt.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

<    5   6   7   8   9   10   11   12   13   14   >