Re: [PATCH 2/5] zram: partial IO refactoring

Hi! On 04/03/2017 08:17 AM, Minchan Kim wrote: > For architecture(PAGE_SIZE > 4K), zram have supported partial IO. > However, the mixed code for handling normal/partial IO is too mess, > error-prone to modify IO handler functions with upcoming feature > so this patch aims for cleaning up zram's

Re: [PATCH 2/5] zram: partial IO refactoring

Hi! On 04/03/2017 08:17 AM, Minchan Kim wrote: > For architecture(PAGE_SIZE > 4K), zram have supported partial IO. > However, the mixed code for handling normal/partial IO is too mess, > error-prone to modify IO handler functions with upcoming feature > so this patch aims for cleaning up zram's

Re: [RFC] mm/crypto: add tunable compression algorithm for zswap

On Sat, Apr 01, 2017 at 11:18:13PM +0200, Vlastimil Babka wrote: > Zswap (and zram) save memory by compressing pages instead of swapping them > out. This is nice, but with traditional compression algorithms such as LZO, > one cannot know, how well the data will compress, so the overal savings are

Re: [RFC] mm/crypto: add tunable compression algorithm for zswap

On Sat, Apr 01, 2017 at 11:18:13PM +0200, Vlastimil Babka wrote: > Zswap (and zram) save memory by compressing pages instead of swapping them > out. This is nice, but with traditional compression algorithms such as LZO, > one cannot know, how well the data will compress, so the overal savings are

Re: [PATCH] dwc2: gadget: Fix in control write transfers

Hi, On 3/30/2017 2:42 PM, Felipe Balbi wrote: > > Hi, > > Minas Harutyunyan writes: >> After data out stage gadget driver should not initate ZLP on control EP, >> because it is up to function driver. > > not true always, depends on return value from ->setup().

Re: [PATCH] dwc2: gadget: Fix in control write transfers

Hi, On 3/30/2017 2:42 PM, Felipe Balbi wrote: > > Hi, > > Minas Harutyunyan writes: >> After data out stage gadget driver should not initate ZLP on control EP, >> because it is up to function driver. > > not true always, depends on return value from ->setup(). Which problem > did you have? Which

Re: [PATCH v2 3/4] usb: dwc3: add dual-role support

On 03/30/2017 02:27 AM, Felipe Balbi wrote: > > Hi > > Roger Quadros writes: > For something that simple, we wouldn't even need to use OTG FSM layer > because that brings no benefit for such a simple requirement. no no. I think you got it wrong. I'm not using the

Re: [PATCH v2 3/4] usb: dwc3: add dual-role support

On 03/30/2017 02:27 AM, Felipe Balbi wrote: > > Hi > > Roger Quadros writes: > For something that simple, we wouldn't even need to use OTG FSM layer > because that brings no benefit for such a simple requirement. no no. I think you got it wrong. I'm not using the OTG FSM layer

[PATCH v2 1/2] regulator: hi655x: Describe consumed platform device

The hi655x-regulator driver consumes a similarly named platform device. Adding that to the module device table, allows modprobe to locate this driver once the device is created. Signed-off-by: Jeremy Linton --- drivers/regulator/hi655x-regulator.c | 7 +++ 1 file

[PATCH v2 1/2] regulator: hi655x: Describe consumed platform device

The hi655x-regulator driver consumes a similarly named platform device. Adding that to the module device table, allows modprobe to locate this driver once the device is created. Signed-off-by: Jeremy Linton --- drivers/regulator/hi655x-regulator.c | 7 +++ 1 file changed, 7 insertions(+)

[PATCH v2 2/2] regulator: hi655x: Bump parent pmic module use count

The hi655x-regulator driver depends on the parent pmic/mfc device driver but doesn't increase its use count. This results in system crashes if the parent module is unloaded while the regulators are still in use. Add explicit module get/put calls to keep the parent from being unloaded. example

[PATCH v2 0/2] Hi655x: mfd/pmic: regulator: Correct dependencies

In an environment where the hi655x pmic is being built as a standalone module, it fails to automatically load resulting in boot failures, machine hangs, etc. First we correct this by setting an appropriate module dependency. Then we bump the module use count on the mfd/pmic driver so that it

[PATCH v2 0/2] Hi655x: mfd/pmic: regulator: Correct dependencies

In an environment where the hi655x pmic is being built as a standalone module, it fails to automatically load resulting in boot failures, machine hangs, etc. First we correct this by setting an appropriate module dependency. Then we bump the module use count on the mfd/pmic driver so that it

[PATCH v2 2/2] regulator: hi655x: Bump parent pmic module use count

The hi655x-regulator driver depends on the parent pmic/mfc device driver but doesn't increase its use count. This results in system crashes if the parent module is unloaded while the regulators are still in use. Add explicit module get/put calls to keep the parent from being unloaded. example

Re: dwc2_hc_chhltd_intr_dma - ChHltd set errors?

On 03/31/2017 04:04 PM, John Stultz wrote: > On Thu, Mar 2, 2017 at 12:00 PM, John Stultz wrote: >> Hey John, >> We've noticed that when using usb ethernet adapters on HiKey, we >> occasionally see errors like: >> >> dwc2 f72c.usb: dwc2_hc_chhltd_intr_dma: Channel 0

Re: dwc2_hc_chhltd_intr_dma - ChHltd set errors?

On 03/31/2017 04:04 PM, John Stultz wrote: > On Thu, Mar 2, 2017 at 12:00 PM, John Stultz wrote: >> Hey John, >> We've noticed that when using usb ethernet adapters on HiKey, we >> occasionally see errors like: >> >> dwc2 f72c.usb: dwc2_hc_chhltd_intr_dma: Channel 0 - ChHltd set, >> but

Re: [PATCH RFC] remove custom Michael MIC implementation

+ linux-wireless "Tobin C. Harding" writes: > On Fri, Mar 31, 2017 at 09:58:51AM +0200, Wolfram Sang wrote: >> >> > The code is untested, I have hardware in the mail. >> >> Cool! > > The card I have is a Spectec FCC ID: S2Y-WLAN-11B-G which I believe is > a SDW-823 and should

Re: [PATCH RFC] remove custom Michael MIC implementation

+ linux-wireless "Tobin C. Harding" writes: > On Fri, Mar 31, 2017 at 09:58:51AM +0200, Wolfram Sang wrote: >> >> > The code is untested, I have hardware in the mail. >> >> Cool! > > The card I have is a Spectec FCC ID: S2Y-WLAN-11B-G which I believe is > a SDW-823 and should use the ks7010

[PATCH 0/5] zram clean up

This patchset aims zram clean-up. [1] clean up multiple pages's bvec handling. [2] clean up partial IO handling [3-5] clean up zram via using accessor and removing pointless structure. With [2-5] applied, we can get a few hundred bytes as well as huge readibility enhance. This patchset is based

Re: [PATCH] nios2: reserve boot memory for device tree

On Fri, 2017-03-31 at 11:40 +0200, Tobias Klauser wrote: > Make sure to reserve the boot memory for the flattened device tree. > Otherwise it might get overwritten, e.g. when initial_boot_params is > copied, leading to a corrupted FDT and a boot hang/crash: > >   bootconsole [early0] enabled >  

[PATCH 0/5] zram clean up

This patchset aims zram clean-up. [1] clean up multiple pages's bvec handling. [2] clean up partial IO handling [3-5] clean up zram via using accessor and removing pointless structure. With [2-5] applied, we can get a few hundred bytes as well as huge readibility enhance. This patchset is based

Re: [PATCH] nios2: reserve boot memory for device tree

On Fri, 2017-03-31 at 11:40 +0200, Tobias Klauser wrote: > Make sure to reserve the boot memory for the flattened device tree. > Otherwise it might get overwritten, e.g. when initial_boot_params is > copied, leading to a corrupted FDT and a boot hang/crash: > >   bootconsole [early0] enabled >  

[PATCH 3/5] zram: use zram_slot_lock instead of raw bit_spin_lock op

With this clean-up phase, I want to use zram's wrapper function to lock table access which is more consistent with other zram's functions. Signed-off-by: Minchan Kim --- drivers/block/zram/zram_drv.c | 42 -- 1 file changed, 28

[PATCH 3/5] zram: use zram_slot_lock instead of raw bit_spin_lock op

With this clean-up phase, I want to use zram's wrapper function to lock table access which is more consistent with other zram's functions. Signed-off-by: Minchan Kim --- drivers/block/zram/zram_drv.c | 42 -- 1 file changed, 28 insertions(+), 14

[PATCH 1/5] zram: handle multiple pages attached bio's bvec

Johannes Thumshirn reported system goes the panic when using NVMe over Fabrics loopback target with zram. The reason is zram expects each bvec in bio contains a single page but nvme can attach a huge bulk of pages attached to the bio's bvec so that zram's index arithmetic could be wrong so that

[PATCH 4/5] zram: remove zram_meta structure

It's redundant now. Instead, remove it and use zram structure directly. Signed-off-by: Minchan Kim --- drivers/block/zram/zram_drv.c | 163 +- drivers/block/zram/zram_drv.h | 6 +- 2 files changed, 65 insertions(+), 104 deletions(-)

[PATCH 2/5] zram: partial IO refactoring

For architecture(PAGE_SIZE > 4K), zram have supported partial IO. However, the mixed code for handling normal/partial IO is too mess, error-prone to modify IO handler functions with upcoming feature so this patch aims for cleaning up zram's IO handling functions. Signed-off-by: Minchan Kim

[PATCH 1/5] zram: handle multiple pages attached bio's bvec

Johannes Thumshirn reported system goes the panic when using NVMe over Fabrics loopback target with zram. The reason is zram expects each bvec in bio contains a single page but nvme can attach a huge bulk of pages attached to the bio's bvec so that zram's index arithmetic could be wrong so that

[PATCH 4/5] zram: remove zram_meta structure

It's redundant now. Instead, remove it and use zram structure directly. Signed-off-by: Minchan Kim --- drivers/block/zram/zram_drv.c | 163 +- drivers/block/zram/zram_drv.h | 6 +- 2 files changed, 65 insertions(+), 104 deletions(-) diff --git

[PATCH 2/5] zram: partial IO refactoring

For architecture(PAGE_SIZE > 4K), zram have supported partial IO. However, the mixed code for handling normal/partial IO is too mess, error-prone to modify IO handler functions with upcoming feature so this patch aims for cleaning up zram's IO handling functions. Signed-off-by: Minchan Kim ---

[PATCH 5/5] zram: introduce zram data accessor

With element, sometime I got confused handle and element access. It might be my bad but I think it's time to introduce accessor to prevent future idiot like me. This patch is just clean-up patch so it shouldn't change any behavior. Signed-off-by: Minchan Kim ---

[PATCH 5/5] zram: introduce zram data accessor

With element, sometime I got confused handle and element access. It might be my bad but I think it's time to introduce accessor to prevent future idiot like me. This patch is just clean-up patch so it shouldn't change any behavior. Signed-off-by: Minchan Kim --- drivers/block/zram/zram_drv.c |

Re: + zram-factor-out-partial-io-routine.patch added to -mm tree

Hi Andrew, Could you drop this patchset because I will send new patchset to replace this. Thanks. On Wed, Mar 29, 2017 at 03:25:32PM -0700, a...@linux-foundation.org wrote: > > The patch titled > Subject: zram: factor out partial IO routine > has been added to the -mm tree. Its filename

Re: + zram-factor-out-partial-io-routine.patch added to -mm tree

Hi Andrew, Could you drop this patchset because I will send new patchset to replace this. Thanks. On Wed, Mar 29, 2017 at 03:25:32PM -0700, a...@linux-foundation.org wrote: > > The patch titled > Subject: zram: factor out partial IO routine > has been added to the -mm tree. Its filename

Re: [PATCH] zram: set physical queue limits to avoid array out of bounds accesses

Hi Jens, On Thu, Mar 30, 2017 at 07:38:26PM -0600, Jens Axboe wrote: > On 03/30/2017 05:45 PM, Minchan Kim wrote: > > On Thu, Mar 30, 2017 at 09:35:56AM -0600, Jens Axboe wrote: > >> On 03/30/2017 09:08 AM, Minchan Kim wrote: > >>> Hi Jens, > >>> > >>> It seems you miss this. > >>> Could you

Re: [PATCH] zram: set physical queue limits to avoid array out of bounds accesses

Hi Jens, On Thu, Mar 30, 2017 at 07:38:26PM -0600, Jens Axboe wrote: > On 03/30/2017 05:45 PM, Minchan Kim wrote: > > On Thu, Mar 30, 2017 at 09:35:56AM -0600, Jens Axboe wrote: > >> On 03/30/2017 09:08 AM, Minchan Kim wrote: > >>> Hi Jens, > >>> > >>> It seems you miss this. > >>> Could you

Re: [PATCH net-next v3 5/5] net-next: dsa: add dsa support for Mediatek MT7530 switch

Hi Sean, [auto build test ERROR on net-next/master] url: https://github.com/0day-ci/linux/commits/sean-wang-mediatek-com/net-next-dsa-add-Mediatek-MT7530-support/20170330-135532 config: m68k-allmodconfig (attached as .config) compiler: m68k-linux-gcc (GCC) 4.9.0 reproduce: wget

Re: [PATCH net-next v3 5/5] net-next: dsa: add dsa support for Mediatek MT7530 switch

Hi Sean, [auto build test ERROR on net-next/master] url: https://github.com/0day-ci/linux/commits/sean-wang-mediatek-com/net-next-dsa-add-Mediatek-MT7530-support/20170330-135532 config: m68k-allmodconfig (attached as .config) compiler: m68k-linux-gcc (GCC) 4.9.0 reproduce: wget

Re: [PATCH] staging: rtl8712: fixed multiple line derefence issue

On Mon, 2017-04-03 at 09:43 +0530, Prasant Jalan wrote: > On Thu, Mar 30, 2017 at 12:03 AM, Prasant Jalan > wrote: > > Checkpatch emits WARNING: Avoid multiple line dereference. > > > > Trivial indentation improvement helps fix the checkpatch warning. [] > > diff --git

Re: [PATCH] staging: rtl8712: fixed multiple line derefence issue

On Mon, 2017-04-03 at 09:43 +0530, Prasant Jalan wrote: > On Thu, Mar 30, 2017 at 12:03 AM, Prasant Jalan > wrote: > > Checkpatch emits WARNING: Avoid multiple line dereference. > > > > Trivial indentation improvement helps fix the checkpatch warning. [] > > diff --git

Re: [RFC 1/8] Introduce Peer-to-Peer memory (p2pmem) device

On 02/04/17 03:03 PM, Sinan Kaya wrote: > Push the decision all the way to the user. Let them decide whether they > want this feature to work on a root port connected port or under the > switch. Yes, I prefer this too. If other folks agree with that I'd be very happy to go back to user chooses.

Re: [RFC 1/8] Introduce Peer-to-Peer memory (p2pmem) device

On 02/04/17 03:03 PM, Sinan Kaya wrote: > Push the decision all the way to the user. Let them decide whether they > want this feature to work on a root port connected port or under the > switch. Yes, I prefer this too. If other folks agree with that I'd be very happy to go back to user chooses.

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

On Fri, Mar 31 2017, Jeff Layton wrote: > During LSF/MM this year, we had a discussion about the current sorry > state of writeback error reporting, and what could be done to improve > the situation. This patchset represents a first pass at the proposal > I made there. > > It first adds a new set

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

On Fri, Mar 31 2017, Jeff Layton wrote: > During LSF/MM this year, we had a discussion about the current sorry > state of writeback error reporting, and what could be done to improve > the situation. This patchset represents a first pass at the proposal > I made there. > > It first adds a new set

Re: [RFCv2] arm64: support HAVE_ARCH_RARE_WRITE and HAVE_ARCH_RARE_WRITE_MEMCPY

> On 31 Mar 2017, at 6:25 PM, Ard Biesheuvel wrote: > > On 30 March 2017 at 15:39, Hoeun Ryu wrote: >> This patch might be a part of Kees Cook's rare_write infrastructure series >> for [1] for arm64 architecture. >> >> This implementation is

Re: [RFCv2] arm64: support HAVE_ARCH_RARE_WRITE and HAVE_ARCH_RARE_WRITE_MEMCPY

> On 31 Mar 2017, at 6:25 PM, Ard Biesheuvel wrote: > > On 30 March 2017 at 15:39, Hoeun Ryu wrote: >> This patch might be a part of Kees Cook's rare_write infrastructure series >> for [1] for arm64 architecture. >> >> This implementation is based on Mark Rutland's suggestions [2], which is

Re: [PATCH] staging: rtl8712: fixed multiple line derefence issue

On Thu, Mar 30, 2017 at 12:03 AM, Prasant Jalan wrote: > Checkpatch emits WARNING: Avoid multiple line dereference. > > Trivial indentation improvement helps fix the checkpatch warning. > > Signed-off-by: Prasant Jalan > --- >

Re: [PATCH] staging: rtl8712: fixed multiple line derefence issue

On Thu, Mar 30, 2017 at 12:03 AM, Prasant Jalan wrote: > Checkpatch emits WARNING: Avoid multiple line dereference. > > Trivial indentation improvement helps fix the checkpatch warning. > > Signed-off-by: Prasant Jalan > --- > drivers/staging/rtl8712/rtl871x_xmit.c | 12 ++-- > 1 file

arch/x86/kernel/ftrace.c:35:3: error: #error The following combination is not supported: ((compiler missing -mfentry) || (CONFIG_X86_32 and !CONFIG_DYNAMIC_FTRACE)) && CONFIG_FUNCTION_GRAPH_TRACER &&

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: a71c9a1c779f2499fb2afc0553e543f18aff6edf commit: 3f135e57a4f76d24ae8d8a490314331f0ced40c5 x86/build: Mostly disable '-maccumulate-outgoing-args' date: 4 days ago config: x86_64-randconfig-a0-04031038

arch/x86/kernel/ftrace.c:35:3: error: #error The following combination is not supported: ((compiler missing -mfentry) || (CONFIG_X86_32 and !CONFIG_DYNAMIC_FTRACE)) && CONFIG_FUNCTION_GRAPH_TRACER &&

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: a71c9a1c779f2499fb2afc0553e543f18aff6edf commit: 3f135e57a4f76d24ae8d8a490314331f0ced40c5 x86/build: Mostly disable '-maccumulate-outgoing-args' date: 4 days ago config: x86_64-randconfig-a0-04031038

Re: [PATCH] mm: Add additional consistency check

Kees Cook writes: > On Fri, Mar 31, 2017 at 2:33 PM, Andrew Morton > wrote: >> On Fri, 31 Mar 2017 09:40:28 -0700 Kees Cook wrote: >> >>> As found in PaX, this adds a cheap check on heap consistency, just to >>> notice if

Re: [PATCH] mm: Add additional consistency check

Kees Cook writes: > On Fri, Mar 31, 2017 at 2:33 PM, Andrew Morton > wrote: >> On Fri, 31 Mar 2017 09:40:28 -0700 Kees Cook wrote: >> >>> As found in PaX, this adds a cheap check on heap consistency, just to >>> notice if things have gotten corrupted in the page lookup. >> >> "As found in PaX"

linux-next: build failure after merge of the drm-misc tree

Hi all, After merging the drm-misc tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/gpu/drm/vmwgfx/vmwgfx_scrn.c: In function 'vmw_sou_crtc_page_flip': drivers/gpu/drm/vmwgfx/vmwgfx_scrn.c:327:8: error: too few arguments to function 'drm_atomic_helper_page_flip'

linux-next: build failure after merge of the drm-misc tree

Hi all, After merging the drm-misc tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/gpu/drm/vmwgfx/vmwgfx_scrn.c: In function 'vmw_sou_crtc_page_flip': drivers/gpu/drm/vmwgfx/vmwgfx_scrn.c:327:8: error: too few arguments to function 'drm_atomic_helper_page_flip'

Re: [PATCH v6 0/4] phy: USB and PCIe phy drivers for Qcom chipsets

On 03/20/2017 07:24 PM, Vivek Gautam wrote: This patch series adds couple of PHY drivers for Qualcomm chipsets. a) qcom-qusb2 phy driver: that provides High Speed USB functionality. b) qcom-qmp phy driver: that is a combo phy providing support for USB3, PCIe, UFS and few other controllers.

Re: [PATCH v6 0/4] phy: USB and PCIe phy drivers for Qcom chipsets

On 03/20/2017 07:24 PM, Vivek Gautam wrote: This patch series adds couple of PHY drivers for Qualcomm chipsets. a) qcom-qusb2 phy driver: that provides High Speed USB functionality. b) qcom-qmp phy driver: that is a combo phy providing support for USB3, PCIe, UFS and few other controllers.

Re: [RFCv2] arm64: support HAVE_ARCH_RARE_WRITE and HAVE_ARCH_RARE_WRITE_MEMCPY

> On Mar 31, 2017, at 4:38 AM, Kees Cook wrote: > >> On Thu, Mar 30, 2017 at 7:39 AM, Hoeun Ryu wrote: >> This patch might be a part of Kees Cook's rare_write infrastructure series >> for [1] for arm64 architecture. >> >> This implementation is

Re: [RFCv2] arm64: support HAVE_ARCH_RARE_WRITE and HAVE_ARCH_RARE_WRITE_MEMCPY

> On Mar 31, 2017, at 4:38 AM, Kees Cook wrote: > >> On Thu, Mar 30, 2017 at 7:39 AM, Hoeun Ryu wrote: >> This patch might be a part of Kees Cook's rare_write infrastructure series >> for [1] for arm64 architecture. >> >> This implementation is based on Mark Rutland's suggestions [2], which

linux-next: manual merge of the drm-misc tree with the drm tree

Hi all, Today's linux-next merge of the drm-misc tree got conflicts in: drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c drivers/gpu/drm/vmwgfx/vmwgfx_scrn.c drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c between commits: 904bb5e5817f ("drm/vmwgfx: Switch over to internal atomic API for STDU") b0119cb9229d

linux-next: manual merge of the drm-misc tree with the drm tree

Hi all, Today's linux-next merge of the drm-misc tree got conflicts in: drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c drivers/gpu/drm/vmwgfx/vmwgfx_scrn.c drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c between commits: 904bb5e5817f ("drm/vmwgfx: Switch over to internal atomic API for STDU") b0119cb9229d

Re: [PATCH v3 14/37] mtd: nand: denali: support "nand-ecc-strength" DT property

Hi Boris, 2017-03-31 18:46 GMT+09:00 Boris Brezillon : > You can try something like that when no explicit ecc.strength and > ecc.size has been set in the DT and when ECC_MAXIMIZE was not passed. > > static int > denali_get_closest_ecc_strength(struct

Re: [PATCH v3 14/37] mtd: nand: denali: support "nand-ecc-strength" DT property

Hi Boris, 2017-03-31 18:46 GMT+09:00 Boris Brezillon : > You can try something like that when no explicit ecc.strength and > ecc.size has been set in the DT and when ECC_MAXIMIZE was not passed. > > static int > denali_get_closest_ecc_strength(struct denali_nand_info *denali, >

Re: [PATCH] phy: bcm-ns-usb3: split all writes into reg & val pairs

On Sun, Apr 2, 2017 at 12:55 PM, Rafał Miłecki wrote: > From: Rafał Miłecki > > So far all the PHY initialization was implemented using some totally > magic values. There was some pattern there but it wasn't clear what is > it about. > > Thanks to the patch

Re: [PATCH] phy: bcm-ns-usb3: split all writes into reg & val pairs

On Sun, Apr 2, 2017 at 12:55 PM, Rafał Miłecki wrote: > From: Rafał Miłecki > > So far all the PHY initialization was implemented using some totally > magic values. There was some pattern there but it wasn't clear what is > it about. > > Thanks to the patch submitted by Broadcom: > [PATCH 5/6]

Re: [kbuild-all] [PATCH] net: hns: fix boolreturn.cocci warnings

Hi David, On Sun, Apr 02, 2017 at 07:44:02PM -0700, David Miller wrote: From: kbuild test robot Date: Sat, 1 Apr 2017 07:50:55 +0800 drivers/net/ethernet/hisilicon/hns/hns_enet.c:1548:8-9: WARNING: return of 0/1 in function 'hns_enable_serdes_lb' with return type bool

Re: [kbuild-all] [PATCH] net: hns: fix boolreturn.cocci warnings

Hi David, On Sun, Apr 02, 2017 at 07:44:02PM -0700, David Miller wrote: From: kbuild test robot Date: Sat, 1 Apr 2017 07:50:55 +0800 drivers/net/ethernet/hisilicon/hns/hns_enet.c:1548:8-9: WARNING: return of 0/1 in function 'hns_enable_serdes_lb' with return type bool Return statements in

Re: [PATCH] net: hns: fix boolreturn.cocci warnings

From: kbuild test robot Date: Sat, 1 Apr 2017 07:50:55 +0800 > drivers/net/ethernet/hisilicon/hns/hns_enet.c:1548:8-9: WARNING: return of > 0/1 in function 'hns_enable_serdes_lb' with return type bool > > Return statements in functions returning bool should use > true/false

Re: [PATCH] phy/ethtool: Add missing SPEED_ strings

On Sun, 2017-04-02 at 15:29 -0700, Florian Fainelli wrote: > Le 04/02/17 à 14:30, Joe Perches a écrit : > > Add all the currently available SPEED_ strings. > > > > Signed-off-by: Joe Perches > > Considering that PHYLIB does not support anything > 10Gbs at the moment, > I am

Re: [PATCH] net: hns: fix boolreturn.cocci warnings

From: kbuild test robot Date: Sat, 1 Apr 2017 07:50:55 +0800 > drivers/net/ethernet/hisilicon/hns/hns_enet.c:1548:8-9: WARNING: return of > 0/1 in function 'hns_enable_serdes_lb' with return type bool > > Return statements in functions returning bool should use > true/false instead of 1/0. >

Re: [PATCH] phy/ethtool: Add missing SPEED_ strings

On Sun, 2017-04-02 at 15:29 -0700, Florian Fainelli wrote: > Le 04/02/17 à 14:30, Joe Perches a écrit : > > Add all the currently available SPEED_ strings. > > > > Signed-off-by: Joe Perches > > Considering that PHYLIB does not support anything > 10Gbs at the moment, > I am not sure how useful

Re: [PATCH] net: ethernet: ti: cpsw: wake tx queues on ndo_tx_timeout

From: Grygorii Strashko Date: Fri, 31 Mar 2017 18:41:23 -0500 > In case, if TX watchdog is fired some or all netdev TX queues will be > stopped and as part of recovery it is required not only to drain and > reinitailize CPSW TX channeles, but also wake up stoppted TX

Re: [PATCH] net: ethernet: ti: cpsw: wake tx queues on ndo_tx_timeout

From: Grygorii Strashko Date: Fri, 31 Mar 2017 18:41:23 -0500 > In case, if TX watchdog is fired some or all netdev TX queues will be > stopped and as part of recovery it is required not only to drain and > reinitailize CPSW TX channeles, but also wake up stoppted TX queues what > doesn't happen

Re: linux-next: build warning after merge of the nfsd tree

On Mon, Apr 03, 2017 at 11:09:48AM +1000, Stephen Rothwell wrote: > Hi, > > After merging the nfsd tree, today's linux-next build (powerpc > ppc64_defconfig) produced this warning: > > fs/nfsd/nfs4state.c: In function 'copy_cred': > fs/nfsd/nfs4state.c:1917:6: warning: unused variable 'ret'

Re: linux-next: build warning after merge of the nfsd tree

On Mon, Apr 03, 2017 at 11:09:48AM +1000, Stephen Rothwell wrote: > Hi, > > After merging the nfsd tree, today's linux-next build (powerpc > ppc64_defconfig) produced this warning: > > fs/nfsd/nfs4state.c: In function 'copy_cred': > fs/nfsd/nfs4state.c:1917:6: warning: unused variable 'ret'

Re: [git pull] vfs fixes

On Sun, Apr 02, 2017 at 05:58:41PM -0700, Linus Torvalds wrote: > I had to go and double-check that "DCACHE_DIRECTORY_TYPE" is what > d_can_lookup() actually checks, so _that_ part is perhaps a bit > subtle, and might be worth noting in that comment that you edited. > > So the real "rule" ends

Re: [git pull] vfs fixes

On Sun, Apr 02, 2017 at 05:58:41PM -0700, Linus Torvalds wrote: > I had to go and double-check that "DCACHE_DIRECTORY_TYPE" is what > d_can_lookup() actually checks, so _that_ part is perhaps a bit > subtle, and might be worth noting in that comment that you edited. > > So the real "rule" ends

linux-next: manual merge of the net-next tree with the net tree

Hi all, Today's linux-next merge of the net-next tree got conflicts in: tools/testing/selftests/bpf/Makefile tools/testing/selftests/bpf/test_verifier.c between commit: 02ea80b1850e ("bpf: add various verifier test cases for self-tests") from the net tree and commits: 6882804c916b

linux-next: manual merge of the net-next tree with the net tree

Hi all, Today's linux-next merge of the net-next tree got conflicts in: tools/testing/selftests/bpf/Makefile tools/testing/selftests/bpf/test_verifier.c between commit: 02ea80b1850e ("bpf: add various verifier test cases for self-tests") from the net tree and commits: 6882804c916b

Re: [PATCH v2] usb: dwc2: Make sure we disconnect the gadget state

On 03/29/2017 08:23 PM, John Stultz wrote: > I had seen some odd behavior with HiKey's usb-gadget interface > that I finally seemed to have chased down. Basically every other > time I plugged in the OTG port, the gadget interface would > properly initialize. The other times, I'd get a big WARN_ON

Re: [PATCH v2] usb: dwc2: Make sure we disconnect the gadget state

On 03/29/2017 08:23 PM, John Stultz wrote: > I had seen some odd behavior with HiKey's usb-gadget interface > that I finally seemed to have chased down. Basically every other > time I plugged in the OTG port, the gadget interface would > properly initialize. The other times, I'd get a big WARN_ON

Re: [PATCH v4 3/5] watchdog: iTCO_wdt: Add PMC specific noreboot update api

Hi, On Sun, Apr 2, 2017 at 7:04 AM, Andy Shevchenko wrote: > On Sat, Apr 1, 2017 at 2:27 AM, Kuppuswamy Sathyanarayanan > wrote: >> In some SOCs, setting noreboot bit needs modification to > > SoCs. > > Perhaps you can

Re: [PATCH v4 3/5] watchdog: iTCO_wdt: Add PMC specific noreboot update api

Hi, On Sun, Apr 2, 2017 at 7:04 AM, Andy Shevchenko wrote: > On Sat, Apr 1, 2017 at 2:27 AM, Kuppuswamy Sathyanarayanan > wrote: >> In some SOCs, setting noreboot bit needs modification to > > SoCs. > > Perhaps you can create a wikipage to share with your team what style > issues usually needs

Re: [PATCH v4 4/5] platform/x86: intel_pmc_ipc: Fix iTCO GCS memory mapping failure

Hi Andy, On Sun, Apr 2, 2017 at 7:10 AM, Andy Shevchenko wrote: > On Sat, Apr 1, 2017 at 2:27 AM, Kuppuswamy Sathyanarayanan > wrote: >> iTCO watchdog driver need access to PMC_CFG GCR register to modify > > iTCO_wdt or

Re: [PATCH v4 4/5] platform/x86: intel_pmc_ipc: Fix iTCO GCS memory mapping failure

Hi Andy, On Sun, Apr 2, 2017 at 7:10 AM, Andy Shevchenko wrote: > On Sat, Apr 1, 2017 at 2:27 AM, Kuppuswamy Sathyanarayanan > wrote: >> iTCO watchdog driver need access to PMC_CFG GCR register to modify > > iTCO_wdt or use above in the rest of the series. > > So, choose one and use it

Re: [PATCH v4 1/5] platform/x86: intel_pmc_ipc: fix gcr offset

Yes, just applying this patch will fix the existing offset issue. On Sun, Apr 2, 2017 at 7:11 AM, Andy Shevchenko wrote: > On Sat, Apr 1, 2017 at 2:27 AM, Kuppuswamy Sathyanarayanan > wrote: >> According to Broxton APL PMC

Re: [PATCH v4 1/5] platform/x86: intel_pmc_ipc: fix gcr offset

Yes, just applying this patch will fix the existing offset issue. On Sun, Apr 2, 2017 at 7:11 AM, Andy Shevchenko wrote: > On Sat, Apr 1, 2017 at 2:27 AM, Kuppuswamy Sathyanarayanan > wrote: >> According to Broxton APL PMC spec, gcr mem region starts >> at offset 0x1000 from ipc mem base

Re: [PATCH v4 2/5] platform/x86: intel_pmc_ipc: Add pmc gcr read/write/update api's

Hi Andy, Thanks for your comments. On Sun, Apr 2, 2017 at 6:58 AM, Andy Shevchenko wrote: > On Sat, Apr 1, 2017 at 2:27 AM, Kuppuswamy Sathyanarayanan > wrote: >> This patch adds API's to read/write/update PMC GC registers.

Re: [PATCH v4 2/5] platform/x86: intel_pmc_ipc: Add pmc gcr read/write/update api's

Hi Andy, Thanks for your comments. On Sun, Apr 2, 2017 at 6:58 AM, Andy Shevchenko wrote: > On Sat, Apr 1, 2017 at 2:27 AM, Kuppuswamy Sathyanarayanan > wrote: >> This patch adds API's to read/write/update PMC GC registers. >> PMC dependent devices like iTCO_WDT, Telemetry has requirement > >

Linux 4.11-rc5

Ok, things have definitely started to calm down, let's hope it stays this way and it wasn't just a fluke this week. Things look fairly normal, with just under 60% of the changes in drivers (edac, sound, block, pci, etc), and about 30% in arch updates (some misc ptrace fixes, random stuff). The

Linux 4.11-rc5

Ok, things have definitely started to calm down, let's hope it stays this way and it wasn't just a fluke this week. Things look fairly normal, with just under 60% of the changes in drivers (edac, sound, block, pci, etc), and about 30% in arch updates (some misc ptrace fixes, random stuff). The

Re: Updating sunxi tree in linux-next

Hi Stephen, On Mon, Apr 3, 2017 at 7:56 AM, Stephen Rothwell wrote: > Hi Maxime, > > On Fri, 31 Mar 2017 09:57:29 +0200 Maxime Ripard > wrote: >> >> We've switched from my personal git tree for the Allwinner sunxi >> development to a

Re: Updating sunxi tree in linux-next

Hi Stephen, On Mon, Apr 3, 2017 at 7:56 AM, Stephen Rothwell wrote: > Hi Maxime, > > On Fri, 31 Mar 2017 09:57:29 +0200 Maxime Ripard > wrote: >> >> We've switched from my personal git tree for the Allwinner sunxi >> development to a shared tree: >>

[PATCH] loop: Add PF_LESS_THROTTLE to block/loop device thread.

When a filesystem is mounted from a loop device, writes are throttled by balance_dirty_pages() twice: once when writing to the filesystem and once when the loop_handle_cmd() writes to the backing file. This double-throttling can trigger positive feedback loops that create significant delays.

[PATCH] loop: Add PF_LESS_THROTTLE to block/loop device thread.

When a filesystem is mounted from a loop device, writes are throttled by balance_dirty_pages() twice: once when writing to the filesystem and once when the loop_handle_cmd() writes to the backing file. This double-throttling can trigger positive feedback loops that create significant delays.

Re: [PATCH net-next v3 5/5] net-next: dsa: add dsa support for Mediatek MT7530 switch

Hi Sean, [auto build test ERROR on net-next/master] url: https://github.com/0day-ci/linux/commits/sean-wang-mediatek-com/net-next-dsa-add-Mediatek-MT7530-support/20170330-135532 config: arm-allmodconfig (attached as .config) compiler: arm-linux-gnueabi-gcc (Debian 6.1.1-9) 6.1.1 20160705

Re: [PATCH net-next v3 5/5] net-next: dsa: add dsa support for Mediatek MT7530 switch

Hi Sean, [auto build test ERROR on net-next/master] url: https://github.com/0day-ci/linux/commits/sean-wang-mediatek-com/net-next-dsa-add-Mediatek-MT7530-support/20170330-135532 config: arm-allmodconfig (attached as .config) compiler: arm-linux-gnueabi-gcc (Debian 6.1.1-9) 6.1.1 20160705

Re: [PATCH] i2c: use void pointers for supplying data for reads and writes

Hi Dmitry, [auto build test ERROR on wsa/i2c/for-next] [also build test ERROR on v4.11-rc4 next-20170331] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

linux-next: build warning after merge of the nfsd tree

Hi, After merging the nfsd tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: fs/nfsd/nfs4state.c: In function 'copy_cred': fs/nfsd/nfs4state.c:1917:6: warning: unused variable 'ret' [-Wunused-variable] int ret; ^ Introduced by commit d39662236bf8

Re: [PATCH] i2c: use void pointers for supplying data for reads and writes

Hi Dmitry, [auto build test ERROR on wsa/i2c/for-next] [also build test ERROR on v4.11-rc4 next-20170331] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

linux-next: build warning after merge of the nfsd tree

Hi, After merging the nfsd tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: fs/nfsd/nfs4state.c: In function 'copy_cred': fs/nfsd/nfs4state.c:1917:6: warning: unused variable 'ret' [-Wunused-variable] int ret; ^ Introduced by commit d39662236bf8

  1   2   3   4   5   6   >