[PATCH] Revert "clocksource/drivers/timer_sun5i: Replace code by clocksource_mmio_init"

This reverts commit 157dfadef832 ("clocksource/drivers/timer_sun5i: Replace code by clocksource_mmio_init"). struct clocksource is also used by the clk notifier callback, to unregister and re-register the clocksource with a different clock rate. clocksource_mmio_init does not pass back a pointer

[PATCH] Revert "clocksource/drivers/timer_sun5i: Replace code by clocksource_mmio_init"

This reverts commit 157dfadef832 ("clocksource/drivers/timer_sun5i: Replace code by clocksource_mmio_init"). struct clocksource is also used by the clk notifier callback, to unregister and re-register the clocksource with a different clock rate. clocksource_mmio_init does not pass back a pointer

[PATCH] clk: sunxi-ng: sun6i-a31: Force AHB1 clock to use PLL6 as parent

On the A31, the DMA engine only works if AHB1 is clocked from PLL6. In addition, the hstimer is clocked from AHB1, and if AHB1 is clocked from the CPU clock, and cpufreq is working, we get an unstable timer. Force the AHB1 clock to use PLL6 as its parent. Previously this was done in the device

[PATCH] clk: sunxi-ng: sun6i-a31: Force AHB1 clock to use PLL6 as parent

On the A31, the DMA engine only works if AHB1 is clocked from PLL6. In addition, the hstimer is clocked from AHB1, and if AHB1 is clocked from the CPU clock, and cpufreq is working, we get an unstable timer. Force the AHB1 clock to use PLL6 as its parent. Previously this was done in the device

Re: [PATCH v5 02/23] of: device: Export of_device_{get_modalias, uvent_modalias} to modules

On Tue, Oct 18, 2016 at 9:56 AM, Stephen Boyd wrote: > The ULPI bus can be built as a module, and it will soon be > calling these functions when it supports probing devices from DT. > Export them so they can be used by the ULPI module. > > Acked-by: Rob Herring

Re: [PATCH v5 02/23] of: device: Export of_device_{get_modalias, uvent_modalias} to modules

On Tue, Oct 18, 2016 at 9:56 AM, Stephen Boyd wrote: > The ULPI bus can be built as a module, and it will soon be > calling these functions when it supports probing devices from DT. > Export them so they can be used by the ULPI module. > > Acked-by: Rob Herring > Cc: > Signed-off-by: Stephen

Re: [PATCH 02/28] [v2] mtd: mtk: avoid warning in mtk_ecc_encode

On Tue, 18 Oct 2016 00:05:31 +0200 Arnd Bergmann wrote: > When building with -Wmaybe-uninitialized, gcc produces a silly false positive > warning for the mtk_ecc_encode function: > > drivers/mtd/nand/mtk_ecc.c: In function 'mtk_ecc_encode': > drivers/mtd/nand/mtk_ecc.c:402:15:

Re: [PATCH 02/28] [v2] mtd: mtk: avoid warning in mtk_ecc_encode

On Tue, 18 Oct 2016 00:05:31 +0200 Arnd Bergmann wrote: > When building with -Wmaybe-uninitialized, gcc produces a silly false positive > warning for the mtk_ecc_encode function: > > drivers/mtd/nand/mtk_ecc.c: In function 'mtk_ecc_encode': > drivers/mtd/nand/mtk_ecc.c:402:15: error: 'val' may

Re: [PATCH 10/28] UBI: fix uninitialized access of vid_hdr pointer

Hi Arnd, On Tue, 18 Oct 2016 00:10:13 +0200 Arnd Bergmann wrote: > A rework of UBI that just appeared in linux-next during the merge > window introduced caused the recover_peb to use a variable that > is never initialized as seen from this gcc warning: > > drivers/mtd/ubi/eba.c:

Re: [PATCH 10/28] UBI: fix uninitialized access of vid_hdr pointer

Hi Arnd, On Tue, 18 Oct 2016 00:10:13 +0200 Arnd Bergmann wrote: > A rework of UBI that just appeared in linux-next during the merge > window introduced caused the recover_peb to use a variable that > is never initialized as seen from this gcc warning: > > drivers/mtd/ubi/eba.c: In function

Re: [PATCH 6/8] IB/hns: Replace counting semaphore event_sem with wait condition

On 18 October 2016 at 01:59, Arnd Bergmann wrote: > On Monday, October 17, 2016 10:01:00 PM CEST Binoy Jayan wrote: >> --- a/drivers/infiniband/hw/hns/hns_roce_cmd.c >> +++ b/drivers/infiniband/hw/hns/hns_roce_cmd.c >> @@ -248,10 +248,14 @@ static int hns_roce_cmd_mbox_wait(struct

Re: [PATCH 6/8] IB/hns: Replace counting semaphore event_sem with wait condition

On 18 October 2016 at 01:59, Arnd Bergmann wrote: > On Monday, October 17, 2016 10:01:00 PM CEST Binoy Jayan wrote: >> --- a/drivers/infiniband/hw/hns/hns_roce_cmd.c >> +++ b/drivers/infiniband/hw/hns/hns_roce_cmd.c >> @@ -248,10 +248,14 @@ static int hns_roce_cmd_mbox_wait(struct hns_roce_dev

Re: [PATCH V3 00/11] block-throttle: add .high limit

Not to compound upon this again. However if BFQ isn't suitable to replace CFQ for high I/O workloads (I've yet to see 20k IOPS on any reasonably sized SAN (SC4020 / v5000, etc)), can't we at-least default BFQ to become the default I/O scheduler for people otherwise requesting CFQ? Paolo has had a

Re: [PATCH 05/28] ext2: avoid bogus -Wmaybe-uninitialized warning

Thanks Arnd, this looks fine to me: Reviewed-by: Christoph Hellwig

Re: [PATCH V3 00/11] block-throttle: add .high limit

Not to compound upon this again. However if BFQ isn't suitable to replace CFQ for high I/O workloads (I've yet to see 20k IOPS on any reasonably sized SAN (SC4020 / v5000, etc)), can't we at-least default BFQ to become the default I/O scheduler for people otherwise requesting CFQ? Paolo has had a

Re: [PATCH 05/28] ext2: avoid bogus -Wmaybe-uninitialized warning

Thanks Arnd, this looks fine to me: Reviewed-by: Christoph Hellwig

Re: [PATCH 00/28] Reenable maybe-uninitialized warnings

On Tue, Oct 18, 2016 at 12:03:28AM +0200, Arnd Bergmann wrote: > This is a set of patches that I hope to get into v4.9 in some form > in order to turn on the -Wmaybe-uninitialized warnings again. Hi Arnd, I jsut complained to Geert that I was introducing way to many bugs or pointless warnings

Re: [PATCH 00/28] Reenable maybe-uninitialized warnings

On Tue, Oct 18, 2016 at 12:03:28AM +0200, Arnd Bergmann wrote: > This is a set of patches that I hope to get into v4.9 in some form > in order to turn on the -Wmaybe-uninitialized warnings again. Hi Arnd, I jsut complained to Geert that I was introducing way to many bugs or pointless warnings

[PATCH] Documentation/RCU: Fix minor typo

deference should actually be dereference. Signed-off-by: Pranith Kumar --- Documentation/RCU/whatisRCU.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/RCU/whatisRCU.txt b/Documentation/RCU/whatisRCU.txt index 2044227..5cbd8b2 100644

[PATCH] Documentation/RCU: Fix minor typo

deference should actually be dereference. Signed-off-by: Pranith Kumar --- Documentation/RCU/whatisRCU.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/RCU/whatisRCU.txt b/Documentation/RCU/whatisRCU.txt index 2044227..5cbd8b2 100644 ---

Bug in fua code

Ming, I recently discovered a bug in the FUA code - a recent bcachefs change exposed it - and my best guess is it's related to your recent changes to blk-flush.c. What I'm seeing is if all writes are issued as FUA writes, in a short period of time the request queue get stuck - writes are on the

Bug in fua code

Ming, I recently discovered a bug in the FUA code - a recent bcachefs change exposed it - and my best guess is it's related to your recent changes to blk-flush.c. What I'm seeing is if all writes are issued as FUA writes, in a short period of time the request queue get stuck - writes are on the

[PATCH 7/7] ufs-qcom: phy/hcd: Refactoring phy clock handling

Add phy clock enable code to phy_power_on/off callbacks, and remove explicit calls to enable these phy clocks from the ufs-qcom hcd driver. Signed-off-by: Vivek Gautam Reviewed-by: Subhash Jadavani --- drivers/phy/phy-qcom-ufs.c | 12

[PATCH 7/7] ufs-qcom: phy/hcd: Refactoring phy clock handling

Add phy clock enable code to phy_power_on/off callbacks, and remove explicit calls to enable these phy clocks from the ufs-qcom hcd driver. Signed-off-by: Vivek Gautam Reviewed-by: Subhash Jadavani --- drivers/phy/phy-qcom-ufs.c | 12 +++- drivers/scsi/ufs/ufs-qcom.c | 15

[PATCH 6/7] phy: qcom-ufs-qmp-xx: Move clock and regulator init out of phy init

The phy init is meant to do phy initialization rather than just getting the clock and regulator. Move these clock and regulator get to probe(), to make room for actual phy initialization sequence. Signed-off-by: Vivek Gautam Reviewed-by: Subhash Jadavani

[PATCH 4/7] phy: qcom-ufs-qmp-xx: Discard remove callback for drivers.

remove() callback does a phy_exit() only and nothing else now. The phy_exit() over the generic phy is called from the phy consumer, and phy provider driver should not explicitly need to call any phy_exit(). So discard the remove callback for qcom-ufs phy platform drivers. Signed-off-by: Vivek

[PATCH 6/7] phy: qcom-ufs-qmp-xx: Move clock and regulator init out of phy init

The phy init is meant to do phy initialization rather than just getting the clock and regulator. Move these clock and regulator get to probe(), to make room for actual phy initialization sequence. Signed-off-by: Vivek Gautam Reviewed-by: Subhash Jadavani --- drivers/phy/phy-qcom-ufs-qmp-14nm.c

[PATCH 4/7] phy: qcom-ufs-qmp-xx: Discard remove callback for drivers.

remove() callback does a phy_exit() only and nothing else now. The phy_exit() over the generic phy is called from the phy consumer, and phy provider driver should not explicitly need to call any phy_exit(). So discard the remove callback for qcom-ufs phy platform drivers. Signed-off-by: Vivek

[PATCH 5/7] phy: qcom-ufs: Cleanup clock and regulator initialization

Different methods pass around generic phy pointer to extract device pointer. Instead, pass the device pointer directly between function calls. Signed-off-by: Vivek Gautam Reviewed-by: Subhash Jadavani --- drivers/phy/phy-qcom-ufs-i.h

[PATCH 2/7] phy: qcom-ufs: Remove unnecessary BUG_ON

BUG_ON() are not preferred in the driver, plus the variable on which BUG_ON is asserted is already checked in the code before passing. Signed-off-by: Vivek Gautam Reviewed-by: Subhash Jadavani --- drivers/phy/phy-qcom-ufs.c | 2 -- 1 file

[PATCH 3/7] phy: qcom-ufs: Use devm sibling of kstrdup for regulator names

This helps us in avoiding any requirement for kfree() operation to be called exclusively over the allocated string pointer. Signed-off-by: Vivek Gautam Reviewed-by: Subhash Jadavani --- drivers/phy/phy-qcom-ufs.c | 5 + 1 file changed,

[PATCH 2/7] phy: qcom-ufs: Remove unnecessary BUG_ON

BUG_ON() are not preferred in the driver, plus the variable on which BUG_ON is asserted is already checked in the code before passing. Signed-off-by: Vivek Gautam Reviewed-by: Subhash Jadavani --- drivers/phy/phy-qcom-ufs.c | 2 -- 1 file changed, 2 deletions(-) diff --git

[PATCH 3/7] phy: qcom-ufs: Use devm sibling of kstrdup for regulator names

This helps us in avoiding any requirement for kfree() operation to be called exclusively over the allocated string pointer. Signed-off-by: Vivek Gautam Reviewed-by: Subhash Jadavani --- drivers/phy/phy-qcom-ufs.c | 5 + 1 file changed, 1 insertion(+), 4 deletions(-) diff --git

[PATCH 5/7] phy: qcom-ufs: Cleanup clock and regulator initialization

Different methods pass around generic phy pointer to extract device pointer. Instead, pass the device pointer directly between function calls. Signed-off-by: Vivek Gautam Reviewed-by: Subhash Jadavani --- drivers/phy/phy-qcom-ufs-i.h| 6 +-- drivers/phy/phy-qcom-ufs-qmp-14nm.c | 4 +-

[PATCH 1/7] phy: qcom-ufs: remove failure when rx/tx_iface_clk are absent

From: Yaniv Gardi Since in future UFS Phy's the tx_iface_clk and rx_iface_clk are no longer exist, we should not fail when their initialization fail, but rather just report with debug message. Signed-off-by: Yaniv Gardi Signed-off-by: Vivek Gautam

[PATCH 1/7] phy: qcom-ufs: remove failure when rx/tx_iface_clk are absent

From: Yaniv Gardi Since in future UFS Phy's the tx_iface_clk and rx_iface_clk are no longer exist, we should not fail when their initialization fail, but rather just report with debug message. Signed-off-by: Yaniv Gardi Signed-off-by: Vivek Gautam --- drivers/phy/phy-qcom-ufs.c | 15

[PATCH 0/7] ufs-qcom: phy/hcd: Clean up qcom-ufs phy and ufs-qcom hcd

These patches cleanup the ufs phy driver to an extent. Subsequent patches will target to clean the phy_init() of these qcom-ufs phy drivers in order to get rid of a number of exported APIs that phy drivers expose for ufs-qcom hcd driver to use. These patches are based on linux-phy next branch,

[PATCH 0/7] ufs-qcom: phy/hcd: Clean up qcom-ufs phy and ufs-qcom hcd

These patches cleanup the ufs phy driver to an extent. Subsequent patches will target to clean the phy_init() of these qcom-ufs phy drivers in order to get rid of a number of exported APIs that phy drivers expose for ufs-qcom hcd driver to use. These patches are based on linux-phy next branch,

Re: [PATCH v2] hwmon: (adm1275) Enable adm1278 VOUT sampling

On Tue, Oct 18, 2016 at 3:50 AM, Guenter Roeck wrote: > On Mon, Oct 17, 2016 at 06:38:53PM +1030, Joel Stanley wrote: >> From: Yi Li >> >> The adm1278 can optionally monitor the VOUT pin. This functioanltiy is >> not enabled at reset, so PMON_CONFIG needs to

Re: [PATCH v2] hwmon: (adm1275) Enable adm1278 VOUT sampling

On Tue, Oct 18, 2016 at 3:50 AM, Guenter Roeck wrote: > On Mon, Oct 17, 2016 at 06:38:53PM +1030, Joel Stanley wrote: >> From: Yi Li >> >> The adm1278 can optionally monitor the VOUT pin. This functioanltiy is >> not enabled at reset, so PMON_CONFIG needs to be modified in order to >> enable it.

Re: [PATCH 00/32] Create an User's manual and improve development-process book

Hi Jon, Am 18.10.2016 um 00:43 schrieb Jonathan Corbet : > I've only been able to take a quick look at these - I'm buried fairly deep > at the moment. A few superficial thoughts. > > On Mon, 17 Oct 2016 14:55:37 -0200 > Mauro Carvalho Chehab wrote: >

Re: [PATCH 00/32] Create an User's manual and improve development-process book

Hi Jon, Am 18.10.2016 um 00:43 schrieb Jonathan Corbet : > I've only been able to take a quick look at these - I'm buried fairly deep > at the moment. A few superficial thoughts. > > On Mon, 17 Oct 2016 14:55:37 -0200 > Mauro Carvalho Chehab wrote: > >> In my opinion, it would be better to

Re: [PATCH] MAINTAINERS: mmc: Move the mmc tree to kernel.org

On 10/18/2016 01:08 PM, Shawn Lin wrote: > 在 2016/10/18 11:52, Jaehoon Chung 写道: >> On 10/18/2016 12:19 PM, Shawn Lin wrote: >>> Hi Ulf, >>> >>> On 2016/10/17 20:54, Ulf Hansson wrote: Signed-off-by: Ulf Hansson --- MAINTAINERS | 2 +- 1 file changed,

Re: [PATCH] MAINTAINERS: mmc: Move the mmc tree to kernel.org

On 10/18/2016 01:08 PM, Shawn Lin wrote: > 在 2016/10/18 11:52, Jaehoon Chung 写道: >> On 10/18/2016 12:19 PM, Shawn Lin wrote: >>> Hi Ulf, >>> >>> On 2016/10/17 20:54, Ulf Hansson wrote: Signed-off-by: Ulf Hansson --- MAINTAINERS | 2 +- 1 file changed, 1 insertion(+), 1

Re: [PATCH] MAINTAINERS: mmc: Move the mmc tree to kernel.org

在 2016/10/18 11:52, Jaehoon Chung 写道: On 10/18/2016 12:19 PM, Shawn Lin wrote: Hi Ulf, On 2016/10/17 20:54, Ulf Hansson wrote: Signed-off-by: Ulf Hansson --- MAINTAINERS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS

Re: [PATCH] MAINTAINERS: mmc: Move the mmc tree to kernel.org

在 2016/10/18 11:52, Jaehoon Chung 写道: On 10/18/2016 12:19 PM, Shawn Lin wrote: Hi Ulf, On 2016/10/17 20:54, Ulf Hansson wrote: Signed-off-by: Ulf Hansson --- MAINTAINERS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index a009e00..e685724

Re: [PATCH] MAINTAINERS: mmc: Move the mmc tree to kernel.org

On 10/18/2016 12:19 PM, Shawn Lin wrote: > Hi Ulf, > > On 2016/10/17 20:54, Ulf Hansson wrote: >> Signed-off-by: Ulf Hansson >> --- >> MAINTAINERS | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/MAINTAINERS b/MAINTAINERS >> index

Re: [PATCH] MAINTAINERS: mmc: Move the mmc tree to kernel.org

On 10/18/2016 12:19 PM, Shawn Lin wrote: > Hi Ulf, > > On 2016/10/17 20:54, Ulf Hansson wrote: >> Signed-off-by: Ulf Hansson >> --- >> MAINTAINERS | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/MAINTAINERS b/MAINTAINERS >> index a009e00..e685724 100644 >> ---

[PATCH net-next] r8152: add new products of Lenovo

Add the following four products of Lenovo and sort the order of the list. VID PID 0x17ef 0x3062 0x17ef 0x3069 0x17ef 0x720c 0x17ef 0x7214 Signed-off-by: Hayes Wang ---

[PATCH net-next] r8152: add new products of Lenovo

Add the following four products of Lenovo and sort the order of the list. VID PID 0x17ef 0x3062 0x17ef 0x3069 0x17ef 0x720c 0x17ef 0x7214 Signed-off-by: Hayes Wang --- drivers/net/usb/cdc_ether.c | 28

[PATCH v2 3/4] input: Deprecate real timestamps beyond year 2106

struct timeval is not y2038 safe. All usage of timeval in the kernel will be replaced by y2038 safe structures. struct input_event maintains time for each input event. Real time timestamps are not ideal for input as this time can go backwards as noted in the patch a80b83b7b8 by John Stultz.

[PATCH v2 1/4] uinput: Add ioctl for using monotonic/ boot times

struct timeval which is part of struct input_event to maintain the event times is not y2038 safe. Real time timestamps are also not ideal for input_event as this time can go backwards as noted in the patch a80b83b7b8 by John Stultz. Arnd Bergmann suggested deprecating real time and using

[PATCH v2 3/4] input: Deprecate real timestamps beyond year 2106

struct timeval is not y2038 safe. All usage of timeval in the kernel will be replaced by y2038 safe structures. struct input_event maintains time for each input event. Real time timestamps are not ideal for input as this time can go backwards as noted in the patch a80b83b7b8 by John Stultz.

[PATCH v2 1/4] uinput: Add ioctl for using monotonic/ boot times

struct timeval which is part of struct input_event to maintain the event times is not y2038 safe. Real time timestamps are also not ideal for input_event as this time can go backwards as noted in the patch a80b83b7b8 by John Stultz. Arnd Bergmann suggested deprecating real time and using

[PATCH v2 4/4] input: serio: Replace timeval by timespec64

struct timeval is not y2038 safe. All references to timeval will be deleted from the kernel to make it y2038 safe. Replace its uses by y2038 safe struct timespec64. The timestamps changed here only keep track of delta times. These timestamps are also internal to kernel. Hence, monotonic times are

[PATCH v2 2/4] input: evdev: Replace timeval with timespec64

struct timeval is not y2038 safe. All references to timeval in the kernel will be replaced by y2038 safe structures. Replace all references to timeval with y2038 safe struct timespec64 here. struct input_event will be changed in a different patch. Signed-off-by: Deepa Dinamani

[PATCH v2 4/4] input: serio: Replace timeval by timespec64

struct timeval is not y2038 safe. All references to timeval will be deleted from the kernel to make it y2038 safe. Replace its uses by y2038 safe struct timespec64. The timestamps changed here only keep track of delta times. These timestamps are also internal to kernel. Hence, monotonic times are

[PATCH v2 2/4] input: evdev: Replace timeval with timespec64

struct timeval is not y2038 safe. All references to timeval in the kernel will be replaced by y2038 safe structures. Replace all references to timeval with y2038 safe struct timespec64 here. struct input_event will be changed in a different patch. Signed-off-by: Deepa Dinamani Reviewed-by:

[PATCH v2 0/4] Make input drivers y2038 safe

Reposting the series as I did not hear comments from the maintainers. The series is aimed at making input events y2038 safe. It extends the lifetime of the realtime timestamps in the events to year 2106. The plan is to deprecate realtime timestamps anyway as they are not appropriate for these

[PATCH v2 0/4] Make input drivers y2038 safe

Reposting the series as I did not hear comments from the maintainers. The series is aimed at making input events y2038 safe. It extends the lifetime of the realtime timestamps in the events to year 2106. The plan is to deprecate realtime timestamps anyway as they are not appropriate for these

RE: USB GADGET: have a question about usb2eth

> -Original Message- > From: Felipe Balbi [mailto:ba...@kernel.org] > Sent: Monday, October 17, 2016 5:29 PM > To: Lipengcheng; Peter Chen > Cc: gre...@linuxfoundation.org; linux-...@vger.kernel.org; > linux-kernel@vger.kernel.org > Subject: RE: USB GADGET: have a question about usb2eth

RE: USB GADGET: have a question about usb2eth

> -Original Message- > From: Felipe Balbi [mailto:ba...@kernel.org] > Sent: Monday, October 17, 2016 5:29 PM > To: Lipengcheng; Peter Chen > Cc: gre...@linuxfoundation.org; linux-...@vger.kernel.org; > linux-kernel@vger.kernel.org > Subject: RE: USB GADGET: have a question about usb2eth

Re: [PATCH] MAINTAINERS: mmc: Move the mmc tree to kernel.org

Hi Ulf, On 2016/10/17 20:54, Ulf Hansson wrote: Signed-off-by: Ulf Hansson --- MAINTAINERS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index a009e00..e685724 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -8164,7 +8164,7

Re: [PATCH] MAINTAINERS: mmc: Move the mmc tree to kernel.org

Hi Ulf, On 2016/10/17 20:54, Ulf Hansson wrote: Signed-off-by: Ulf Hansson --- MAINTAINERS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index a009e00..e685724 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -8164,7 +8164,7 @@ F:

Re: [PATCH v5 2/3] z3fold: remove redundant locking

On Mon, Oct 17, 2016 at 10:48 PM, Dan Streetman wrote: > On Sat, Oct 15, 2016 at 7:59 AM, Vitaly Wool wrote: >> The per-pool z3fold spinlock should generally be taken only when >> a non-atomic pool variable is modified. There's no need to take it >> to

Re: [PATCH v5 2/3] z3fold: remove redundant locking

On Mon, Oct 17, 2016 at 10:48 PM, Dan Streetman wrote: > On Sat, Oct 15, 2016 at 7:59 AM, Vitaly Wool wrote: >> The per-pool z3fold spinlock should generally be taken only when >> a non-atomic pool variable is modified. There's no need to take it >> to map/unmap an object. > > no. it absolutely

Re: [PATCH v2] MAINTAINERS: add myself as Marvell berlin SoC maintainer

On Thu, Sep 29, 2016 at 06:51:20PM +0800, Jisheng Zhang wrote: > I would like to take maintainership for Marvell berlin SoCs. > > Signed-off-by: Jisheng Zhang > Acked-by: Sebastian Hesselbarth Applied to fixes. Thanks. -Olof

Re: [PATCH v2] MAINTAINERS: add myself as Marvell berlin SoC maintainer

On Thu, Sep 29, 2016 at 06:51:20PM +0800, Jisheng Zhang wrote: > I would like to take maintainership for Marvell berlin SoCs. > > Signed-off-by: Jisheng Zhang > Acked-by: Sebastian Hesselbarth Applied to fixes. Thanks. -Olof

Re: [PATCH vmalloc] reduce purge_lock range and hold time of

hey Hellwig: cond_resched_lock is a good choice. i mixed the cond_resched_lock and batch to balance of realtime and performance and resubmit this patch. On 2016/10/16 0:55, Christoph Hellwig wrote: On Sat, Oct 15, 2016 at 10:12:48PM +0800, zhouxianr...@huawei.com wrote: From:

Re: [PATCH vmalloc] reduce purge_lock range and hold time of

hey Hellwig: cond_resched_lock is a good choice. i mixed the cond_resched_lock and batch to balance of realtime and performance and resubmit this patch. On 2016/10/16 0:55, Christoph Hellwig wrote: On Sat, Oct 15, 2016 at 10:12:48PM +0800, zhouxianr...@huawei.com wrote: From:

Re: [PATCH v2 1/2] watchdog: Introduce arch_watchdog_nmi_enable and arch_watchdog_nmi_disable

Don, On 10/17/2016 12:31 PM, Don Zickus wrote: On Thu, Oct 13, 2016 at 01:38:01PM -0700, Babu Moger wrote: Currently we do not have a way to enable/disable arch specific watchdog handlers if it was implemented by any of the architectures. This patch introduces new functions

Re: [PATCH v2 1/2] watchdog: Introduce arch_watchdog_nmi_enable and arch_watchdog_nmi_disable

Don, On 10/17/2016 12:31 PM, Don Zickus wrote: On Thu, Oct 13, 2016 at 01:38:01PM -0700, Babu Moger wrote: Currently we do not have a way to enable/disable arch specific watchdog handlers if it was implemented by any of the architectures. This patch introduces new functions

Re: [PATCH v5 3/3] z3fold: add shrinker

Hi Dan, On Tue, Oct 18, 2016 at 4:06 AM, Dan Streetman wrote: > On Sat, Oct 15, 2016 at 8:05 AM, Vitaly Wool wrote: >> This patch implements shrinker for z3fold. This shrinker >> implementation does not free up any pages directly but it allows >> for a

Re: [PATCH v5 3/3] z3fold: add shrinker

Hi Dan, On Tue, Oct 18, 2016 at 4:06 AM, Dan Streetman wrote: > On Sat, Oct 15, 2016 at 8:05 AM, Vitaly Wool wrote: >> This patch implements shrinker for z3fold. This shrinker >> implementation does not free up any pages directly but it allows >> for a denser placement of compressed objects

Re: [PATCH v4] usb: dwc3: Wait for control tranfer completed when stopping gadget

Hi, On 17 October 2016 at 19:53, Felipe Balbi wrote: > > Hi, > > Baolin Wang writes: >>> Baolin Wang writes: When we change the USB function with configfs dynamically, we possibly met this situation: one core is

Re: [PATCH v4] usb: dwc3: Wait for control tranfer completed when stopping gadget

Hi, On 17 October 2016 at 19:53, Felipe Balbi wrote: > > Hi, > > Baolin Wang writes: >>> Baolin Wang writes: When we change the USB function with configfs dynamically, we possibly met this situation: one core is doing the control transfer, another core is trying to

Re: Oops on Power8 (was Re: [PATCH v2 1/7] workqueue: make workqueue available early during boot)

Balbir Singh writes: > On 17/10/16 23:24, Michael Ellerman wrote: >> That happened because we haven't yet called set_cpu_numa_node() for the >> non-boot >> cpus, because that happens in smp_prepare_cpus(), and >> workqueue_init_early() is called much earlier than that. >>

Re: Oops on Power8 (was Re: [PATCH v2 1/7] workqueue: make workqueue available early during boot)

Balbir Singh writes: > On 17/10/16 23:24, Michael Ellerman wrote: >> That happened because we haven't yet called set_cpu_numa_node() for the >> non-boot >> cpus, because that happens in smp_prepare_cpus(), and >> workqueue_init_early() is called much earlier than that. >> >> This doesn't

[PATCH vmalloc] reduce purge_lock range and hold time of vmap_area_lock

From: z00281421 Signed-off-by: z00281421 --- mm/vmalloc.c |9 +++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/mm/vmalloc.c b/mm/vmalloc.c index 91f44e7..e9c9c04 100644 --- a/mm/vmalloc.c +++

[PATCH vmalloc] reduce purge_lock range and hold time of vmap_area_lock

From: z00281421 Signed-off-by: z00281421 --- mm/vmalloc.c |9 +++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/mm/vmalloc.c b/mm/vmalloc.c index 91f44e7..e9c9c04 100644 --- a/mm/vmalloc.c +++ b/mm/vmalloc.c @@ -661,13 +661,18 @@ static void

Re: [PATCH] staging: dgnc: Replace CamelCase namings with underscores.

On Mon, Oct 17, 2016 at 1:16 PM, Greg KH wrote: > > On Mon, Oct 17, 2016 at 01:13:55AM +0530, Pankaj Bharadiya wrote: > > Replace CamelCase names with underscores to comply with the standard > > kernel coding style. > > > > Signed-off-by: Pankaj Bharadiya

Re: [PATCH] staging: dgnc: Replace CamelCase namings with underscores.

On Mon, Oct 17, 2016 at 1:16 PM, Greg KH wrote: > > On Mon, Oct 17, 2016 at 01:13:55AM +0530, Pankaj Bharadiya wrote: > > Replace CamelCase names with underscores to comply with the standard > > kernel coding style. > > > > Signed-off-by: Pankaj Bharadiya > > --- > >

linux-next: Tree for Oct 18

Hi all, Changes since 20161017: The drm-intel tree gained build failures so I used the version from next-20161017. The akpm-current tree still had its build failures for which I applied 2 patches. Non-merge commits (relative to Linus' tree): 910 1213 files changed, 32579 insertions(+), 17418

linux-next: Tree for Oct 18

Hi all, Changes since 20161017: The drm-intel tree gained build failures so I used the version from next-20161017. The akpm-current tree still had its build failures for which I applied 2 patches. Non-merge commits (relative to Linus' tree): 910 1213 files changed, 32579 insertions(+), 17418

Re: [PATCH v3] time: alarmtimer: Add the trcepoints for alarmtimer

On 18 October 2016 at 03:03, Steven Rostedt wrote: > On Tue, 11 Oct 2016 18:48:16 +0800 > Baolin Wang wrote: > >> --- >> Changes since v2: >> - Save time as s64 type. >> - Remove 'process_name' parameter and add 'now' parameter. >> - Rename the

Re: [PATCH v3] time: alarmtimer: Add the trcepoints for alarmtimer

On 18 October 2016 at 03:03, Steven Rostedt wrote: > On Tue, 11 Oct 2016 18:48:16 +0800 > Baolin Wang wrote: > >> --- >> Changes since v2: >> - Save time as s64 type. >> - Remove 'process_name' parameter and add 'now' parameter. >> - Rename the trace event name. >> - Remove restart trace

Re: [PATCH 2/2] builddeb: allow building without headers/firmware packages

On 26/08/16 18:17, Andrew Donnellan wrote: Currently, the deb-pkg and bindeb-pkg targets create multiple packages for the kernel binaries, headers, userspace headers and firmware. For developers who generate Debian packages as part of their development workflows, it's often not necessary to

Re: [PATCH 2/2] builddeb: allow building without headers/firmware packages

On 26/08/16 18:17, Andrew Donnellan wrote: Currently, the deb-pkg and bindeb-pkg targets create multiple packages for the kernel binaries, headers, userspace headers and firmware. For developers who generate Debian packages as part of their development workflows, it's often not necessary to

Re: [PATCH 07/28] ceph: avoid false positive maybe-uninitialized warning

> On 18 Oct 2016, at 06:08, Arnd Bergmann wrote: > > A recent rework removed the initialization of the local 'root' > variable that is returned from ceph_real_mount: > > fs/ceph/super.c: In function 'ceph_mount': > fs/ceph/super.c:1016:38: error: 'root' may be used uninitialized

Re: [PATCH 07/28] ceph: avoid false positive maybe-uninitialized warning

> On 18 Oct 2016, at 06:08, Arnd Bergmann wrote: > > A recent rework removed the initialization of the local 'root' > variable that is returned from ceph_real_mount: > > fs/ceph/super.c: In function 'ceph_mount': > fs/ceph/super.c:1016:38: error: 'root' may be used uninitialized in this >

Re: [PATCH v5 3/3] z3fold: add shrinker

On Sat, Oct 15, 2016 at 8:05 AM, Vitaly Wool wrote: > This patch implements shrinker for z3fold. This shrinker > implementation does not free up any pages directly but it allows > for a denser placement of compressed objects which results in > less actual pages consumed and

Re: [PATCH v5 3/3] z3fold: add shrinker

On Sat, Oct 15, 2016 at 8:05 AM, Vitaly Wool wrote: > This patch implements shrinker for z3fold. This shrinker > implementation does not free up any pages directly but it allows > for a denser placement of compressed objects which results in > less actual pages consumed and higher compression

[PATCH v5 02/23] of: device: Export of_device_{get_modalias,uvent_modalias} to modules

The ULPI bus can be built as a module, and it will soon be calling these functions when it supports probing devices from DT. Export them so they can be used by the ULPI module. Acked-by: Rob Herring Cc: Signed-off-by: Stephen Boyd

[PATCH v5 02/23] of: device: Export of_device_{get_modalias,uvent_modalias} to modules

The ULPI bus can be built as a module, and it will soon be calling these functions when it supports probing devices from DT. Export them so they can be used by the ULPI module. Acked-by: Rob Herring Cc: Signed-off-by: Stephen Boyd --- drivers/of/device.c | 2 ++ 1 file changed, 2

[PATCH v5 03/23] usb: ulpi: Support device discovery via DT

The qcom HSIC ULPI phy doesn't have any bits set in the vendor or product ID registers. This makes it impossible to make a ULPI driver match against the ID registers. Add support to discover the ULPI phys via DT help alleviate this problem. In the DT case, we'll look for a ULPI bus node underneath

[PATCH v5 03/23] usb: ulpi: Support device discovery via DT

The qcom HSIC ULPI phy doesn't have any bits set in the vendor or product ID registers. This makes it impossible to make a ULPI driver match against the ID registers. Add support to discover the ULPI phys via DT help alleviate this problem. In the DT case, we'll look for a ULPI bus node underneath

[PATCH v5 10/23] usb: chipidea: Consolidate extcon notifiers

The two extcon notifiers are almost the same except for the variable name for the cable structure and the id notifier inverts the cable->state logic. Make it the same and replace two functions with one to save some lines. This also makes it so that the id cable state is true when the id pin is

[PATCH v5 10/23] usb: chipidea: Consolidate extcon notifiers

The two extcon notifiers are almost the same except for the variable name for the cable structure and the id notifier inverts the cable->state logic. Make it the same and replace two functions with one to save some lines. This also makes it so that the id cable state is true when the id pin is

[PATCH v5 16/23] usb: chipidea: msm: Mux over secondary phy at the right time

We need to pick the correct phy at runtime based on how the SoC has been wired onto the board. If the secondary phy is used, take it out of reset and mux over to it by writing into the TCSR register. Make sure to do this on reset too, because this register is reset to the default value (primary

[PATCH v5 13/23] usb: chipidea: msm: Rely on core to override AHBBURST

The core framework already handles setting this parameter with a platform quirk. Add the appropriate flag so that we always set AHBBURST to 0. Technically DT should be doing this, but we always do it for msm chipidea devices so setting the flag in the driver works just as well. If the burst needs

  1   2   3   4   5   6   7   8   9   10   >