Re: Misalignment, MIPS, and ip_hdr(skb)->version

Hi Jason, On 07.12.2016 19:35, Jason A. Donenfeld wrote: > I receive encrypted packets with a 13 byte header. I decrypt the > ciphertext in place, and then discard the header. I then pass the > plaintext to the rest of the networking stack. The plaintext is an IP > packet. Due to the 13 byte

Re: Misalignment, MIPS, and ip_hdr(skb)->version

Hi Jason, On 07.12.2016 19:35, Jason A. Donenfeld wrote: > I receive encrypted packets with a 13 byte header. I decrypt the > ciphertext in place, and then discard the header. I then pass the > plaintext to the rest of the networking stack. The plaintext is an IP > packet. Due to the 13 byte

Re: [PATCH 6/8] staging/lustre: Declare lu_context/session_tags_default

> Make the declaration in a header, not as an extern in a C file, > that is frowned upon. > This also makes sparse a little bit more happy. > Reviewed-by: James Simmons > Signed-off-by: Oleg Drokin > --- >

Re: [PATCH 6/8] staging/lustre: Declare lu_context/session_tags_default

> Make the declaration in a header, not as an extern in a C file, > that is frowned upon. > This also makes sparse a little bit more happy. > Reviewed-by: James Simmons > Signed-off-by: Oleg Drokin > --- > drivers/staging/lustre/lustre/include/lu_object.h | 3 +++ >

Re: [PATCH 8/8] staging/lustre/ptlrpc: Move nrs_conf_fifo extern to a header

> This avoids having an extern definition in a C file which is bad, > and also silences sparse complaint as well. > > Signed-off-by: Oleg Drokin Reviewed-by: James Simmons > --- > drivers/staging/lustre/lustre/ptlrpc/nrs.c | 3 --- >

Re: [PATCH 8/8] staging/lustre/ptlrpc: Move nrs_conf_fifo extern to a header

> This avoids having an extern definition in a C file which is bad, > and also silences sparse complaint as well. > > Signed-off-by: Oleg Drokin Reviewed-by: James Simmons > --- > drivers/staging/lustre/lustre/ptlrpc/nrs.c | 3 --- >

[PATCH] drm/mxsfb: fix pixel clock polarity

The DRM subsystem specifies the pixel clock polarity from a controllers perspective: DRM_BUS_FLAG_PIXDATA_NEGEDGE means the controller drives the data on pixel clocks falling edge. That is the controllers DOTCLK_POL=0 (Default is data launched at negative edge). Also change the data enable logic

[PATCH] drm/mxsfb: fix pixel clock polarity

The DRM subsystem specifies the pixel clock polarity from a controllers perspective: DRM_BUS_FLAG_PIXDATA_NEGEDGE means the controller drives the data on pixel clocks falling edge. That is the controllers DOTCLK_POL=0 (Default is data launched at negative edge). Also change the data enable logic

Re: [PATCH 3/8] staging/lustre/llite: mark ll_io_init() static

> It's not used anywhere out of this file. > Highlighted by sparse. Reviewed-by: James Simmons > Signed-off-by: Oleg Drokin > --- > drivers/staging/lustre/lustre/llite/file.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git

Re: [PATCH 3/8] staging/lustre/llite: mark ll_io_init() static

> It's not used anywhere out of this file. > Highlighted by sparse. Reviewed-by: James Simmons > Signed-off-by: Oleg Drokin > --- > drivers/staging/lustre/lustre/llite/file.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/staging/lustre/lustre/llite/file.c

Re: [PATCH 7/8] staging/lustre: Move lov_read_and_clear_async_rc declaration

> Move it to obd.h, so that it's included from both the users and > the actual definition, making sure they never get out of sync. > This also silences a sparse warning. Reviewed-by: James Simmons > Signed-off-by: Oleg Drokin > --- >

Re: [PATCH 7/8] staging/lustre: Move lov_read_and_clear_async_rc declaration

> Move it to obd.h, so that it's included from both the users and > the actual definition, making sure they never get out of sync. > This also silences a sparse warning. Reviewed-by: James Simmons > Signed-off-by: Oleg Drokin > --- > drivers/staging/lustre/lustre/include/obd.h| 3

Re: [PATCH 4/8] staging/lustre/lov: make lov_lsm_alloc() static

> It's not used anywhere outside of this file. > Highlighted by sparse. Reviewed-by: James Simmons > Signed-off-by: Oleg Drokin > --- > drivers/staging/lustre/lustre/lov/lov_pack.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > >

Re: [PATCH 4/8] staging/lustre/lov: make lov_lsm_alloc() static

> It's not used anywhere outside of this file. > Highlighted by sparse. Reviewed-by: James Simmons > Signed-off-by: Oleg Drokin > --- > drivers/staging/lustre/lustre/lov/lov_pack.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git

Re: [PATCH 1/1] clk: clk-wm831x: fix a logic error

On 12/01, Pan Bian wrote: > Fix bug https://bugzilla.kernel.org/show_bug.cgi?id=188561. Function > wm831x_clkout_is_prepared() returns "true" when it fails to read > CLOCK_CONTROL_1. "true" means the device is already prepared. So > return "true" on the read failure seems improper. > >

Re: [PATCH 1/1] clk: clk-wm831x: fix a logic error

On 12/01, Pan Bian wrote: > Fix bug https://bugzilla.kernel.org/show_bug.cgi?id=188561. Function > wm831x_clkout_is_prepared() returns "true" when it fails to read > CLOCK_CONTROL_1. "true" means the device is already prepared. So > return "true" on the read failure seems improper. > >

Re: [PATCH 5/8] staging/lustre/osc: extern declare osc_caches in a header

> This avoids frowned upon extern in the C file, and also > shuts down a sparse warning of > drivers/staging/lustre/lustre/osc/osc_dev.c:55:22: warning: symbol > 'osc_caches' was not declared. Should it be static? Reviewed-by: James Simmons > Signed-off-by: Oleg

Re: [PATCH 5/8] staging/lustre/osc: extern declare osc_caches in a header

> This avoids frowned upon extern in the C file, and also > shuts down a sparse warning of > drivers/staging/lustre/lustre/osc/osc_dev.c:55:22: warning: symbol > 'osc_caches' was not declared. Should it be static? Reviewed-by: James Simmons > Signed-off-by: Oleg Drokin > --- >

Re: [PATCH] PM: Fix bug in the error handling of async suspend

On Wednesday, December 07, 2016 08:10:32 PM Sahitya Tummala wrote: > If async_suspend is enabled for parent and child devices, then > PM framework has to ensure that parent's async suspend gets called > only after child's async suspend is done. In case if child's async > suspend fails with error,

Re: [PATCH] PM: Fix bug in the error handling of async suspend

On Wednesday, December 07, 2016 08:10:32 PM Sahitya Tummala wrote: > If async_suspend is enabled for parent and child devices, then > PM framework has to ensure that parent's async suspend gets called > only after child's async suspend is done. In case if child's async > suspend fails with error,

Re: [PATCH 5/8] staging/lustre/osc: extern declare osc_caches in a header

> This avoids frowned upon extern in the C file, and also > shuts down a sparse warning of > drivers/staging/lustre/lustre/osc/osc_dev.c:55:22: warning: symbol > 'osc_caches' was not declared. Should it be static? Reviewed-by: James Simmons > Signed-off-by: Oleg

Re: [PATCH 5/8] staging/lustre/osc: extern declare osc_caches in a header

> This avoids frowned upon extern in the C file, and also > shuts down a sparse warning of > drivers/staging/lustre/lustre/osc/osc_dev.c:55:22: warning: symbol > 'osc_caches' was not declared. Should it be static? Reviewed-by: James Simmons > Signed-off-by: Oleg Drokin > --- >

Re: [PATCH 2/8] staging/lustre/ldlm: Correct itree_overlap_cb return type

> As per interval_search() prototype, the callback should return > enum, not int. > This fixes correspondign sparse warning. > > Signed-off-by: Oleg Drokin Reviewed-by: James Simmons > --- > drivers/staging/lustre/lustre/ldlm/ldlm_lock.c | 2 +-

Re: [PATCH 2/8] staging/lustre/ldlm: Correct itree_overlap_cb return type

> As per interval_search() prototype, the callback should return > enum, not int. > This fixes correspondign sparse warning. > > Signed-off-by: Oleg Drokin Reviewed-by: James Simmons > --- > drivers/staging/lustre/lustre/ldlm/ldlm_lock.c | 2 +- > 1 file changed, 1 insertion(+), 1

Re: [PATCH] sd: make ->no_write_same independent of reported ->max_ws_blocks

> "Nicolai" == Nicolai Stange writes: Nicolai, Nicolai> 1.) Do these older SCSI devices have a way to report Nicolai> ->max_ws_blocks? I'm afraid not. Nicolai> 3.) Those older devices that have ->max_ws_blocks > Nicolai> SD_MAX_WS10_BLOCKS but ->ws16 == ->ws10

Re: [PATCH] sd: make ->no_write_same independent of reported ->max_ws_blocks

> "Nicolai" == Nicolai Stange writes: Nicolai, Nicolai> 1.) Do these older SCSI devices have a way to report Nicolai> ->max_ws_blocks? I'm afraid not. Nicolai> 3.) Those older devices that have ->max_ws_blocks > Nicolai> SD_MAX_WS10_BLOCKS but ->ws16 == ->ws10 == 0, i.e. the

Re: [PATCH v3 1/2] clk: uniphier: add CPU-gear change (cpufreq) support

On 12/07, Masahiro Yamada wrote: > Core support code for CPU frequency changes, which will be used by > the generic cpufreq driver. > > The register view is different from the generic clk-mux; it has > a separate status register, and an update bit to load the register > setting. > >

Re: [PATCH 1/1] cpuidle: fix improper return value on error

On Saturday, December 03, 2016 11:02:27 PM Pan Bian wrote: > From: Pan Bian > > In function cpuidle_add_state_sysfs(), variable ret takes the return > value. Its value should be negative on errors. Because ret is reset in > the loop, its value will be 0 during the second and

Re: [PATCH v3 1/2] clk: uniphier: add CPU-gear change (cpufreq) support

On 12/07, Masahiro Yamada wrote: > Core support code for CPU frequency changes, which will be used by > the generic cpufreq driver. > > The register view is different from the generic clk-mux; it has > a separate status register, and an update bit to load the register > setting. > >

Re: [PATCH 1/1] cpuidle: fix improper return value on error

On Saturday, December 03, 2016 11:02:27 PM Pan Bian wrote: > From: Pan Bian > > In function cpuidle_add_state_sysfs(), variable ret takes the return > value. Its value should be negative on errors. Because ret is reset in > the loop, its value will be 0 during the second and after repeat of the

Re: [PATCH v3 2/2] clk: uniphier: add cpufreq data for LD11, LD20 SoCs

On 12/07, Masahiro Yamada wrote: > Add more data to 64bit SoCs for the cpufreq support. > > Signed-off-by: Masahiro Yamada > --- Applied to clk-next -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project

Re: [PATCH v3 2/2] clk: uniphier: add cpufreq data for LD11, LD20 SoCs

On 12/07, Masahiro Yamada wrote: > Add more data to 64bit SoCs for the cpufreq support. > > Signed-off-by: Masahiro Yamada > --- Applied to clk-next -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project

Re: [PATCH 2/8] staging/lustre/ldlm: Correct itree_overlap_cb return type

> As per interval_search() prototype, the callback should return > enum, not int. > This fixes correspondign sparse warning. > > Signed-off-by: Oleg Drokin Reviewed-by: James Simmons > --- > drivers/staging/lustre/lustre/ldlm/ldlm_lock.c | 2 +-

Re: [PATCH 2/8] staging/lustre/ldlm: Correct itree_overlap_cb return type

> As per interval_search() prototype, the callback should return > enum, not int. > This fixes correspondign sparse warning. > > Signed-off-by: Oleg Drokin Reviewed-by: James Simmons > --- > drivers/staging/lustre/lustre/ldlm/ldlm_lock.c | 2 +- > 1 file changed, 1 insertion(+), 1

Re: [PATCH] PM / wakeirq: Fix dedicated wakeirq for drivers not using autosuspend

On Monday, December 05, 2016 04:38:16 PM Tony Lindgren wrote: > I noticed some wakeirq flakeyness with consumer drivers not using > autosuspend. For drivers not using autosuspend, the wakeirq may never > get unmasked in rpm_suspend() because of irq desc->depth. > > We are configuring dedicated

Re: [PATCH] PM / wakeirq: Fix dedicated wakeirq for drivers not using autosuspend

On Monday, December 05, 2016 04:38:16 PM Tony Lindgren wrote: > I noticed some wakeirq flakeyness with consumer drivers not using > autosuspend. For drivers not using autosuspend, the wakeirq may never > get unmasked in rpm_suspend() because of irq desc->depth. > > We are configuring dedicated

linux-next: manual merge of the sunxi tree with the arm-soc tree

Hi Maxime, Today's linux-next merge of the sunxi tree got a conflict in: arch/arm/boot/dts/sun8i-h3.dtsi between commit: 4367c1d84655 ("dts: sun8i-h3: correct UART3 pin definitions") from the arm-soc tree and commits: acac77949d26 ("ARM: sunxi: Remove useless allwinner,drive property")

Re: [PATCH v4] x86/suspend: fix false positive KASAN warning on suspend/resume

On Friday, December 02, 2016 11:42:21 AM Josh Poimboeuf wrote: > Resuming from a suspend operation is showing a KASAN false positive > warning: > > BUG: KASAN: stack-out-of-bounds in unwind_get_return_address+0x11d/0x130 at > addr 8803867d7878 > Read of size 8 by task pm-suspend/7774 >

linux-next: manual merge of the sunxi tree with the arm-soc tree

Hi Maxime, Today's linux-next merge of the sunxi tree got a conflict in: arch/arm/boot/dts/sun8i-h3.dtsi between commit: 4367c1d84655 ("dts: sun8i-h3: correct UART3 pin definitions") from the arm-soc tree and commits: acac77949d26 ("ARM: sunxi: Remove useless allwinner,drive property")

Re: [PATCH v4] x86/suspend: fix false positive KASAN warning on suspend/resume

On Friday, December 02, 2016 11:42:21 AM Josh Poimboeuf wrote: > Resuming from a suspend operation is showing a KASAN false positive > warning: > > BUG: KASAN: stack-out-of-bounds in unwind_get_return_address+0x11d/0x130 at > addr 8803867d7878 > Read of size 8 by task pm-suspend/7774 >

اپليكيشن رايگان

برخی امکانات و قابلیت های این اپلیکیشن: امکان خرید آنلاین و آفلاین خرید آسان کارت شارژ های ایرانسل، همراه اول، تالیا و رایتل وارد کردن رمز شارژ فقط با یک کلیک امکان شارژ اتوماتیک (تاپ آپ) خرید گیفت کارت های گوگل پلی، آیتونز، مایکروسافت و ... خرید آنتی ویروس خرید بسته اینترنت ایرانسل پرداخت قبوض

اپليكيشن رايگان

برخی امکانات و قابلیت های این اپلیکیشن: امکان خرید آنلاین و آفلاین خرید آسان کارت شارژ های ایرانسل، همراه اول، تالیا و رایتل وارد کردن رمز شارژ فقط با یک کلیک امکان شارژ اتوماتیک (تاپ آپ) خرید گیفت کارت های گوگل پلی، آیتونز، مایکروسافت و ... خرید آنتی ویروس خرید بسته اینترنت ایرانسل پرداخت قبوض

Re: Note on 4.10 merge window timing (was Re: Linux 4.9-rc8)

On Wed, Dec 07, 2016 at 10:32:47AM -0800, Linus Torvalds wrote: > Btw, for anybody with a calendar (or just excellent finger counting > skills), this should all be obvious, but I thought I'd make it very > explicit anyway: this means that 4.9 will be released this upcoming > Sunday, December

Re: Note on 4.10 merge window timing (was Re: Linux 4.9-rc8)

On Wed, Dec 07, 2016 at 10:32:47AM -0800, Linus Torvalds wrote: > Btw, for anybody with a calendar (or just excellent finger counting > skills), this should all be obvious, but I thought I'd make it very > explicit anyway: this means that 4.9 will be released this upcoming > Sunday, December

[GIT PULL] gcc-plugins updates for v4.10-rc1

Hi, Please pull these gcc-plugins changes for v4.10-rc1. Thanks! -Kees The following changes since commit 07d9a380680d1c0eb51ef87ff2eab5c994949e69: Linux 4.9-rc2 (2016-10-23 17:10:14 -0700) are available in the git repository at:

[GIT PULL] gcc-plugins updates for v4.10-rc1

Hi, Please pull these gcc-plugins changes for v4.10-rc1. Thanks! -Kees The following changes since commit 07d9a380680d1c0eb51ef87ff2eab5c994949e69: Linux 4.9-rc2 (2016-10-23 17:10:14 -0700) are available in the git repository at:

Re: linux-next: Tree for Dec 7 (kallsyms failure)

Hi Randy, On Wed, 7 Dec 2016 15:42:32 -0800 Randy Dunlap wrote: > > I started seeing this yesterday (2016-1206). > This is on x86_64. > > Anybody know about it? > > kallsyms failure: relative symbol value 0x8100 out of range in > relative mode I got a

Re: linux-next: Tree for Dec 7 (kallsyms failure)

Hi Randy, On Wed, 7 Dec 2016 15:42:32 -0800 Randy Dunlap wrote: > > I started seeing this yesterday (2016-1206). > This is on x86_64. > > Anybody know about it? > > kallsyms failure: relative symbol value 0x8100 out of range in > relative mode I got a similar failure starting a

Re: [PATCH 3/3] pciehp: Fix race condition handling surprise link-down

On Wed, Dec 07, 2016 at 05:40:54PM -0600, Bjorn Helgaas wrote: > On Sat, Nov 19, 2016 at 12:32:47AM -0800, Ashok Raj wrote: > > --- a/drivers/pci/hotplug/pciehp_ctrl.c > > +++ b/drivers/pci/hotplug/pciehp_ctrl.c > > @@ -182,6 +182,7 @@ static void pciehp_power_thread(struct work_struct > > *work)

Re: [PATCH 3/3] pciehp: Fix race condition handling surprise link-down

On Wed, Dec 07, 2016 at 05:40:54PM -0600, Bjorn Helgaas wrote: > On Sat, Nov 19, 2016 at 12:32:47AM -0800, Ashok Raj wrote: > > --- a/drivers/pci/hotplug/pciehp_ctrl.c > > +++ b/drivers/pci/hotplug/pciehp_ctrl.c > > @@ -182,6 +182,7 @@ static void pciehp_power_thread(struct work_struct > > *work)

Re: [PATCHv13,1/3] lib/string: add sysfs_match_string helper

On Thu, Nov 24, 2016 at 02:21:42PM +0200, Heikki Krogerus wrote: > Make a simple helper for matching strings with sysfs > attribute files. In most parts the same as match_string(), > except sysfs_match_string() uses sysfs_streq() instead of > strcmp() for matching. This is more convenient when

Re: [PATCHv13,1/3] lib/string: add sysfs_match_string helper

On Thu, Nov 24, 2016 at 02:21:42PM +0200, Heikki Krogerus wrote: > Make a simple helper for matching strings with sysfs > attribute files. In most parts the same as match_string(), > except sysfs_match_string() uses sysfs_streq() instead of > strcmp() for matching. This is more convenient when

Re: [PATCH] MAINTAINERS: clarify that "B:" is the URI where to file bugs

On Wednesday, December 07, 2016 10:35:07 AM Jani Nikula wrote: > On Wed, 07 Dec 2016, "Rafael J. Wysocki" wrote: > > On Monday, December 05, 2016 02:03:59 PM Jani Nikula wrote: > >> Different subsystems and drivers have different preferences for where to > >> file bugs and

Re: [PATCH] MAINTAINERS: clarify that "B:" is the URI where to file bugs

On Wednesday, December 07, 2016 10:35:07 AM Jani Nikula wrote: > On Wed, 07 Dec 2016, "Rafael J. Wysocki" wrote: > > On Monday, December 05, 2016 02:03:59 PM Jani Nikula wrote: > >> Different subsystems and drivers have different preferences for where to > >> file bugs and what information to

Re: [PATCH 0/8] Sparse warning fixes in Lustre.

On Wed, Dec 07, 2016 at 05:41:26PM -0500, Oleg Drokin wrote: > This set of fixes aims at sparse warnings. Speaking of the stuff sparse catches there: class_process_proc_param(). I've tried to describe what I think of that Fine Piece Of Software several times, but I had to give up - my command of

Re: [PATCH 0/8] Sparse warning fixes in Lustre.

On Wed, Dec 07, 2016 at 05:41:26PM -0500, Oleg Drokin wrote: > This set of fixes aims at sparse warnings. Speaking of the stuff sparse catches there: class_process_proc_param(). I've tried to describe what I think of that Fine Piece Of Software several times, but I had to give up - my command of

Re: linux-next: Tree for Dec 7 (kallsyms failure)

On 12/06/16 22:24, Stephen Rothwell wrote: > Hi all, > > Changes since 20161206: > > The powerpc allyesconfig build fails for this release. > > The pinctrl tree still had its build failure so I used the version from > next-20161202. > > The sound-asoc tree lost its build failure. > > The tip

Re: linux-next: Tree for Dec 7 (kallsyms failure)

On 12/06/16 22:24, Stephen Rothwell wrote: > Hi all, > > Changes since 20161206: > > The powerpc allyesconfig build fails for this release. > > The pinctrl tree still had its build failure so I used the version from > next-20161202. > > The sound-asoc tree lost its build failure. > > The tip

Re: [PATCH 2/2] net: ethernet: stmmac: remove private tx queue lock

From: Pavel Machek Date: Wed, 7 Dec 2016 22:37:57 +0100 > diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c > b/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c > index 982c952..7415bc2 100644 > --- a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c > +++

Re: [PATCH 2/2] net: ethernet: stmmac: remove private tx queue lock

From: Pavel Machek Date: Wed, 7 Dec 2016 22:37:57 +0100 > diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c > b/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c > index 982c952..7415bc2 100644 > --- a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c > +++

Re: [PATCH 3/3] pciehp: Fix race condition handling surprise link-down

On Sat, Nov 19, 2016 at 12:32:47AM -0800, Ashok Raj wrote: > A surprise link down may retrain very quickly, causing the same slot to > generate a link up event before handling the link down completes. > > Since the link is active, the power off work queued from the first link > down will cause a

Re: [PATCH 3/3] pciehp: Fix race condition handling surprise link-down

On Sat, Nov 19, 2016 at 12:32:47AM -0800, Ashok Raj wrote: > A surprise link down may retrain very quickly, causing the same slot to > generate a link up event before handling the link down completes. > > Since the link is active, the power off work queued from the first link > down will cause a

[PATCH] staging: fsl-mc: add sysfs ABI doc

define the bind/unbind sysfs interfaces for the fsl-mc bus Signed-off-by: Stuart Yoder --- Documentation/ABI/testing/sysfs-bus-fsl-mc | 21 + 1 file changed, 21 insertions(+) create mode 100644 Documentation/ABI/testing/sysfs-bus-fsl-mc diff --git

[PATCH] staging: fsl-mc: remove unnecessary info prints from bus driver

remove pr_info/dev_info prints that add unnecessary verbosity Signed-off-by: Stuart Yoder --- drivers/staging/fsl-mc/bus/fsl-mc-bus.c | 6 -- 1 file changed, 6 deletions(-) diff --git a/drivers/staging/fsl-mc/bus/fsl-mc-bus.c b/drivers/staging/fsl-mc/bus/fsl-mc-bus.c

[PATCH] staging: fsl-mc: add sysfs ABI doc

define the bind/unbind sysfs interfaces for the fsl-mc bus Signed-off-by: Stuart Yoder --- Documentation/ABI/testing/sysfs-bus-fsl-mc | 21 + 1 file changed, 21 insertions(+) create mode 100644 Documentation/ABI/testing/sysfs-bus-fsl-mc diff --git

[PATCH] staging: fsl-mc: remove unnecessary info prints from bus driver

remove pr_info/dev_info prints that add unnecessary verbosity Signed-off-by: Stuart Yoder --- drivers/staging/fsl-mc/bus/fsl-mc-bus.c | 6 -- 1 file changed, 6 deletions(-) diff --git a/drivers/staging/fsl-mc/bus/fsl-mc-bus.c b/drivers/staging/fsl-mc/bus/fsl-mc-bus.c index

[GIT PULL] pstore updates for v4.10-rc1

Hi, As requested, here's an early pull request for v4.10. :) Please pull these pstore changes for v4.10-rc1. Thanks! -Kees The following changes since commit 07d9a380680d1c0eb51ef87ff2eab5c994949e69: Linux 4.9-rc2 (2016-10-23 17:10:14 -0700) are available in the git repository at:

[GIT PULL] pstore updates for v4.10-rc1

Hi, As requested, here's an early pull request for v4.10. :) Please pull these pstore changes for v4.10-rc1. Thanks! -Kees The following changes since commit 07d9a380680d1c0eb51ef87ff2eab5c994949e69: Linux 4.9-rc2 (2016-10-23 17:10:14 -0700) are available in the git repository at:

Re: [PATCH 08/16] drivers/fsi: Add crc4 helpers

Hi Greg, > Why not just create lib/crc4.c with these functions, like the other crc > functions in the kernel? Two (bad) reasons: - The crc4 implementation here is pretty specific to the FSI usage (only supporting 4-bit-sized chunks), to keep the math & lookup table simple - I'm lazy

Re: [PATCH 08/16] drivers/fsi: Add crc4 helpers

Hi Greg, > Why not just create lib/crc4.c with these functions, like the other crc > functions in the kernel? Two (bad) reasons: - The crc4 implementation here is pretty specific to the FSI usage (only supporting 4-bit-sized chunks), to keep the math & lookup table simple - I'm lazy

Re: [PATCH v8 8/8] cpufreq: intel_pstate: Use CPPC to get max performance

On Wednesday, December 07, 2016 03:12:53 PM Tim Chen wrote: > On Wed, 2016-12-07 at 20:06 +0100, Sebastian Andrzej Siewior wrote: > > > > > > Signed-off-by: Sebastian Andrzej Siewior > > --- > > drivers/acpi/cppc_acpi.c | 3 +++ > > 1 file changed, 3 insertions(+) > > >

Re: [PATCH v8 8/8] cpufreq: intel_pstate: Use CPPC to get max performance

On Wednesday, December 07, 2016 03:12:53 PM Tim Chen wrote: > On Wed, 2016-12-07 at 20:06 +0100, Sebastian Andrzej Siewior wrote: > > > > > > Signed-off-by: Sebastian Andrzej Siewior > > --- > > drivers/acpi/cppc_acpi.c | 3 +++ > > 1 file changed, 3 insertions(+) > > > > diff --git

Re: [PATCH 0/3] Fix improper handling of pcie hotplug events.

Hi Ashok, On Sat, Nov 19, 2016 at 12:32:44AM -0800, Ashok Raj wrote: > This patch series fixes pciehp for certain special conditions observed during > testing. > > Ashok Raj (3): > pciehp: Prioritize data-link event over presence detect > pciehp: Fix led status when enabling already enabled

Re: [PATCH 0/3] Fix improper handling of pcie hotplug events.

Hi Ashok, On Sat, Nov 19, 2016 at 12:32:44AM -0800, Ashok Raj wrote: > This patch series fixes pciehp for certain special conditions observed during > testing. > > Ashok Raj (3): > pciehp: Prioritize data-link event over presence detect > pciehp: Fix led status when enabling already enabled

Re: [PATCH 05/16] drivers/fsi: Add fake master driver

Hi Mark & Chris, > On Tue, Dec 06, 2016 at 06:14:26PM -0600, Chris Bostic wrote: >> From: Jeremy Kerr >> >> For debugging, add a fake master driver, that only supports reads, >> returning a fixed set of data. > >> +config FSI_MASTER_FAKE >> +tristate "Fake FSI master" >> +

Re: [PATCH] Revert "PM / OPP: Don't assume platform doesn't have regulators"

On Wed, Dec 7, 2016 at 11:31 AM, Viresh Kumar wrote: > This reverts commit ef3caabee9691386e6801ea92150e37277db9c7a. > > The commit was based on the assumption that a platform with voltages > specified with individual OPPs, would have registered a regulator as > well in

Re: [PATCH 05/16] drivers/fsi: Add fake master driver

Hi Mark & Chris, > On Tue, Dec 06, 2016 at 06:14:26PM -0600, Chris Bostic wrote: >> From: Jeremy Kerr >> >> For debugging, add a fake master driver, that only supports reads, >> returning a fixed set of data. > >> +config FSI_MASTER_FAKE >> +tristate "Fake FSI master" >> +depends on FSI

Re: [PATCH] Revert "PM / OPP: Don't assume platform doesn't have regulators"

On Wed, Dec 7, 2016 at 11:31 AM, Viresh Kumar wrote: > This reverts commit ef3caabee9691386e6801ea92150e37277db9c7a. > > The commit was based on the assumption that a platform with voltages > specified with individual OPPs, would have registered a regulator as > well in order to do full DVFS. > >

[PATCH v2 2/6] rtc: mcp795: fix bitmask value for leap year (LP).

According the datasheet the leap year is a fifth bit in month register. Signed-off-by: Emil Bartczak --- drivers/rtc/rtc-mcp795.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/rtc/rtc-mcp795.c b/drivers/rtc/rtc-mcp795.c index 0389ee0..5fbdb4c

[PATCH v2 5/6] rtc: mcp795: Prefer using the BIT() macro.

This patch doesn't change the code but replaces all bitmask values with the BIT(x) macro. Signed-off-by: Emil Bartczak --- drivers/rtc/rtc-mcp795.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/rtc/rtc-mcp795.c b/drivers/rtc/rtc-mcp795.c

[PATCH v2 6/6] rtc: mcp795: Fix whitespace and indentation.

Fix whitespace and indentation errors and the following checkpatch warnings: - line 15: Block comments use a trailing */ on a separate line - line 256: Line over 80 characters No code change. Signed-off-by: Emil Bartczak --- drivers/rtc/rtc-mcp795.c | 12 ++-- 1 file

[PATCH v2 2/6] rtc: mcp795: fix bitmask value for leap year (LP).

According the datasheet the leap year is a fifth bit in month register. Signed-off-by: Emil Bartczak --- drivers/rtc/rtc-mcp795.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/rtc/rtc-mcp795.c b/drivers/rtc/rtc-mcp795.c index 0389ee0..5fbdb4c 100644 ---

[PATCH v2 5/6] rtc: mcp795: Prefer using the BIT() macro.

This patch doesn't change the code but replaces all bitmask values with the BIT(x) macro. Signed-off-by: Emil Bartczak --- drivers/rtc/rtc-mcp795.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/rtc/rtc-mcp795.c b/drivers/rtc/rtc-mcp795.c index 89b0ffa..8ed55f6

[PATCH v2 6/6] rtc: mcp795: Fix whitespace and indentation.

Fix whitespace and indentation errors and the following checkpatch warnings: - line 15: Block comments use a trailing */ on a separate line - line 256: Line over 80 characters No code change. Signed-off-by: Emil Bartczak --- drivers/rtc/rtc-mcp795.c | 12 ++-- 1 file changed, 6

[PATCH v2 3/6] rtc: mcp795: fix time range difference between linux and RTC chip.

In linux rtc_time struct, tm_mon range is 0~11, while in RTC HW REG, month range is 1~12. This patch adjusts difference of them. Signed-off-by: Emil Bartczak --- drivers/rtc/rtc-mcp795.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH v2 3/6] rtc: mcp795: fix time range difference between linux and RTC chip.

In linux rtc_time struct, tm_mon range is 0~11, while in RTC HW REG, month range is 1~12. This patch adjusts difference of them. Signed-off-by: Emil Bartczak --- drivers/rtc/rtc-mcp795.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/rtc/rtc-mcp795.c

[PATCH v2 4/6] rtc: mcp795: fix month write resetting date to 1.

According to Microchip errata some combinations of date and month values may result in the date being reset to 1, even if the date is also written with the month (for example 31-07 or 31-08). As a workaround avoid writing date and month values within the same Write command. Instead, terminate the

[PATCH v2 0/6] Provides bug fixes for rtc-mcp795.c

This patchset provides 4 bug fixes (patch 1, 2, 3, 4), one improvement (patch 5) and whitespace, indention errors fixes (patch 6) in the file driver/rtc/rtc-mcp795.c. Please review the changes and consider to apply them to the main kernel tree. Changes from v1: - Introduced SoB to all patches.

[PATCH v2 1/6] rtc: mcp795: use bcd2bin/bin2bcd.

Change rtc-mcp795.c to use the bcd2bin/bin2bcd functions. This change fixes the wrong conversion of month value from binary to BCD (missing right shift operation for 10 month). Signed-off-by: Emil Bartczak --- drivers/rtc/rtc-mcp795.c | 25 + 1 file

[PATCH v2 4/6] rtc: mcp795: fix month write resetting date to 1.

According to Microchip errata some combinations of date and month values may result in the date being reset to 1, even if the date is also written with the month (for example 31-07 or 31-08). As a workaround avoid writing date and month values within the same Write command. Instead, terminate the

[PATCH v2 0/6] Provides bug fixes for rtc-mcp795.c

This patchset provides 4 bug fixes (patch 1, 2, 3, 4), one improvement (patch 5) and whitespace, indention errors fixes (patch 6) in the file driver/rtc/rtc-mcp795.c. Please review the changes and consider to apply them to the main kernel tree. Changes from v1: - Introduced SoB to all patches.

[PATCH v2 1/6] rtc: mcp795: use bcd2bin/bin2bcd.

Change rtc-mcp795.c to use the bcd2bin/bin2bcd functions. This change fixes the wrong conversion of month value from binary to BCD (missing right shift operation for 10 month). Signed-off-by: Emil Bartczak --- drivers/rtc/rtc-mcp795.c | 25 + 1 file changed, 13

Re: [PATCH 18/22] m68k/mm: kmap - Modernize printing of kernel messages

On Wed, 7 Dec 2016, Geert Uytterhoeven wrote: > - Convert from printk() to pr_*(), > - Add missing continuations, > - Remove #undef DEBUG. > > Note that "#ifdef DEBUG" is sometimes retained because pr_cont() is not > optimized away when debugging is disabled. > I think that argues for

Re: [PATCH 18/22] m68k/mm: kmap - Modernize printing of kernel messages

On Wed, 7 Dec 2016, Geert Uytterhoeven wrote: > - Convert from printk() to pr_*(), > - Add missing continuations, > - Remove #undef DEBUG. > > Note that "#ifdef DEBUG" is sometimes retained because pr_cont() is not > optimized away when debugging is disabled. > I think that argues for

Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v7

On Wed, Dec 07, 2016 at 09:19:58PM +, Mel Gorman wrote: > At small packet sizes on localhost, I see relatively low page allocator > activity except during the socket setup and other unrelated activity > (khugepaged, irqbalance, some btrfs stuff) which is curious as it's > less clear why the

Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v7

On Wed, Dec 07, 2016 at 09:19:58PM +, Mel Gorman wrote: > At small packet sizes on localhost, I see relatively low page allocator > activity except during the socket setup and other unrelated activity > (khugepaged, irqbalance, some btrfs stuff) which is curious as it's > less clear why the

Re: [PATCH 2/2] net: ethernet: stmmac: remove private tx queue lock

On Wed 2016-12-07 23:34:19, Lino Sanfilippo wrote: > On 07.12.2016 22:43, Lino Sanfilippo wrote: > > Hi Pavel, > > > > On 07.12.2016 22:37, Pavel Machek wrote: > >> On Wed 2016-12-07 21:05:38, Lino Sanfilippo wrote: > >>> The driver uses a private lock for synchronization between the xmit > >>>

Re: [PATCH 2/2] net: ethernet: stmmac: remove private tx queue lock

On Wed 2016-12-07 23:34:19, Lino Sanfilippo wrote: > On 07.12.2016 22:43, Lino Sanfilippo wrote: > > Hi Pavel, > > > > On 07.12.2016 22:37, Pavel Machek wrote: > >> On Wed 2016-12-07 21:05:38, Lino Sanfilippo wrote: > >>> The driver uses a private lock for synchronization between the xmit > >>>

Re: [PATCH 11/22] m68k/mac: Modernize printing of kernel messages

On Wed, 7 Dec 2016, Geert Uytterhoeven wrote: > Convert from printk() to pr_*(). > > Signed-off-by: Geert Uytterhoeven > --- > arch/m68k/mac/config.c | 34 -- > arch/m68k/mac/misc.c | 8 > 2 files changed, 20 insertions(+), 22

Re: [PATCH 11/22] m68k/mac: Modernize printing of kernel messages

On Wed, 7 Dec 2016, Geert Uytterhoeven wrote: > Convert from printk() to pr_*(). > > Signed-off-by: Geert Uytterhoeven > --- > arch/m68k/mac/config.c | 34 -- > arch/m68k/mac/misc.c | 8 > 2 files changed, 20 insertions(+), 22 deletions(-) > > diff

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