[PATCH] scsi: be2iscsi: Convert timers to use timer_setup()

In preparation for unconditionally passing the struct timer_list pointer to all timer callbacks, switch to using the new timer_setup() and from_timer() to pass the timer pointer explicitly. Signed-off-by: Kees Cook Reviewed-by: Martin K. Petersen

[PATCH] scsi: be2iscsi: Convert timers to use timer_setup()

In preparation for unconditionally passing the struct timer_list pointer to all timer callbacks, switch to using the new timer_setup() and from_timer() to pass the timer pointer explicitly. Signed-off-by: Kees Cook Reviewed-by: Martin K. Petersen --- This is a resend to tglx, with Reviews/Acks.

[PATCH] scsi/bnx2i: Convert timers to use timer_setup()

In preparation for unconditionally passing the struct timer_list pointer to all timer callbacks, switch to using the new timer_setup() and from_timer() to pass the timer pointer explicitly. There was a seemingly missing call to initialize the timer in one handler, so this was added to remove the

[PATCH] scsi/bnx2i: Convert timers to use timer_setup()

In preparation for unconditionally passing the struct timer_list pointer to all timer callbacks, switch to using the new timer_setup() and from_timer() to pass the timer pointer explicitly. There was a seemingly missing call to initialize the timer in one handler, so this was added to remove the

[PATCH] scsi: libfc: Convert timers to use timer_setup()

In preparation for unconditionally passing the struct timer_list pointer to all timer callbacks, switch to using the new timer_setup() and from_timer() to pass the timer pointer explicitly. This removes several redundant setup calls in favor of just changing the timer function directly.

[PATCH] scsi: libfc: Convert timers to use timer_setup()

In preparation for unconditionally passing the struct timer_list pointer to all timer callbacks, switch to using the new timer_setup() and from_timer() to pass the timer pointer explicitly. This removes several redundant setup calls in favor of just changing the timer function directly.

[PATCH] scsi: fcoe: Convert timers to use timer_setup()

In preparation for unconditionally passing the struct timer_list pointer to all timer callbacks, switch to using the new timer_setup() and from_timer() to pass the timer pointer explicitly. Signed-off-by: Kees Cook Acked-by: Johannes Thumshirn --- This is

[PATCH] scsi: fcoe: Convert timers to use timer_setup()

In preparation for unconditionally passing the struct timer_list pointer to all timer callbacks, switch to using the new timer_setup() and from_timer() to pass the timer pointer explicitly. Signed-off-by: Kees Cook Acked-by: Johannes Thumshirn --- This is a resend to tglx, with Reviews/Acks.

Re: [PATCH v9 13/29] x86/insn-eval: Add utility functions to get segment selector

On Tue, Oct 17, 2017 at 01:31:52PM -0700, Ricardo Neri wrote: > I apologize for the inconvenience, I have verified that may mail client > works properly this time. I double-checked that it did not wrap. But did you try applying the patch which you have sent to yourself first? Because it doesn't

Re: [PATCH v9 13/29] x86/insn-eval: Add utility functions to get segment selector

On Tue, Oct 17, 2017 at 01:31:52PM -0700, Ricardo Neri wrote: > I apologize for the inconvenience, I have verified that may mail client > works properly this time. I double-checked that it did not wrap. But did you try applying the patch which you have sent to yourself first? Because it doesn't

[PATCH] scsi: isci: Convert timers to use timer_setup()

In preparation for unconditionally passing the struct timer_list pointer to all timer callbacks, switch to using the new timer_setup() and from_timer() to pass the timer pointer explicitly. Signed-off-by: Kees Cook Reviewed-by: Artur Paszkiewicz

[PATCH] scsi: isci: Convert timers to use timer_setup()

In preparation for unconditionally passing the struct timer_list pointer to all timer callbacks, switch to using the new timer_setup() and from_timer() to pass the timer pointer explicitly. Signed-off-by: Kees Cook Reviewed-by: Artur Paszkiewicz --- This is a resend to tglx, with Reviews/Acks.

Re: Linux-kernel examples for LKMM recipes

On Wed, Oct 18, 2017 at 10:43:42AM -0400, Alan Stern wrote: > On Tue, 17 Oct 2017, Paul E. McKenney wrote: > > > > > > > b. Compilers are permitted to use the "as-if" rule. > > > > > > That is, a compiler can emit whatever code it likes, > > > > > > as long as the

Re: Linux-kernel examples for LKMM recipes

On Wed, Oct 18, 2017 at 10:43:42AM -0400, Alan Stern wrote: > On Tue, 17 Oct 2017, Paul E. McKenney wrote: > > > > > > > b. Compilers are permitted to use the "as-if" rule. > > > > > > That is, a compiler can emit whatever code it likes, > > > > > > as long as the

[PATCH] staging/irda/net: Convert timers to use timer_setup()

In preparation for unconditionally passing the struct timer_list pointer to all timer callbacks, switch to using the new timer_setup() and from_timer() to pass the timer pointer explicitly. Cc: Samuel Ortiz Cc: Stephen Hemminger Cc: Johannes Berg

[PATCH] staging/irda/net: Convert timers to use timer_setup()

In preparation for unconditionally passing the struct timer_list pointer to all timer callbacks, switch to using the new timer_setup() and from_timer() to pass the timer pointer explicitly. Cc: Samuel Ortiz Cc: Stephen Hemminger Cc: Johannes Berg Cc: Ingo Molnar Signed-off-by: Kees Cook ---

[PATCH] staging/irda/bfin_sir: Convert timers to use timer_setup()

In preparation for unconditionally passing the struct timer_list pointer to all timer callbacks, switch to using the new timer_setup() and from_timer() to pass the timer pointer explicitly. Cc: Samuel Ortiz Signed-off-by: Kees Cook ---

[PATCH] staging/irda/bfin_sir: Convert timers to use timer_setup()

In preparation for unconditionally passing the struct timer_list pointer to all timer callbacks, switch to using the new timer_setup() and from_timer() to pass the timer pointer explicitly. Cc: Samuel Ortiz Signed-off-by: Kees Cook --- drivers/staging/irda/drivers/bfin_sir.c | 12 +++-

[PATCH] staging/irda-usb: Convert timers to use timer_setup()

In preparation for unconditionally passing the struct timer_list pointer to all timer callbacks, switch to using the new timer_setup() and from_timer() to pass the timer pointer explicitly. This requires adding a pointer to hold the timer's target URB, as there won't be a way to pass this in the

[PATCH] staging/irda-usb: Convert timers to use timer_setup()

In preparation for unconditionally passing the struct timer_list pointer to all timer callbacks, switch to using the new timer_setup() and from_timer() to pass the timer pointer explicitly. This requires adding a pointer to hold the timer's target URB, as there won't be a way to pass this in the

[PATCH 1/2 v3] typec: tcpm: Validate source and sink caps

The source and sink caps should follow the following rules. This patch validates whether the src_caps/snk_caps adheres to it. 6.4.1 Capabilities Message A Capabilities message (Source Capabilities message or Sink Capabilities message) shall have at least one Power Data Object for vSafe5V. The

[PATCH] staging: wlan-ng: Convert timers to use timer_setup()

In preparation for unconditionally passing the struct timer_list pointer to all timer callbacks, switch to using the new timer_setup() and from_timer() to pass the timer pointer explicitly. Cc: Greg Kroah-Hartman Cc: Sergio Paracuellos

[PATCH 2/2] typec: tcpm: Only request matching pdos

At present, TCPM code assumes that local device supports variable/batt pdos and always selects the pdo with highest possible power within the board limit. This assumption might not hold good for all devices. To overcome this, this patch makes TCPM only accept a source_pdo when there is a matching

[PATCH] staging: wlan-ng: Convert timers to use timer_setup()

In preparation for unconditionally passing the struct timer_list pointer to all timer callbacks, switch to using the new timer_setup() and from_timer() to pass the timer pointer explicitly. Cc: Greg Kroah-Hartman Cc: Sergio Paracuellos Cc: Adrien Descamps Cc: Thibaut SAUTEREAU Cc:

[PATCH 2/2] typec: tcpm: Only request matching pdos

At present, TCPM code assumes that local device supports variable/batt pdos and always selects the pdo with highest possible power within the board limit. This assumption might not hold good for all devices. To overcome this, this patch makes TCPM only accept a source_pdo when there is a matching

[PATCH 1/2 v3] typec: tcpm: Validate source and sink caps

The source and sink caps should follow the following rules. This patch validates whether the src_caps/snk_caps adheres to it. 6.4.1 Capabilities Message A Capabilities message (Source Capabilities message or Sink Capabilities message) shall have at least one Power Data Object for vSafe5V. The

Re: [PATCH v7] PCI: Workaround wrong flags completions for IDT switch

On 10/11/2017 03:27 PM, Bjorn Helgaas wrote: On Tue, Sep 26, 2017 at 04:03:13PM -0400, Sinan Kaya wrote: On 9/26/2017 3:52 PM, James Puthukattukaran wrote: I think you want to do the part above as part of a quirk that runs before the probe. I don't think there's a way to run this early

Re: [PATCH v7] PCI: Workaround wrong flags completions for IDT switch

On 10/11/2017 03:27 PM, Bjorn Helgaas wrote: On Tue, Sep 26, 2017 at 04:03:13PM -0400, Sinan Kaya wrote: On 9/26/2017 3:52 PM, James Puthukattukaran wrote: I think you want to do the part above as part of a quirk that runs before the probe. I don't think there's a way to run this early

Re: dtc issue with overlays starting in next-20171009

Use devicetree-compiler list for dtc issues please. On Wed, Oct 18, 2017 at 2:33 PM, Frank Rowand wrote: > Hi Rob, Alan, > > On 10/18/17 08:58, Alan Tull wrote: >> Hi Rob, >> >> I've noticed a problem compiling DT overlays and traced it back to >> beginning in

Re: dtc issue with overlays starting in next-20171009

Use devicetree-compiler list for dtc issues please. On Wed, Oct 18, 2017 at 2:33 PM, Frank Rowand wrote: > Hi Rob, Alan, > > On 10/18/17 08:58, Alan Tull wrote: >> Hi Rob, >> >> I've noticed a problem compiling DT overlays and traced it back to >> beginning in next-20171009 >> >> That tag adds

25710 linux-kernel

<>

25710 linux-kernel

<>

[PATCH V2 3/3] pseries/initnodes: Ensure nodes initialized for hotplug

pseries/nodes: On pseries systems which allow 'hot-add' of CPU, it may occur that the new resources are to be inserted into nodes that were not used for memory resources at bootup. Many different configurations of PowerPC resources may need to be supported depending upon the environment. This

[PATCH V2 3/3] pseries/initnodes: Ensure nodes initialized for hotplug

pseries/nodes: On pseries systems which allow 'hot-add' of CPU, it may occur that the new resources are to be inserted into nodes that were not used for memory resources at bootup. Many different configurations of PowerPC resources may need to be supported depending upon the environment. This

[PATCH V2 1/3] pseries/nodes: Ensure enough nodes avail for operations

pseries/nodes: On pseries systems which allow 'hot-add' of CPU or memory resources, it may occur that the new resources are to be inserted into nodes that were not used for these resources at bootup. In the kernel, any node that is used must be defined and initialized. This patch ensures that

[PATCH V2 1/3] pseries/nodes: Ensure enough nodes avail for operations

pseries/nodes: On pseries systems which allow 'hot-add' of CPU or memory resources, it may occur that the new resources are to be inserted into nodes that were not used for these resources at bootup. In the kernel, any node that is used must be defined and initialized. This patch ensures that

[PATCH V2 2/3] pseries/findnodes: Find nodes with memory for memoryless nodes

pseries/findnodes: On pseries systems which allow 'hot-add' of resources, we may boot configurations that have CPUs, but no memory associated to a node by the affinity calculations. Previously, the software took a shortcut to collapse initialization and references to such memoryless nodes with

[PATCH V2 2/3] pseries/findnodes: Find nodes with memory for memoryless nodes

pseries/findnodes: On pseries systems which allow 'hot-add' of resources, we may boot configurations that have CPUs, but no memory associated to a node by the affinity calculations. Previously, the software took a shortcut to collapse initialization and references to such memoryless nodes with

[PATCH V2 0/3] pseries/nodes: Fix issues with memoryless nodes

pseries/nodes: Ensure enough nodes avail for operations pseries/findnodes: Find nodes with memory when booting memoryless nodes pseries/initnodes: Ensure nodes initialized for hotplug Signed-off-by: Michael Bringmann Michael Bringmann (3): pseries/nodes: Ensure

[PATCH V2 0/3] pseries/nodes: Fix issues with memoryless nodes

pseries/nodes: Ensure enough nodes avail for operations pseries/findnodes: Find nodes with memory when booting memoryless nodes pseries/initnodes: Ensure nodes initialized for hotplug Signed-off-by: Michael Bringmann Michael Bringmann (3): pseries/nodes: Ensure enough nodes avail for

Re: [PATCH v5 2/2] staging: ion: create one device entry per heap

On 09/27/2017 06:20 AM, Benjamin Gaignard wrote: > diff --git a/drivers/staging/android/ion/ion.c > b/drivers/staging/android/ion/ion.c > index 93e2c90..092b24c 100644 > --- a/drivers/staging/android/ion/ion.c > +++ b/drivers/staging/android/ion/ion.c > @@ -40,6 +40,8 @@ > > #include "ion.h" >

Re: [PATCH v5 2/2] staging: ion: create one device entry per heap

On 09/27/2017 06:20 AM, Benjamin Gaignard wrote: > diff --git a/drivers/staging/android/ion/ion.c > b/drivers/staging/android/ion/ion.c > index 93e2c90..092b24c 100644 > --- a/drivers/staging/android/ion/ion.c > +++ b/drivers/staging/android/ion/ion.c > @@ -40,6 +40,8 @@ > > #include "ion.h" >

Re: [PATCH V1 1/1] serial: 8250_fintek: Fix finding base_port with activated SuperIO

On Tue, 17 Oct 2017 14:23:08 +0800 "Ji-Ze Hong (Peter Hong)" wrote: > The SuperIO will be configured at boot time by BIOS, but some BIOS > will not deactivate the SuperIO when the end of configuration. It'll > lead to mismatch for pdata->base_port in probe_setup_port(). So

Re: [PATCH V1 1/1] serial: 8250_fintek: Fix finding base_port with activated SuperIO

On Tue, 17 Oct 2017 14:23:08 +0800 "Ji-Ze Hong (Peter Hong)" wrote: > The SuperIO will be configured at boot time by BIOS, but some BIOS > will not deactivate the SuperIO when the end of configuration. It'll > lead to mismatch for pdata->base_port in probe_setup_port(). So we'll > deactivate all

Re: [PATCH v2] dell-laptop: Fix keyboard led max_brightness property for Dell Latitude E6410

On Wed, Oct 18, 2017 at 08:06:01PM +0200, Pali Rohár wrote: > This machine reports number of keyboard backlight led levels, instead of > value of the last led level index. Therefore max_brightness properly needs > to be subtracted by 1 to match led max_brightness API. > > Signed-off-by: Pali

Re: [PATCH v2] dell-laptop: Fix keyboard led max_brightness property for Dell Latitude E6410

On Wed, Oct 18, 2017 at 08:06:01PM +0200, Pali Rohár wrote: > This machine reports number of keyboard backlight led levels, instead of > value of the last led level index. Therefore max_brightness properly needs > to be subtracted by 1 to match led max_brightness API. > > Signed-off-by: Pali

[GIT PULL urgent-membarrier] membarrier commits for 4.14

Hello, Linus, This urgent pull request contains five commits that fix a problem that arose when designing requested extensions to sys_membarrier() to allow JITs to efficiently flush old code from instruction caches. Several potential algorithms are much less painful if the user register intent to

[GIT PULL urgent-membarrier] membarrier commits for 4.14

Hello, Linus, This urgent pull request contains five commits that fix a problem that arose when designing requested extensions to sys_membarrier() to allow JITs to efficiently flush old code from instruction caches. Several potential algorithms are much less painful if the user register intent to

Re: RFC(v2): Audit Kernel Container IDs

On Tue, Oct 17, 2017 at 8:31 AM, Simo Sorce wrote: > The container Id can be used also for authorization purposes (by other > processes on the host), not just audit, I think this is why a separate > control has been proposed. Apologies, but I'm just now getting a chance to work

Re: RFC(v2): Audit Kernel Container IDs

On Tue, Oct 17, 2017 at 8:31 AM, Simo Sorce wrote: > The container Id can be used also for authorization purposes (by other > processes on the host), not just audit, I think this is why a separate > control has been proposed. Apologies, but I'm just now getting a chance to work my way through

Re: [PATCH V8 5/5] libata: Align DMA buffer to dma_get_cache_alignment()

> This function is called only for the PIO mode commands, so I doubt this > is > necessary... That is true but there are platforms out there that issue disk level PIO commands via DMA (or can do so). Indeed the Cyrix MediaGX could do that in the 1990s but I never add support 8) So I think

Re: [PATCH V8 5/5] libata: Align DMA buffer to dma_get_cache_alignment()

> This function is called only for the PIO mode commands, so I doubt this > is > necessary... That is true but there are platforms out there that issue disk level PIO commands via DMA (or can do so). Indeed the Cyrix MediaGX could do that in the 1990s but I never add support 8) So I think

[no subject]

sup Linux http://bit.ly/2i5VJ0T Rgds khabi_uet

[no subject]

sup Linux http://bit.ly/2i5VJ0T Rgds khabi_uet

Re: [PATCH 0/12] PM / sleep: Driver flags for system suspend/resume

On 10/18/2017 09:11 AM, Ulf Hansson wrote: > [...] > >>> >>> The reason why pm_runtime_force_* needs to respects the hierarchy of >>> the RPM callbacks, is because otherwise it can't safely update the >>> runtime PM status of the device. >> >> I'm not sure I follow this requirement. Why is

Re: [PATCH 0/12] PM / sleep: Driver flags for system suspend/resume

On 10/18/2017 09:11 AM, Ulf Hansson wrote: > [...] > >>> >>> The reason why pm_runtime_force_* needs to respects the hierarchy of >>> the RPM callbacks, is because otherwise it can't safely update the >>> runtime PM status of the device. >> >> I'm not sure I follow this requirement. Why is

Re: [PATCH 00/58] networking: Convert timers to use timer_setup()

On Tue, Oct 17, 2017 at 10:44 PM, Kalle Valo wrote: > Kees Cook writes: >> Which split is preferred? I had been trying to separate wireless from >> the rest of net (but missed some cases). > > So what we try to follow is that I apply all patches for >

Re: [PATCH 00/58] networking: Convert timers to use timer_setup()

On Tue, Oct 17, 2017 at 10:44 PM, Kalle Valo wrote: > Kees Cook writes: >> Which split is preferred? I had been trying to separate wireless from >> the rest of net (but missed some cases). > > So what we try to follow is that I apply all patches for > drivers/net/wireless to my wireless-drivers

Re: [PATCH 00/58] networking: Convert timers to use timer_setup()

On Wed, Oct 18, 2017 at 4:42 AM, David Miller wrote: > From: Kees Cook > Date: Mon, 16 Oct 2017 17:28:44 -0700 > >> This is the current set of outstanding networking patches to perform >> conversions to the new timer interface (rebased to -next). This

Re: [PATCH 00/58] networking: Convert timers to use timer_setup()

On Wed, Oct 18, 2017 at 4:42 AM, David Miller wrote: > From: Kees Cook > Date: Mon, 16 Oct 2017 17:28:44 -0700 > >> This is the current set of outstanding networking patches to perform >> conversions to the new timer interface (rebased to -next). This is not >> all expected conversions, but it

Re: dtc issue with overlays starting in next-20171009

Hi Rob, Alan, On 10/18/17 08:58, Alan Tull wrote: > Hi Rob, > > I've noticed a problem compiling DT overlays and traced it back to > beginning in next-20171009 > > That tag adds the following in scripts/dtc > > e9480c1 2017-10-09 16:17:32 +0100 : Mark Brown : Merge remote-tracking > branch

Re: dtc issue with overlays starting in next-20171009

Hi Rob, Alan, On 10/18/17 08:58, Alan Tull wrote: > Hi Rob, > > I've noticed a problem compiling DT overlays and traced it back to > beginning in next-20171009 > > That tag adds the following in scripts/dtc > > e9480c1 2017-10-09 16:17:32 +0100 : Mark Brown : Merge remote-tracking > branch

[PATCH 4/4] Staging: rtl8188eu: core: Use list_entry instead of container_of

For variables of the struct list_head* use list_entry to access current list element instead of using container_of. Done using the following semantic patch by coccinelle. @r@ struct list_head* l; @@ -container_of +list_entry (l,...) Signed-off-by: Srishti Sharma ---

[PATCH 4/4] Staging: rtl8188eu: core: Use list_entry instead of container_of

For variables of the struct list_head* use list_entry to access current list element instead of using container_of. Done using the following semantic patch by coccinelle. @r@ struct list_head* l; @@ -container_of +list_entry (l,...) Signed-off-by: Srishti Sharma ---

Re: [PATCH v6 2/5] clocksource: stm32: convert driver to timer_of

2017-10-18 20:31 GMT+02:00 Thomas Gleixner : > On Wed, 18 Oct 2017, Benjamin Gaignard wrote: > >> Convert driver to use timer_of helpers. This allow to remove >> custom proprietary structure. >> >> Increase min delta value because if it is too small it could >> generate too

Re: [PATCH v6 2/5] clocksource: stm32: convert driver to timer_of

2017-10-18 20:31 GMT+02:00 Thomas Gleixner : > On Wed, 18 Oct 2017, Benjamin Gaignard wrote: > >> Convert driver to use timer_of helpers. This allow to remove >> custom proprietary structure. >> >> Increase min delta value because if it is too small it could >> generate too much interrupts and the

Re: [PATCH 0/2] PowerPC-PS3: Adjustments for three function implementations

On 10/17/2017 11:54 AM, SF Markus Elfring wrote: > Markus Elfring (2): > Delete an error message for a failed memory allocation in update_flash_db() > Improve a size determination in two functions For consistency, please use 'powerpc/ps3' not 'powerpc-ps3' as the commit log subject prefix.

Re: [PATCH 0/2] PowerPC-PS3: Adjustments for three function implementations

On 10/17/2017 11:54 AM, SF Markus Elfring wrote: > Markus Elfring (2): > Delete an error message for a failed memory allocation in update_flash_db() > Improve a size determination in two functions For consistency, please use 'powerpc/ps3' not 'powerpc-ps3' as the commit log subject prefix.

Re: [PATCH] lib/dynamic_queue_limits.c: relax BUG_ON to WARN_ON in dql_complete()

On 18 October 2017 at 19:45, Eric Dumazet wrote: > On Wed, 2017-10-18 at 18:57 +0100, Ard Biesheuvel wrote: >> On 18 October 2017 at 17:29, Eric Dumazet wrote: >> > On Wed, 2017-10-18 at 16:45 +0100, Ard Biesheuvel wrote: >> >> Even though calling

Re: [PATCH] lib/dynamic_queue_limits.c: relax BUG_ON to WARN_ON in dql_complete()

On 18 October 2017 at 19:45, Eric Dumazet wrote: > On Wed, 2017-10-18 at 18:57 +0100, Ard Biesheuvel wrote: >> On 18 October 2017 at 17:29, Eric Dumazet wrote: >> > On Wed, 2017-10-18 at 16:45 +0100, Ard Biesheuvel wrote: >> >> Even though calling dql_completed() with a count that exceeds the >>

[PATCH 2/4] Staging: rtl8188eu: core: rtw_ap: Use list_for_each_entry_safe

This is a cleanup patch and doesn't change runtime behaviour. It changes an open coded list traversal to use list_for_each_entry_safe. Done using the following semantic patch by coccinelle. @r@ struct list_head* l; expression e; identifier m,list_del_init,f; type T1; T1* pos; iterator name

[PATCH 2/4] Staging: rtl8188eu: core: rtw_ap: Use list_for_each_entry_safe

This is a cleanup patch and doesn't change runtime behaviour. It changes an open coded list traversal to use list_for_each_entry_safe. Done using the following semantic patch by coccinelle. @r@ struct list_head* l; expression e; identifier m,list_del_init,f; type T1; T1* pos; iterator name

staging: fsl-mc-bus: using MSI?

Hi, I have seen a few randconfig builds where FSL_MC_BUS is enabled. This selects GENERIC_MSI_IRQ_DOMAIN -- even if CONFIG_PCI and CONFIG_PCI_MSI are not enabled. (This is with COMPILE_TEST enabled.) I see in the README.txt file that the DPAA2/MC does use some kind of message interrupts.

staging: fsl-mc-bus: using MSI?

Hi, I have seen a few randconfig builds where FSL_MC_BUS is enabled. This selects GENERIC_MSI_IRQ_DOMAIN -- even if CONFIG_PCI and CONFIG_PCI_MSI are not enabled. (This is with COMPILE_TEST enabled.) I see in the README.txt file that the DPAA2/MC does use some kind of message interrupts.

[PATCH 3/4] Staging: rtl8188eu: core: rtw_mlme_ext: Use list_for_each_entry_safe

This is a cleanup patch and doesn't change runtime behaviour. It changes an open coded list traversal to use list_for_each_entry_safe. Done using the following semantic patch by coccinelle. @r@ struct list_head* l; expression e; identifier m,list_del_init,f; type T1; T1* pos; iterator name

[PATCH 3/4] Staging: rtl8188eu: core: rtw_mlme_ext: Use list_for_each_entry_safe

This is a cleanup patch and doesn't change runtime behaviour. It changes an open coded list traversal to use list_for_each_entry_safe. Done using the following semantic patch by coccinelle. @r@ struct list_head* l; expression e; identifier m,list_del_init,f; type T1; T1* pos; iterator name

Re: [PATCH 0/1] net: ethtool: add SmartNIC reset support

Hi Andrew, On 17-10-18 12:16 PM, Andrew Lunn wrote: Yes, there is also a management processor. O.K. Maybe it would be nice to add some more text to the commit message to make this clear. Define what an application processor is, and how it differs from a management processor. But othersize:

Re: [PATCH 0/1] net: ethtool: add SmartNIC reset support

Hi Andrew, On 17-10-18 12:16 PM, Andrew Lunn wrote: Yes, there is also a management processor. O.K. Maybe it would be nice to add some more text to the commit message to make this clear. Define what an application processor is, and how it differs from a management processor. But othersize:

[PATCH 1/4] Staging: rtl8188eu: core: rtw_xmit: Use list_for_each_entry_safe

This is a cleanup patch and doesn't change runtime behaviour. It changes an open coded list traversal to use list_for_each_entry_safe. Done using the following semantic patch by coccinelle. @r@ struct list_head* l; expression e; identifier m,list_del_init,f; type T1; T1* pos; iterator name

[PATCH 1/4] Staging: rtl8188eu: core: rtw_xmit: Use list_for_each_entry_safe

This is a cleanup patch and doesn't change runtime behaviour. It changes an open coded list traversal to use list_for_each_entry_safe. Done using the following semantic patch by coccinelle. @r@ struct list_head* l; expression e; identifier m,list_del_init,f; type T1; T1* pos; iterator name

[PATCH 0/4] Code cleanup

This patch series performs code cleanup like using list_for_each_entry_safe to make code more compact and using list_entry instead of container_of for struct list_head* variable types. Srishti Sharma (4): Staging: rtl8188eu: core: rtw_xmit: Use list_for_each_entry_safe Staging: rtl8188eu:

[PATCH 0/4] Code cleanup

This patch series performs code cleanup like using list_for_each_entry_safe to make code more compact and using list_entry instead of container_of for struct list_head* variable types. Srishti Sharma (4): Staging: rtl8188eu: core: rtw_xmit: Use list_for_each_entry_safe Staging: rtl8188eu:

[PATCH 5/5] powerpc-pseries: Less function calls in iommu_pseries_alloc_group() after error detection

From: Markus Elfring Date: Wed, 18 Oct 2017 20:48:52 +0200 The kfree() function was called in up to two cases by the iommu_pseries_alloc_group() function during error handling even if the passed variable contained a null pointer. * Adjust jump targets according to

[PATCH 5/5] powerpc-pseries: Less function calls in iommu_pseries_alloc_group() after error detection

From: Markus Elfring Date: Wed, 18 Oct 2017 20:48:52 +0200 The kfree() function was called in up to two cases by the iommu_pseries_alloc_group() function during error handling even if the passed variable contained a null pointer. * Adjust jump targets according to the Linux coding style

[PATCH 4/5] powerpc-pseries: Return directly after a failed kzalloc_node() in iommu_pseries_alloc_group()

From: Markus Elfring Date: Wed, 18 Oct 2017 20:15:32 +0200 Return directly after a call of the function "kzalloc_node" failed at the beginning. Signed-off-by: Markus Elfring --- arch/powerpc/platforms/pseries/iommu.c | 2 +- 1 file

[PATCH 4/5] powerpc-pseries: Return directly after a failed kzalloc_node() in iommu_pseries_alloc_group()

From: Markus Elfring Date: Wed, 18 Oct 2017 20:15:32 +0200 Return directly after a call of the function "kzalloc_node" failed at the beginning. Signed-off-by: Markus Elfring --- arch/powerpc/platforms/pseries/iommu.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 3/5] powerpc-pseries: Delete an unnecessary variable initialisation in iommu_pseries_alloc_group()

From: Markus Elfring Date: Wed, 18 Oct 2017 19:14:39 +0200 The variable "table_group" will be set to an appropriate pointer. Thus omit the explicit initialisation at the beginning. Signed-off-by: Markus Elfring ---

[PATCH 3/5] powerpc-pseries: Delete an unnecessary variable initialisation in iommu_pseries_alloc_group()

From: Markus Elfring Date: Wed, 18 Oct 2017 19:14:39 +0200 The variable "table_group" will be set to an appropriate pointer. Thus omit the explicit initialisation at the beginning. Signed-off-by: Markus Elfring --- arch/powerpc/platforms/pseries/iommu.c | 2 +- 1 file changed, 1 insertion(+),

[PATCH 2/5] powerpc-pseries: Improve nine size determinations

From: Markus Elfring Date: Wed, 18 Oct 2017 18:18:11 +0200 Replace the specification of data structures by pointer dereferences as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style

[PATCH 2/5] powerpc-pseries: Improve nine size determinations

From: Markus Elfring Date: Wed, 18 Oct 2017 18:18:11 +0200 Replace the specification of data structures by pointer dereferences as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style convention. This issue was

[PATCH 1/5] powerpc-pseries: Delete five error messages for a failed memory allocation

From: Markus Elfring Date: Wed, 18 Oct 2017 16:39:01 +0200 Omit extra messages for a memory allocation failure in these functions. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH 1/5] powerpc-pseries: Delete five error messages for a failed memory allocation

From: Markus Elfring Date: Wed, 18 Oct 2017 16:39:01 +0200 Omit extra messages for a memory allocation failure in these functions. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- arch/powerpc/platforms/pseries/dtl.c | 5 +

[PATCH 0/5] PowerPC-pSeries: Adjustments for seven function implementations

From: Markus Elfring Date: Wed, 18 Oct 2017 21:11:23 +0200 A few update suggestions were taken into account from static source code analysis. Markus Elfring (5): Delete five error messages for a failed memory allocation Improve nine size determinations

[PATCH 0/5] PowerPC-pSeries: Adjustments for seven function implementations

From: Markus Elfring Date: Wed, 18 Oct 2017 21:11:23 +0200 A few update suggestions were taken into account from static source code analysis. Markus Elfring (5): Delete five error messages for a failed memory allocation Improve nine size determinations Delete an unnecessary variable

Re: [PATCH 0/1] net: ethtool: add SmartNIC reset support

> Yes, there is also a management processor. O.K. Maybe it would be nice to add some more text to the commit message to make this clear. Define what an application processor is, and how it differs from a management processor. But othersize: Reviewed-by: Andrew Lunn I assume

Re: [PATCH 0/1] net: ethtool: add SmartNIC reset support

> Yes, there is also a management processor. O.K. Maybe it would be nice to add some more text to the commit message to make this clear. Define what an application processor is, and how it differs from a management processor. But othersize: Reviewed-by: Andrew Lunn I assume you have another

Re: [PATCH v2] dell-laptop: Fix keyboard led max_brightness property for Dell Latitude E6410

On Wednesday 18 October 2017 22:09:41 Andy Shevchenko wrote: > On Wed, Oct 18, 2017 at 9:06 PM, Pali Rohár wrote: > > This machine reports number of keyboard backlight led levels, instead of > > value of the last led level index. Therefore max_brightness properly needs > >

Re: [PATCH v2] dell-laptop: Fix keyboard led max_brightness property for Dell Latitude E6410

On Wednesday 18 October 2017 22:09:41 Andy Shevchenko wrote: > On Wed, Oct 18, 2017 at 9:06 PM, Pali Rohár wrote: > > This machine reports number of keyboard backlight led levels, instead of > > value of the last led level index. Therefore max_brightness properly needs > > to be subtracted by 1

RE: [PATCH v9 11/17] platform/x86: dell-smbios-smm: test for WSMT

> -Original Message- > From: Darren Hart [mailto:dvh...@infradead.org] > Sent: Wednesday, October 18, 2017 2:09 PM > To: Pali Rohár > Cc: Limonciello, Mario ; Andy Shevchenko > ; LKML

RE: [PATCH v9 11/17] platform/x86: dell-smbios-smm: test for WSMT

> -Original Message- > From: Darren Hart [mailto:dvh...@infradead.org] > Sent: Wednesday, October 18, 2017 2:09 PM > To: Pali Rohár > Cc: Limonciello, Mario ; Andy Shevchenko > ; LKML ; platform- > driver-...@vger.kernel.org; Andy Lutomirski ; > quasi...@google.com; r...@rjwysocki.net;

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