Re: [PATCH 1/2] Alps HID I2C T4 device support

Dear Masaki, Thanks! I think I figured out the problem - it was on my side. After I installed your patch, I ran "make localmodconfig". However, I think prior to your patch my touchpad was handled by hid_generic - so hid_alps was not loaded and the patched module thus never build. However, your

Re: [PATCH 1/2] Alps HID I2C T4 device support

Dear Masaki, Thanks! I think I figured out the problem - it was on my side. After I installed your patch, I ran "make localmodconfig". However, I think prior to your patch my touchpad was handled by hid_generic - so hid_alps was not loaded and the patched module thus never build. However, your

Re: [GIT PULL] AppArmor fixes for 4.12

On Thu, 6 Apr 2017, John Johansen wrote: > Hi James, > > Here is the pull request for 4.12 > > There are no new features here, just a small set of bug fixes since > the 4.11 pull request. All applied to: git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next -- James

Re: [GIT PULL] AppArmor fixes for 4.12

On Thu, 6 Apr 2017, John Johansen wrote: > Hi James, > > Here is the pull request for 4.12 > > There are no new features here, just a small set of bug fixes since > the 4.11 pull request. All applied to: git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next -- James

Re: [RFC][PATCH 1/2] printk: Introduce per-console filtering of messages by loglevel

On Thursday 04/06 at 16:02 +0200, Petr Mladek wrote: > On Wed 2017-04-05 17:38:19, Calvin Owens wrote: > > On Wednesday 04/05 at 17:22 +0200, Petr Mladek wrote: > > > I think about a reasonable behavior. There seems to be three variables > > > that are related and are in use: > > > > > >

Re: [RFC][PATCH 1/2] printk: Introduce per-console filtering of messages by loglevel

On Thursday 04/06 at 16:02 +0200, Petr Mladek wrote: > On Wed 2017-04-05 17:38:19, Calvin Owens wrote: > > On Wednesday 04/05 at 17:22 +0200, Petr Mladek wrote: > > > I think about a reasonable behavior. There seems to be three variables > > > that are related and are in use: > > > > > >

Re: [Outreachy kernel] [PATCH] net: netfilter: Remove typedef from "typedef struct bitstr_t".

On Tue, Mar 28, 2017 at 11:54:13PM +0530, Arushi Singhal wrote: > This patch removes typedefs from struct and renames it from "typedef struct > bitstr_t" to "struct bitstr" as per kernel coding standards." > > Signed-off-by: Arushi Singhal > --- >

Re: [Outreachy kernel] [PATCH] net: netfilter: Remove typedef from "typedef struct bitstr_t".

On Tue, Mar 28, 2017 at 11:54:13PM +0530, Arushi Singhal wrote: > This patch removes typedefs from struct and renames it from "typedef struct > bitstr_t" to "struct bitstr" as per kernel coding standards." > > Signed-off-by: Arushi Singhal > --- > net/netfilter/nf_conntrack_h323_asn1.c | 80 >

Re: [PATCH] mac80211: Fix clang warning about constant operand in logical operation

On Thu, 2017-04-06 at 15:42 -0700, Matthias Kaehlcke wrote: > > Thanks, it would also require to move the initialization of > ieee80211_default_rc_algo into an ifdef. If you can live with such a > solution I'm happy to change it. I think that'd be something I can live with, yeah. > > git

Re: [PATCH] mac80211: Fix clang warning about constant operand in logical operation

On Thu, 2017-04-06 at 15:42 -0700, Matthias Kaehlcke wrote: > > Thanks, it would also require to move the initialization of > ieee80211_default_rc_algo into an ifdef. If you can live with such a > solution I'm happy to change it. I think that'd be something I can live with, yeah. > > git

Re: [PATCH 3/5] Add the ability to lock down access to the running kernel image

On Thu, 6 Apr 2017, David Howells wrote: > Provide a single call to allow kernel code to determine whether the system > should be locked down, thereby disallowing various accesses that might > allow the running kernel image to be changed including the loading of > modules that aren't validly

Re: [PATCH 3/5] Add the ability to lock down access to the running kernel image

On Thu, 6 Apr 2017, David Howells wrote: > Provide a single call to allow kernel code to determine whether the system > should be locked down, thereby disallowing various accesses that might > allow the running kernel image to be changed including the loading of > modules that aren't validly

Re: [PATCH] mac80211: Fix clang warning about constant operand in logical operation

El Thu, Apr 06, 2017 at 11:12:25PM +0200 Johannes Berg ha dit: > On Thu, 2017-04-06 at 12:24 -0700, Matthias Kaehlcke wrote: > > > I agree that the code looks worse :( I hoped to find a fix using a > > preprocessor condition but wasn't successful. > > It's actually easy - just remove the

Re: [PATCH] mac80211: Fix clang warning about constant operand in logical operation

El Thu, Apr 06, 2017 at 11:12:25PM +0200 Johannes Berg ha dit: > On Thu, 2017-04-06 at 12:24 -0700, Matthias Kaehlcke wrote: > > > I agree that the code looks worse :( I hoped to find a fix using a > > preprocessor condition but wasn't successful. > > It's actually easy - just remove the

Re: [PATCH] of: change fixup of dma-ranges size to error

On Thu, Apr 6, 2017 at 1:37 PM, Frank Rowand wrote: > On 04/06/17 07:03, Rob Herring wrote: >> On Thu, Apr 6, 2017 at 1:18 AM, wrote: >>> From: Frank Rowand >>> >>> of_dma_get_range() has workaround code to fixup a device

Re: [PATCH] of: change fixup of dma-ranges size to error

On Thu, Apr 6, 2017 at 1:37 PM, Frank Rowand wrote: > On 04/06/17 07:03, Rob Herring wrote: >> On Thu, Apr 6, 2017 at 1:18 AM, wrote: >>> From: Frank Rowand >>> >>> of_dma_get_range() has workaround code to fixup a device tree that >>> incorrectly specified a mask instead of a size for

Re: [PATCH 0/2] mtd: spi-nor: add stm32 qspi driver

Hi all, Le 30/03/2017 à 12:15, Marek Vasut a écrit : > On 03/30/2017 09:31 AM, Ludovic BARRE wrote: >> hi Cyrille >> >> I see your patch series >> >> [PATCH v5 0/6] mtd: spi-nor: parse SFDP tables to setup (Q)SPI memories >> >> No problem, I rebase my V2 onto your patch > > I still didn't review

Re: [PATCH 0/2] mtd: spi-nor: add stm32 qspi driver

Hi all, Le 30/03/2017 à 12:15, Marek Vasut a écrit : > On 03/30/2017 09:31 AM, Ludovic BARRE wrote: >> hi Cyrille >> >> I see your patch series >> >> [PATCH v5 0/6] mtd: spi-nor: parse SFDP tables to setup (Q)SPI memories >> >> No problem, I rebase my V2 onto your patch > > I still didn't review

Re: [PATCH 2/3] ARM: dts: rockchip: rock2: Setup usb vbus-supply

Am Mittwoch, 5. April 2017, 16:06:11 CEST schrieb Sjoerd Simons: > Now that the rockchip usb phy has a vbus-supply property use that to > control the vbus regulator on rock2. > > Signed-off-by: Sjoerd Simons I've queued this for 4.13 . Not eligible for 4.12, as

Re: [PATCH 2/3] ARM: dts: rockchip: rock2: Setup usb vbus-supply

Am Mittwoch, 5. April 2017, 16:06:11 CEST schrieb Sjoerd Simons: > Now that the rockchip usb phy has a vbus-supply property use that to > control the vbus regulator on rock2. > > Signed-off-by: Sjoerd Simons I've queued this for 4.13 . Not eligible for 4.12, as the patch alone (when testing my

Re: [PATCH v2 1/3] ARM: dts: rockchip: Add support for phyCORE-RK3288 SoM

Am Donnerstag, 6. April 2017, 15:04:24 CEST schrieb Wadim Egorov: > The phyCORE-RK3288 is a SoM (System on Module) containing a RK3288 SoC. > The module can be connected to different carrier boards. > It can be also equipped with different RAM, SPI flash and eMMC variants. > The Rapid Development

Re: [PATCH v2 1/3] ARM: dts: rockchip: Add support for phyCORE-RK3288 SoM

Am Donnerstag, 6. April 2017, 15:04:24 CEST schrieb Wadim Egorov: > The phyCORE-RK3288 is a SoM (System on Module) containing a RK3288 SoC. > The module can be connected to different carrier boards. > It can be also equipped with different RAM, SPI flash and eMMC variants. > The Rapid Development

Re: [RFC PATCH 0/4] fs: introduce new writeback error tracking infrastructure and convert ext4 to use it

On Thu, Apr 06 2017, Jeff Layton wrote: > > I tried to avoid updating things unnecesssarily. I could use some > guidance on how to specify the constants in terms of MAX_ERRNO as well. ilog2() defined in include/linux/log2.h And you have MAX_ERROR in one comment, instead of MAX_ERRNO :-) > >

Re: [RFC PATCH 0/4] fs: introduce new writeback error tracking infrastructure and convert ext4 to use it

On Thu, Apr 06 2017, Jeff Layton wrote: > > I tried to avoid updating things unnecesssarily. I could use some > guidance on how to specify the constants in terms of MAX_ERRNO as well. ilog2() defined in include/linux/log2.h And you have MAX_ERROR in one comment, instead of MAX_ERRNO :-) > >

Re: [PATCH 3/4] tracing: Add stack_tracer_disable/enable() functions

On Thu, Apr 06, 2017 at 05:23:48PM -0400, Steven Rostedt wrote: > On Thu, 6 Apr 2017 13:21:17 -0700 > "Paul E. McKenney" wrote: > > > > My worry is that we add another caller that doesn't disable interrupts > > > or preemption. > > > > > > I could add a

Re: [PATCH 3/4] tracing: Add stack_tracer_disable/enable() functions

On Thu, Apr 06, 2017 at 05:23:48PM -0400, Steven Rostedt wrote: > On Thu, 6 Apr 2017 13:21:17 -0700 > "Paul E. McKenney" wrote: > > > > My worry is that we add another caller that doesn't disable interrupts > > > or preemption. > > > > > > I could add a __stack_trace_disable() that skips the

Re: [Outreachy kernel] [PATCH v3] net: netfilter: Add nfnl_msg_type() helper function

Hi, On Tue, Mar 28, 2017 at 10:27:32PM +0530, Arushi Singhal wrote: > To remove complexity of code the function is added in nfnetlink.h > to make code more clear and readable. > This is opencoded in a way that makes it error prone for future > netfilter netlink subsystems. > > Signed-off-by:

Re: [Outreachy kernel] [PATCH v3] net: netfilter: Add nfnl_msg_type() helper function

Hi, On Tue, Mar 28, 2017 at 10:27:32PM +0530, Arushi Singhal wrote: > To remove complexity of code the function is added in nfnetlink.h > to make code more clear and readable. > This is opencoded in a way that makes it error prone for future > netfilter netlink subsystems. > > Signed-off-by:

[PATCH net-next 1/1] netvsc: Initialize all channel related state prior to opening the channel

From: K. Y. Srinivasan Prior to opening the channel we should have all the state setup to handle interrupts. The current code does not do that; fix the bug. This bug can result in faults in the interrupt path. Signed-off-by: K. Y. Srinivasan ---

[PATCH net-next 1/1] netvsc: Initialize all channel related state prior to opening the channel

From: K. Y. Srinivasan Prior to opening the channel we should have all the state setup to handle interrupts. The current code does not do that; fix the bug. This bug can result in faults in the interrupt path. Signed-off-by: K. Y. Srinivasan --- drivers/net/hyperv/netvsc.c | 27

Re: [PATCH 1/2] devicetree: add vendor prefix for Winstar Display Corp.

On Fri, Mar 03, 2017 at 04:21:55PM +0100, Richard Genoud wrote: > Winstar Display Corp. is specialized in LCD displays for embedded > products. > cf: http://www.winstar.com.tw > > Signed-off-by: Richard Genoud > --- >

Re: [PATCH 1/2] devicetree: add vendor prefix for Winstar Display Corp.

On Fri, Mar 03, 2017 at 04:21:55PM +0100, Richard Genoud wrote: > Winstar Display Corp. is specialized in LCD displays for embedded > products. > cf: http://www.winstar.com.tw > > Signed-off-by: Richard Genoud > --- > Documentation/devicetree/bindings/vendor-prefixes.txt | 1 + > 1 file

Re: [PATCH 02/24] Add the ability to lock down access to the running kernel image

On Thu, 6 Apr 2017, David Howells wrote: > James Morris wrote: > > > > +static __read_mostly bool kernel_locked_down; > > > > How about marking this __ro_after_init if ALLOW_LOCKDOWN_LIFT is not > > configured? > > I guess lock_kernel_down() would need to be __init also in

Re: [PATCH 02/24] Add the ability to lock down access to the running kernel image

On Thu, 6 Apr 2017, David Howells wrote: > James Morris wrote: > > > > +static __read_mostly bool kernel_locked_down; > > > > How about marking this __ro_after_init if ALLOW_LOCKDOWN_LIFT is not > > configured? > > I guess lock_kernel_down() would need to be __init also in that case.

Re: [PATCH 4.4 00/26] 4.4.60-stable review

On Thu, Apr 06, 2017 at 10:38:22AM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.60 release. > There are 26 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me

Re: [PATCH 4.4 00/26] 4.4.60-stable review

On Thu, Apr 06, 2017 at 10:38:22AM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.60 release. > There are 26 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me

Re: [RFC PATCH 0/4] fs: introduce new writeback error tracking infrastructure and convert ext4 to use it

On Thu, Apr 06 2017, Matthew Wilcox wrote: > On Thu, Apr 06, 2017 at 03:12:42PM +1000, NeilBrown wrote: >> On Wed, Apr 05 2017, Matthew Wilcox wrote: >> >> > On Thu, Apr 06, 2017 at 10:02:48AM +1000, NeilBrown wrote: >> >> If you are concerned about space in 'struct address_space', just prune >>

Re: [RFC PATCH 0/4] fs: introduce new writeback error tracking infrastructure and convert ext4 to use it

On Thu, Apr 06 2017, Matthew Wilcox wrote: > On Thu, Apr 06, 2017 at 03:12:42PM +1000, NeilBrown wrote: >> On Wed, Apr 05 2017, Matthew Wilcox wrote: >> >> > On Thu, Apr 06, 2017 at 10:02:48AM +1000, NeilBrown wrote: >> >> If you are concerned about space in 'struct address_space', just prune >>

Re: [PATCH v3 2/2] drm/panel: Add driver for sitronix ST7789V LCD controller

On Mon, Apr 03, 2017 at 03:38:32PM +0200, Maxime Ripard wrote: > The Sitronix ST7789v controller is used to drive 240x320 LCD panels through > various interfaces, including SPI and RGB/Parallel. > > The current driver is configuring it for the latter. Support for tinyDRM > can always be added

Re: [PATCH v3 2/2] drm/panel: Add driver for sitronix ST7789V LCD controller

On Mon, Apr 03, 2017 at 03:38:32PM +0200, Maxime Ripard wrote: > The Sitronix ST7789v controller is used to drive 240x320 LCD panels through > various interfaces, including SPI and RGB/Parallel. > > The current driver is configuring it for the latter. Support for tinyDRM > can always be added

Re: [PATCH 4.10 00/81] 4.10.9-stable review

On Thu, Apr 06, 2017 at 10:37:52AM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.10.9 release. > There are 81 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me

Re: [PATCH 4.10 00/81] 4.10.9-stable review

On Thu, Apr 06, 2017 at 10:37:52AM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.10.9 release. > There are 81 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me

Re: [PATCH v3 1/2] dt-bindings: display: panel: Add bindings for the Sitronix ST7789V panel

On Mon, Apr 03, 2017 at 03:38:31PM +0200, Maxime Ripard wrote: > The Sitronix ST7789V is an LCD panel controller, controlled over SPI, that > can drive 18-bits 240x320 LCD displays. > > Signed-off-by: Maxime Ripard > Acked-by: Rob Herring > ---

Re: [PATCH v3 1/2] dt-bindings: display: panel: Add bindings for the Sitronix ST7789V panel

On Mon, Apr 03, 2017 at 03:38:31PM +0200, Maxime Ripard wrote: > The Sitronix ST7789V is an LCD panel controller, controlled over SPI, that > can drive 18-bits 240x320 LCD displays. > > Signed-off-by: Maxime Ripard > Acked-by: Rob Herring > --- >

Re: [PATCH 4.9 00/72] 4.9.21-stable review

On Thu, Apr 06, 2017 at 10:37:47AM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.21 release. > There are 72 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me

Re: [PATCH 4.9 00/72] 4.9.21-stable review

On Thu, Apr 06, 2017 at 10:37:47AM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.21 release. > There are 72 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me

Re: linux-next: manual merge of the staging tree with the v4l-dvb tree

Hi Sean, On Thu, 6 Apr 2017 21:39:05 +0100 Sean Young wrote: > > I think this is happening: > > On the v4l-dvb tree, 5cd6522 modifies both lirc_sasem.c and lirc_sir.c; > then both files are removed. Now 87ddb91067b9 is merged from the staging > tree and both files don't exist any

Re: linux-next: manual merge of the staging tree with the v4l-dvb tree

Hi Sean, On Thu, 6 Apr 2017 21:39:05 +0100 Sean Young wrote: > > I think this is happening: > > On the v4l-dvb tree, 5cd6522 modifies both lirc_sasem.c and lirc_sir.c; > then both files are removed. Now 87ddb91067b9 is merged from the staging > tree and both files don't exist any more, so it no

Re: [PATCH 2/2] platform/x86: silead_dmi - abort early if DMI does not match

On Tue, Apr 4, 2017 at 6:25 AM, Dmitry Torokhov wrote: > There is no point in registering I2C bus notifier if DMI data does not > match. > Both applied to testing. Please check I didn't mess things up. Thanks! > Signed-off-by: Dmitry Torokhov

Re: [PATCH 2/2] platform/x86: silead_dmi - abort early if DMI does not match

On Tue, Apr 4, 2017 at 6:25 AM, Dmitry Torokhov wrote: > There is no point in registering I2C bus notifier if DMI data does not > match. > Both applied to testing. Please check I didn't mess things up. Thanks! > Signed-off-by: Dmitry Torokhov > --- > drivers/platform/x86/silead_dmi.c | 20

Re: [PATCH v6 5/6] platform/x86: intel_pmc_ipc: Fix iTCO_wdt GCS memory mapping failure

On Thu, Apr 6, 2017 at 1:54 AM, Kuppuswamy Sathyanarayanan wrote: > iTCO_wdt driver need access to PMC_CFG GCR register to modify the > noreboot setting. Currently, this is done by passing PMC_CFG reg > address as memory resource to watchdog driver and

Re: [PATCH v6 5/6] platform/x86: intel_pmc_ipc: Fix iTCO_wdt GCS memory mapping failure

On Thu, Apr 6, 2017 at 1:54 AM, Kuppuswamy Sathyanarayanan wrote: > iTCO_wdt driver need access to PMC_CFG GCR register to modify the > noreboot setting. Currently, this is done by passing PMC_CFG reg > address as memory resource to watchdog driver and allowing it directly > modify the PMC_CFG

Re: [PATCH v11 2/3] drm/panel: Add support for S6E3HA2 panel driver on TM2 board

On Wed, Mar 08, 2017 at 10:42:36AM +0900, Hoegeun Kwon wrote: > This patch add support for MIPI-DSI based S6E3HA2 AMOLED panel > driver. This panel has 1440x2560 resolution in 5.7-inch physical > panel in the TM2 device. > > Signed-off-by: Donghwa Lee > Signed-off-by:

Re: [PATCH v11 1/3] dt-bindings: Add support for samsung s6e3ha2 panel binding

On Wed, Mar 08, 2017 at 10:42:35AM +0900, Hoegeun Kwon wrote: > The Samsung s6e3ha2 is a 5.7" 1440x2560 AMOLED panel connected > using MIPI-DSI interfaces. > > Signed-off-by: Donghwa Lee > Signed-off-by: Hyungwon Hwang > Signed-off-by: Hoegeun Kwon

Re: [PATCH v11 2/3] drm/panel: Add support for S6E3HA2 panel driver on TM2 board

On Wed, Mar 08, 2017 at 10:42:36AM +0900, Hoegeun Kwon wrote: > This patch add support for MIPI-DSI based S6E3HA2 AMOLED panel > driver. This panel has 1440x2560 resolution in 5.7-inch physical > panel in the TM2 device. > > Signed-off-by: Donghwa Lee > Signed-off-by: Hyungwon Hwang >

Re: [PATCH v11 1/3] dt-bindings: Add support for samsung s6e3ha2 panel binding

On Wed, Mar 08, 2017 at 10:42:35AM +0900, Hoegeun Kwon wrote: > The Samsung s6e3ha2 is a 5.7" 1440x2560 AMOLED panel connected > using MIPI-DSI interfaces. > > Signed-off-by: Donghwa Lee > Signed-off-by: Hyungwon Hwang > Signed-off-by: Hoegeun Kwon > Reviewed-by: Andrzej Hajda > Reviewed-by:

[PATCH] dax: fix radix tree insertion race

While running generic/340 in my test setup I hit the following race. It can happen with kernels that support FS DAX PMDs, so v4.10 thru v4.11-rc5. Thread 1Thread 2 dax_iomap_pmd_fault() grab_mapping_entry()

[PATCH] dax: fix radix tree insertion race

While running generic/340 in my test setup I hit the following race. It can happen with kernels that support FS DAX PMDs, so v4.10 thru v4.11-rc5. Thread 1Thread 2 dax_iomap_pmd_fault() grab_mapping_entry()

Re: [PATCH] ath9k: Add cast to u8 to FREQ2FBIN macro

On Thu, 2017-04-06 at 14:21 -0700, Matthias Kaehlcke wrote: > The macro results are assigned to u8 variables/fields. Adding the cast > fixes plenty of clang warnings about "implicit conversion from 'int' to > 'u8'". > > Signed-off-by: Matthias Kaehlcke > --- >

Re: [PATCH] ath9k: Add cast to u8 to FREQ2FBIN macro

On Thu, 2017-04-06 at 14:21 -0700, Matthias Kaehlcke wrote: > The macro results are assigned to u8 variables/fields. Adding the cast > fixes plenty of clang warnings about "implicit conversion from 'int' to > 'u8'". > > Signed-off-by: Matthias Kaehlcke > --- >

Re: [PATCH] staging: rtl8192u: ieee80211: Fix space required after }.

Hi, Thanks for the feedback. I re-submitted the patch as v2. best Valerio Il 06/04/2017 01:57, Joe Perches ha scritto: > On Wed, 2017-04-05 at 21:23 +0200, Valerio Genovese wrote: >> This was reported by checkpatch.pl: >> ERROR: space required after that close brace '}' >> >> Signed-off-by:

Re: [PATCH] staging: rtl8192u: ieee80211: Fix space required after }.

Hi, Thanks for the feedback. I re-submitted the patch as v2. best Valerio Il 06/04/2017 01:57, Joe Perches ha scritto: > On Wed, 2017-04-05 at 21:23 +0200, Valerio Genovese wrote: >> This was reported by checkpatch.pl: >> ERROR: space required after that close brace '}' >> >> Signed-off-by:

Fast Loans

Do you need a loan to pay up bill or to start a business? Email Us

Fast Loans

Do you need a loan to pay up bill or to start a business? Email Us

[GIT PULL] xfs: fixes for 4.11-rc6

Hi Linus, Here are three more fixes for 4.11. The first one reworks the inline directory verifier to check the working copy of the directory metadata and to avoid triggering a periodic crash in xfs/348. The second patch fixes a regression in hole punching at EOF that corrupts files; and the

[GIT PULL] xfs: fixes for 4.11-rc6

Hi Linus, Here are three more fixes for 4.11. The first one reworks the inline directory verifier to check the working copy of the directory metadata and to avoid triggering a periodic crash in xfs/348. The second patch fixes a regression in hole punching at EOF that corrupts files; and the

Re: [PATCH 3/4] tracing: Add stack_tracer_disable/enable() functions

On Thu, 6 Apr 2017 13:21:17 -0700 "Paul E. McKenney" wrote: > > My worry is that we add another caller that doesn't disable interrupts > > or preemption. > > > > I could add a __stack_trace_disable() that skips the disabling of > > preemption, as the "__" usually

Re: [PATCH 3/4] tracing: Add stack_tracer_disable/enable() functions

On Thu, 6 Apr 2017 13:21:17 -0700 "Paul E. McKenney" wrote: > > My worry is that we add another caller that doesn't disable interrupts > > or preemption. > > > > I could add a __stack_trace_disable() that skips the disabling of > > preemption, as the "__" usually denotes the call is "special".

Re: [PATCH net-next 0/7] rxrpc: Miscellany

From: David Howells <dhowe...@redhat.com> Date: Thu, 06 Apr 2017 11:22:14 +0100 > Here's a set of patches that make some minor changes to AF_RXRPC: ... > Tagged thusly: > > git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git > rxrpc-rewrite-201

Re: [PATCH net-next 0/7] rxrpc: Miscellany

From: David Howells Date: Thu, 06 Apr 2017 11:22:14 +0100 > Here's a set of patches that make some minor changes to AF_RXRPC: ... > Tagged thusly: > > git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git > rxrpc-rewrite-20170406 Pulled, thanks David.

Re: [HMM 14/16] mm/hmm/devmem: device memory hotplug using ZONE_DEVICE

So during rebase on lastest mmotm one if branch logic got inversed. Attached is a fixup patch. Cheers, Jérôme >From 374bca39b19a88da1d1c6d38c0a4c49c1af31c18 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=A9r=C3=B4me=20Glisse?= Date: Thu, 6 Apr 2017 17:16:56 -0400 Subject:

To：总经理/参展负责人（收）--《参展邀请函》6月！第十五届中国（广州）国际汽车零部件及用品展 liyuguangdian [08GC/M]

liyuguangdian 中国国际汽车零部件博览会 China International Auto Parts Expo 中华人民共和国商务部引导支持展会 国家级国际性汽车配件用品展贸平台 　 【中文名称】 2017第十五届中国（广州）国际汽车零部件及用品展览会 【英文名称】 The 15th China (Guangzhou) International Auto Parts Expo,2017 （CAPE 2017） 　 【展会日期】 2017年06月02—04日 【展会场馆】 广州琶洲保利世贸博览馆 　 【展会简介】

Re: [HMM 14/16] mm/hmm/devmem: device memory hotplug using ZONE_DEVICE

So during rebase on lastest mmotm one if branch logic got inversed. Attached is a fixup patch. Cheers, Jérôme >From 374bca39b19a88da1d1c6d38c0a4c49c1af31c18 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=A9r=C3=B4me=20Glisse?= Date: Thu, 6 Apr 2017 17:16:56 -0400 Subject: [PATCH] fixup!

To：总经理/参展负责人（收）--《参展邀请函》6月！第十五届中国（广州）国际汽车零部件及用品展 liyuguangdian [08GC/M]

liyuguangdian 中国国际汽车零部件博览会 China International Auto Parts Expo 中华人民共和国商务部引导支持展会 国家级国际性汽车配件用品展贸平台 　 【中文名称】 2017第十五届中国（广州）国际汽车零部件及用品展览会 【英文名称】 The 15th China (Guangzhou) International Auto Parts Expo,2017 （CAPE 2017） 　 【展会日期】 2017年06月02—04日 【展会场馆】 广州琶洲保利世贸博览馆 　 【展会简介】

[PATCH] ath9k: Add cast to u8 to FREQ2FBIN macro

The macro results are assigned to u8 variables/fields. Adding the cast fixes plenty of clang warnings about "implicit conversion from 'int' to 'u8'". Signed-off-by: Matthias Kaehlcke --- drivers/net/wireless/ath/ath9k/eeprom.h | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH] ath9k: Add cast to u8 to FREQ2FBIN macro

The macro results are assigned to u8 variables/fields. Adding the cast fixes plenty of clang warnings about "implicit conversion from 'int' to 'u8'". Signed-off-by: Matthias Kaehlcke --- drivers/net/wireless/ath/ath9k/eeprom.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH] scsi: qla2xxx: remove some redundant pointer assignments

On Thu, 6 Apr 2017, 4:19am, Colin King wrote: > From: Colin Ian King > > There are several local or function parameter pointers that are > being assigned NULL after a kfree where and these have no effect > and hence can be removed. > > Fixes various cppcheck

Re: [PATCH] scsi: qla2xxx: remove some redundant pointer assignments

On Thu, 6 Apr 2017, 4:19am, Colin King wrote: > From: Colin Ian King > > There are several local or function parameter pointers that are > being assigned NULL after a kfree where and these have no effect > and hence can be removed. > > Fixes various cppcheck warnings: > > "Assignment of

Re: [PATCH] mac80211: Fix clang warning about constant operand in logical operation

On Thu, 2017-04-06 at 12:24 -0700, Matthias Kaehlcke wrote: > I agree that the code looks worse :( I hoped to find a fix using a > preprocessor condition but wasn't successful. It's actually easy - just remove the 'default ""' from Kconfig, and then the symbol won't be defined at all if it

Re: [PATCH] mac80211: Fix clang warning about constant operand in logical operation

On Thu, 2017-04-06 at 12:24 -0700, Matthias Kaehlcke wrote: > I agree that the code looks worse :( I hoped to find a fix using a > preprocessor condition but wasn't successful. It's actually easy - just remove the 'default ""' from Kconfig, and then the symbol won't be defined at all if it

[PATCH] x86, pmem: fix broken __copy_user_nocache cache-bypass assumptions

Before we rework the "pmem api" to stop abusing __copy_user_nocache() for memcpy_to_pmem() we need to fix cases where we may strand dirty data in the cpu cache. The problem occurs when copy_from_iter_pmem() is used for arbitrary data transfers from userspace. There is no guarantee that these

[PATCH] x86, pmem: fix broken __copy_user_nocache cache-bypass assumptions

Before we rework the "pmem api" to stop abusing __copy_user_nocache() for memcpy_to_pmem() we need to fix cases where we may strand dirty data in the cpu cache. The problem occurs when copy_from_iter_pmem() is used for arbitrary data transfers from userspace. There is no guarantee that these

Re: [PATCH v3 0/5] DRM OF graph clean-up

On Wed, Mar 22, 2017 at 9:26 AM, Rob Herring wrote: > I've been unhappy with the OF graph API for some time and decided to > do something about it. The problem is drivers have to do too much of the > graph parsing and walking themselves. This has led to the same pattern >

Re: [PATCH v3 0/5] DRM OF graph clean-up

On Wed, Mar 22, 2017 at 9:26 AM, Rob Herring wrote: > I've been unhappy with the OF graph API for some time and decided to > do something about it. The problem is drivers have to do too much of the > graph parsing and walking themselves. This has led to the same pattern > duplicated over and

Re: [PATCH RFC 1/6] KVM: fix guest_mode optimization in kvm_make_all_cpus_request()

On Thu, Apr 06, 2017 at 10:20:51PM +0200, Radim Krčmář wrote: > We have kvm_arch_vcpu_should_kick() to decide whether the target cpu > needs to be kicked. The previous condition was wrong, because > architectures that don't use vcpu->mode would not get interrupts and > also suboptimal, because it

Re: [PATCH RFC 1/6] KVM: fix guest_mode optimization in kvm_make_all_cpus_request()

On Thu, Apr 06, 2017 at 10:20:51PM +0200, Radim Krčmář wrote: > We have kvm_arch_vcpu_should_kick() to decide whether the target cpu > needs to be kicked. The previous condition was wrong, because > architectures that don't use vcpu->mode would not get interrupts and > also suboptimal, because it

[PATCH] staging: unisys: visornic: Replace symbolic perms with octal

Replace symbolic permissions S_IRUSR and S_IWUSR for their octal counterparts Signed-off-by: Thomas Jespersen Acked-by: David Kershner --- drivers/staging/unisys/visornic/visornic_main.c | 4 ++-- 1 file changed, 2 insertions(+), 2

[PATCH] staging: unisys: visornic: Replace symbolic perms with octal

Replace symbolic permissions S_IRUSR and S_IWUSR for their octal counterparts Signed-off-by: Thomas Jespersen Acked-by: David Kershner --- drivers/staging/unisys/visornic/visornic_main.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

Re: WARN @lib/refcount.c:128 during hot unplug of I/O adapter.

On 04/06/2017 03:27 AM, Sachin Sant wrote: > On a POWER8 LPAR running 4.11.0-rc5, a hot unplug operation on > any I/O adapter results in the following warning > > This problem has been in the code for some time now. I had first seen this in > -next tree. > > [ 269.589441] rpadlpar_io: slot PHB

Re: WARN @lib/refcount.c:128 during hot unplug of I/O adapter.

On 04/06/2017 03:27 AM, Sachin Sant wrote: > On a POWER8 LPAR running 4.11.0-rc5, a hot unplug operation on > any I/O adapter results in the following warning > > This problem has been in the code for some time now. I had first seen this in > -next tree. > > [ 269.589441] rpadlpar_io: slot PHB

Re: [PATCH net-next v5 0/2] L2TP:Adjust intf MTU, add underlay L3, L2 hdrs.

From: "R. Parameswaran" Date: Wed, 5 Apr 2017 17:05:49 -0700 (PDT) > > Existing L2TP kernel code does not derive the optimal MTU for Ethernet > pseudowires and instead leaves this to a userspace L2TP daemon or > operator. If an MTU is not specified, the existing

Re: [PATCH net-next v5 0/2] L2TP:Adjust intf MTU, add underlay L3, L2 hdrs.

From: "R. Parameswaran" Date: Wed, 5 Apr 2017 17:05:49 -0700 (PDT) > > Existing L2TP kernel code does not derive the optimal MTU for Ethernet > pseudowires and instead leaves this to a userspace L2TP daemon or > operator. If an MTU is not specified, the existing kernel code chooses > an MTU

Loan offer.

We can help you with a genuine loan to meet your needs. Do you need a personal or business loan without stress and quick approval? Do you need an urgent loan today? No Credit Checks * LOAN APPROVAL IN 60MINS !! * GUARANTEED SAME DAY TRANSFER !! * 100% APPROVAL RATE !! * LOW INTEREST RATE !!

Loan offer.

We can help you with a genuine loan to meet your needs. Do you need a personal or business loan without stress and quick approval? Do you need an urgent loan today? No Credit Checks * LOAN APPROVAL IN 60MINS !! * GUARANTEED SAME DAY TRANSFER !! * 100% APPROVAL RATE !! * LOW INTEREST RATE !!

Re: linux-next: manual merge of the staging tree with the v4l-dvb tree

On Thu, Apr 06, 2017 at 09:19:22PM +0200, Greg KH wrote: > On Thu, Apr 06, 2017 at 07:58:57PM +0100, Sean Young wrote: > > On Thu, Apr 06, 2017 at 01:34:20PM +1000, Stephen Rothwell wrote: > > > Hi all, > > > > > > Today's linux-next merge of the staging tree got conflicts in: > > > > > >

Re: linux-next: manual merge of the staging tree with the v4l-dvb tree

On Thu, Apr 06, 2017 at 09:19:22PM +0200, Greg KH wrote: > On Thu, Apr 06, 2017 at 07:58:57PM +0100, Sean Young wrote: > > On Thu, Apr 06, 2017 at 01:34:20PM +1000, Stephen Rothwell wrote: > > > Hi all, > > > > > > Today's linux-next merge of the staging tree got conflicts in: > > > > > >

Re: [PATCH] net: ethernet: wiznet: avoid format string exposure

From: Kees Cook Date: Wed, 5 Apr 2017 14:39:35 -0700 > While unlikely, this makes sure any format strings in the device name > can't exposure information via the resulting workqueue name. > > Signed-off-by: Kees Cook Applied.

Re: [PATCH] net: ethernet: wiznet: avoid format string exposure

From: Kees Cook Date: Wed, 5 Apr 2017 14:39:35 -0700 > While unlikely, this makes sure any format strings in the device name > can't exposure information via the resulting workqueue name. > > Signed-off-by: Kees Cook Applied.

Re: [PATCH] qlge: avoid format string exposure in workqueue

From: Kees Cook Date: Wed, 5 Apr 2017 14:39:03 -0700 > While unlikely, this makes sure the workqueue name won't be processed > as a format string. > > Signed-off-by: Kees Cook Applied.

Re: [PATCH] qlge: avoid format string exposure in workqueue

From: Kees Cook Date: Wed, 5 Apr 2017 14:39:03 -0700 > While unlikely, this makes sure the workqueue name won't be processed > as a format string. > > Signed-off-by: Kees Cook Applied.

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