[PATCH] tools: Fix str_error_r() Werror=restrict build

Commit c8b5f2c96d1bf6c ("tools: Introduce str_error_r()") added an str_error_r() wrapper which makes gcc8 unhappy due to restrict-qualified parameter aliasing violation: ../lib/str_error_r.c: In function ‘str_error_r’: ../lib/str_error_r.c:25:3: error: passing argument 1 to restrict-qualified

[PATCH] tools: Fix str_error_r() Werror=restrict build

Commit c8b5f2c96d1bf6c ("tools: Introduce str_error_r()") added an str_error_r() wrapper which makes gcc8 unhappy due to restrict-qualified parameter aliasing violation: ../lib/str_error_r.c: In function ‘str_error_r’: ../lib/str_error_r.c:25:3: error: passing argument 1 to restrict-qualified

RE: [PATCH] vmbus: use put_device() if device_register fail

> -Original Message- > From: Michael Kelley (EOSG) > Sent: Sunday, March 18, 2018 8:40 PM > To: KY Srinivasan ; Arvind Yadav > ; Stephen Hemminger > ; Haiyang Zhang > Cc:

RE: [PATCH] vmbus: use put_device() if device_register fail

> -Original Message- > From: Michael Kelley (EOSG) > Sent: Sunday, March 18, 2018 8:40 PM > To: KY Srinivasan ; Arvind Yadav > ; Stephen Hemminger > ; Haiyang Zhang > Cc: de...@linuxdriverproject.org; linux-kernel@vger.kernel.org > Subject: RE: [PATCH] vmbus: use put_device() if

Re: [PATCH 1/3] x86, pkeys: do not special case protection key 0

Dave Hansen writes: > On 03/17/2018 02:12 AM, Thomas Gleixner wrote: >>> This is a bit nicer than what Ram proposed because it is simpler >>> and removes special-casing for pkey 0. On the other hand, it does >>> allow applciations to pkey_free() pkey-0, but that's just a

Re: [PATCH 1/3] x86, pkeys: do not special case protection key 0

Dave Hansen writes: > On 03/17/2018 02:12 AM, Thomas Gleixner wrote: >>> This is a bit nicer than what Ram proposed because it is simpler >>> and removes special-casing for pkey 0. On the other hand, it does >>> allow applciations to pkey_free() pkey-0, but that's just a silly >>> thing to do,

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

On 19-03-2018 06:34, Stephen Rothwell wrote: > Hi Herbert, > > After merging the crypto tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > In file included from drivers/crypto/chelsio/chcr_ipsec.c:66:0: > drivers/crypto/chelsio/chcr_crypto.h:343:12: warning:

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

On 19-03-2018 06:34, Stephen Rothwell wrote: > Hi Herbert, > > After merging the crypto tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > In file included from drivers/crypto/chelsio/chcr_ipsec.c:66:0: > drivers/crypto/chelsio/chcr_crypto.h:343:12: warning:

Re: [PATCH 4.15 000/128] 4.15.11-stable review

On 03/18/2018 08:39 PM, Dan Rue wrote: On Sun, Mar 18, 2018 at 12:15:23PM +0100, Greg Kroah-Hartman wrote: On Sun, Mar 18, 2018 at 11:25:26AM +0100, Greg Kroah-Hartman wrote: On Fri, Mar 16, 2018 at 04:22:21PM +0100, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for

Re: [PATCH 4.15 000/128] 4.15.11-stable review

On 03/18/2018 08:39 PM, Dan Rue wrote: On Sun, Mar 18, 2018 at 12:15:23PM +0100, Greg Kroah-Hartman wrote: On Sun, Mar 18, 2018 at 11:25:26AM +0100, Greg Kroah-Hartman wrote: On Fri, Mar 16, 2018 at 04:22:21PM +0100, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for

[PATCH v2] staging: media: davinci_vpfe: add error handling on kmalloc failure

There is no failure checking on the param value which will be allocated memory by kmalloc. Add a null pointer checking statement. Then goto error: and return -ENOMEM error code when kmalloc is failed. Signed-off-by: Ji-Hun Kim --- Changes since v1: - Return with -ENOMEM

[PATCH v2] staging: media: davinci_vpfe: add error handling on kmalloc failure

There is no failure checking on the param value which will be allocated memory by kmalloc. Add a null pointer checking statement. Then goto error: and return -ENOMEM error code when kmalloc is failed. Signed-off-by: Ji-Hun Kim --- Changes since v1: - Return with -ENOMEM directly, instead of

RE: [PATCH v2 10/21] lightnvm: Remove depends on HAS_DMA in case of platform dependency

> -Original Message- > From: netdev-ow...@vger.kernel.org [mailto:netdev-ow...@vger.kernel.org] > On Behalf Of Geert Uytterhoeven > Sent: Friday, March 16, 2018 3:52 PM > To: Christoph Hellwig ; Marek Szyprowski > ; Robin Murphy

RE: [PATCH v2 10/21] lightnvm: Remove depends on HAS_DMA in case of platform dependency

> -Original Message- > From: netdev-ow...@vger.kernel.org [mailto:netdev-ow...@vger.kernel.org] > On Behalf Of Geert Uytterhoeven > Sent: Friday, March 16, 2018 3:52 PM > To: Christoph Hellwig ; Marek Szyprowski > ; Robin Murphy ; > Felipe Balbi ; Greg Kroah-Hartman > ; James E . J .

[PATCH] gpu: drm: Use list_{next/prev}_entry instead of list_entry

This patch replace list_entry with list_{next/prev}_entry as it makes the code more clear to read. Done using coccinelle: @@ expression e1; identifier e3; type t; @@ ( - list_entry(e1->e3.next,t,e3) + list_next_entry(e1,e3) | - list_entry(e1->e3.prev,t,e3) + list_prev_entry(e1,e3) )

[PATCH] gpu: drm: Use list_{next/prev}_entry instead of list_entry

This patch replace list_entry with list_{next/prev}_entry as it makes the code more clear to read. Done using coccinelle: @@ expression e1; identifier e3; type t; @@ ( - list_entry(e1->e3.next,t,e3) + list_next_entry(e1,e3) | - list_entry(e1->e3.prev,t,e3) + list_prev_entry(e1,e3) )

Re: [PATCH 1/2] x86, msr: add rdmsr_safe_on_cpu_resched() and use it in msr_read()

On Sun, Mar 18, 2018 at 10:14 AM kbuild test robot wrote: > Hi Eric, > Thank you for the patch! Yet something to improve: > [auto build test ERROR on linus/master] > [also build test ERROR on v4.16-rc5 next-20180316] > [if your patch is applied to the wrong git tree, please

Re: [PATCH 1/2] x86, msr: add rdmsr_safe_on_cpu_resched() and use it in msr_read()

On Sun, Mar 18, 2018 at 10:14 AM kbuild test robot wrote: > Hi Eric, > Thank you for the patch! Yet something to improve: > [auto build test ERROR on linus/master] > [also build test ERROR on v4.16-rc5 next-20180316] > [if your patch is applied to the wrong git tree, please drop us a note to

Re: [PATCH v2] exec: Set file unwritable before LSM check

On Fri, 9 Mar 2018, Kees Cook wrote: > The LSM check should happen after the file has been confirmed to be > unchanging. Without this, we could have a race between the Time of Check > (the call to security_kernel_read_file() which could read the file and > make access policy decisions) and the

Re: [PATCH v2] exec: Set file unwritable before LSM check

On Fri, 9 Mar 2018, Kees Cook wrote: > The LSM check should happen after the file has been confirmed to be > unchanging. Without this, we could have a race between the Time of Check > (the call to security_kernel_read_file() which could read the file and > make access policy decisions) and the

Re: [PATCH 5/6] dt-bindings: phy-qcom-usb2: Update bindings for sdm845

Hi, On 3/18/2018 6:22 PM, Rob Herring wrote: > On Fri, Mar 16, 2018 at 03:14:58PM +0530, Manu Gautam wrote: >> Update compatible strings for USB2 PHYs on sdm845. >> There are two QUSB2 PHYs present on sdm845. Few PHY registers >> programming is different for these PHYs related to electrical >>

Re: [PATCH 5/6] dt-bindings: phy-qcom-usb2: Update bindings for sdm845

Hi, On 3/18/2018 6:22 PM, Rob Herring wrote: > On Fri, Mar 16, 2018 at 03:14:58PM +0530, Manu Gautam wrote: >> Update compatible strings for USB2 PHYs on sdm845. >> There are two QUSB2 PHYs present on sdm845. Few PHY registers >> programming is different for these PHYs related to electrical >>

Re: [PATCH v2 3/4] arm64: Implement page table free interfaces

On 3/15/2018 6:48 PM, Mark Rutland wrote: On Thu, Mar 15, 2018 at 06:15:05PM +0530, Chintan Pandya wrote: Implement pud_free_pmd_page() and pmd_free_pte_page(). Make sure, that they are indeed a page table before taking them to free. As mentioned on the prior patch, if the tables we're

Re: [PATCH v2 3/4] arm64: Implement page table free interfaces

On 3/15/2018 6:48 PM, Mark Rutland wrote: On Thu, Mar 15, 2018 at 06:15:05PM +0530, Chintan Pandya wrote: Implement pud_free_pmd_page() and pmd_free_pte_page(). Make sure, that they are indeed a page table before taking them to free. As mentioned on the prior patch, if the tables we're

Re: [PATCH 5/8] trace_uprobe: Support SDT markers having reference count (semaphore)

Hi Oleg, On 03/14/2018 10:29 PM, Oleg Nesterov wrote: > On 03/13, Ravi Bangoria wrote: >> +static bool sdt_valid_vma(struct trace_uprobe *tu, struct vm_area_struct >> *vma) >> +{ >> +unsigned long vaddr = vma_offset_to_vaddr(vma, tu->ref_ctr_offset); >> + >> +return tu->ref_ctr_offset &&

Re: [PATCH v2 2/4] ioremap: Implement TLB_INV before huge mapping

On 3/16/2018 8:20 PM, Kani, Toshi wrote: On Fri, 2018-03-16 at 13:10 +0530, Chintan Pandya wrote: On 3/15/2018 9:42 PM, Kani, Toshi wrote: On Thu, 2018-03-15 at 18:15 +0530, Chintan Pandya wrote: Huge mapping changes PMD/PUD which could have valid previous entries. This requires proper TLB

Re: [PATCH v2 2/4] ioremap: Implement TLB_INV before huge mapping

On 3/16/2018 8:20 PM, Kani, Toshi wrote: On Fri, 2018-03-16 at 13:10 +0530, Chintan Pandya wrote: On 3/15/2018 9:42 PM, Kani, Toshi wrote: On Thu, 2018-03-15 at 18:15 +0530, Chintan Pandya wrote: Huge mapping changes PMD/PUD which could have valid previous entries. This requires proper TLB

Re: [PATCH 5/8] trace_uprobe: Support SDT markers having reference count (semaphore)

Hi Oleg, On 03/14/2018 10:29 PM, Oleg Nesterov wrote: > On 03/13, Ravi Bangoria wrote: >> +static bool sdt_valid_vma(struct trace_uprobe *tu, struct vm_area_struct >> *vma) >> +{ >> +unsigned long vaddr = vma_offset_to_vaddr(vma, tu->ref_ctr_offset); >> + >> +return tu->ref_ctr_offset &&

Re: [PATCH 19/19] irqchip: add irq-nationalchip.c and irq-csky.c

On Mon, Mar 19, 2018 at 03:51:41AM +0800, Guo Ren wrote: > +static unsigned int intc_reg; This should be a void __iomem *ptr; > + > +#define CK_VA_INTC_ICR (void *)(intc_reg + 0x00) /* > Interrupt control register(High 16bits) */ > +#define CK_VA_INTC_ISR (void

Re: [PATCH 19/19] irqchip: add irq-nationalchip.c and irq-csky.c

On Mon, Mar 19, 2018 at 03:51:41AM +0800, Guo Ren wrote: > +static unsigned int intc_reg; This should be a void __iomem *ptr; > + > +#define CK_VA_INTC_ICR (void *)(intc_reg + 0x00) /* > Interrupt control register(High 16bits) */ > +#define CK_VA_INTC_ISR (void

Re: Re: [PATCH] staging: media: davinci_vpfe: add error handling on kmalloc failure

On Fri, Mar 16, 2018 at 11:32:34AM +0300, Dan Carpenter wrote: > On Fri, Mar 16, 2018 at 01:58:23PM +0900, Ji-Hun Kim wrote: > > There is no failure checking on the param value which will be allocated > > memory by kmalloc. Add a null pointer checking statement. Then goto error: > > and return

Re: Re: [PATCH] staging: media: davinci_vpfe: add error handling on kmalloc failure

On Fri, Mar 16, 2018 at 11:32:34AM +0300, Dan Carpenter wrote: > On Fri, Mar 16, 2018 at 01:58:23PM +0900, Ji-Hun Kim wrote: > > There is no failure checking on the param value which will be allocated > > memory by kmalloc. Add a null pointer checking statement. Then goto error: > > and return

Re: [RFC PATCH 4/6] mm: provide generic compat_sys_readahead() implementation

On Sun, Mar 18, 2018 at 06:18:48PM +, Al Viro wrote: > I'd done some digging in that area, will find the notes and post. OK, found: We have two ABIs in the game - syscall and normal C. The latter (for all targets we support) can be described in the following terms: * there is a

Re: [RFC PATCH 4/6] mm: provide generic compat_sys_readahead() implementation

On Sun, Mar 18, 2018 at 06:18:48PM +, Al Viro wrote: > I'd done some digging in that area, will find the notes and post. OK, found: We have two ABIs in the game - syscall and normal C. The latter (for all targets we support) can be described in the following terms: * there is a

Re: [PATCH v1 1/2] dt-bindings: usb: Update documentation for Qualcomm DWC3 driver

Hi, On 3/18/2018 6:19 PM, Rob Herring wrote: > On Tue, Mar 13, 2018 at 04:06:00PM +0530, Manu Gautam wrote: >> Existing documentation has lot of incorrect information as it >> was originally added for a driver that no longer exists. >> >> Signed-off-by: Manu Gautam >>

Re: [PATCH v1 1/2] dt-bindings: usb: Update documentation for Qualcomm DWC3 driver

Hi, On 3/18/2018 6:19 PM, Rob Herring wrote: > On Tue, Mar 13, 2018 at 04:06:00PM +0530, Manu Gautam wrote: >> Existing documentation has lot of incorrect information as it >> was originally added for a driver that no longer exists. >> >> Signed-off-by: Manu Gautam >> --- >>

Re: [PATCH] ASoC: uniphier: evea: add switch for changing source of line-in

Hello Mark, > -Original Message- > From: Mark Brown [mailto:broo...@kernel.org] > Sent: Thursday, March 15, 2018 1:26 AM > To: Suzuki, Katsuhiro > Cc: alsa-de...@alsa-project.org; Masami Hiramatsu ; > Jassi Brar

Re: [PATCH] ASoC: uniphier: evea: add switch for changing source of line-in

Hello Mark, > -Original Message- > From: Mark Brown [mailto:broo...@kernel.org] > Sent: Thursday, March 15, 2018 1:26 AM > To: Suzuki, Katsuhiro > Cc: alsa-de...@alsa-project.org; Masami Hiramatsu ; > Jassi Brar ; linux-arm-ker...@lists.infradead.org; > linux-kernel@vger.kernel.org >

Re: [PATCH 18/19] clocksource: add timer-nationalchip.c

Hi, On Mon, Mar 19, 2018 at 03:51:40AM +0800, Guo Ren wrote: > +#define NC_VA_COUNTER_1_STATUS (void *)(timer_reg + 0x00) > +#define NC_VA_COUNTER_1_VALUE(void *)(timer_reg + 0x04) > +#define NC_VA_COUNTER_1_CONTROL (void *)(timer_reg + 0x10) > +#define

Re: [PATCH 18/19] clocksource: add timer-nationalchip.c

Hi, On Mon, Mar 19, 2018 at 03:51:40AM +0800, Guo Ren wrote: > +#define NC_VA_COUNTER_1_STATUS (void *)(timer_reg + 0x00) > +#define NC_VA_COUNTER_1_VALUE(void *)(timer_reg + 0x04) > +#define NC_VA_COUNTER_1_CONTROL (void *)(timer_reg + 0x10) > +#define

[PATCH][v4] PM / sleep: Do not delay the synchronization of MTRR during resume

From: Chen Yu Sometimes it is too late for the APs to adjust their MTRRs to the valid ones saved before suspend - currently this action is performed by set_mtrr_state() after all the APs have been brought up. In some cases the BIOS might scribble the MTRR across suspend, as

[PATCH][v4] PM / sleep: Do not delay the synchronization of MTRR during resume

From: Chen Yu Sometimes it is too late for the APs to adjust their MTRRs to the valid ones saved before suspend - currently this action is performed by set_mtrr_state() after all the APs have been brought up. In some cases the BIOS might scribble the MTRR across suspend, as a result we might get

Re: Intel GemniLake xHCI connected devices can never wake up the system from suspend

On Mon, Mar 19, 2018 at 6:36 AM, Rafael J. Wysocki wrote: > On Fri, Mar 16, 2018 at 10:06 AM, Mathias Nyman > wrote: >> Adding Rafael directly to CC >> >> In short, if _S3D and _S3W are missing in DSDT then a PCI device >> stays in D0 during

Re: Intel GemniLake xHCI connected devices can never wake up the system from suspend

On Mon, Mar 19, 2018 at 6:36 AM, Rafael J. Wysocki wrote: > On Fri, Mar 16, 2018 at 10:06 AM, Mathias Nyman > wrote: >> Adding Rafael directly to CC >> >> In short, if _S3D and _S3W are missing in DSDT then a PCI device >> stays in D0 during suspend in Linux, but goes to D3 in Windows. >> >> USB

Re: [PATCH v5 3/4] clk: lpc32xx: Set name of regmap_config

Hi Vladimir, On 03/19/2018 05:57 AM, Vladimir Zapolskiy wrote: > static struct regmap_config lpc32xx_scb_regmap_config = { >+ .name = "lpc32xx-scb", please rename it to "scb", LPC32xx SoC name is already known from the context. When it's done, feel free to add to the next version my

Re: [PATCH v5 3/4] clk: lpc32xx: Set name of regmap_config

Hi Vladimir, On 03/19/2018 05:57 AM, Vladimir Zapolskiy wrote: > static struct regmap_config lpc32xx_scb_regmap_config = { >+ .name = "lpc32xx-scb", please rename it to "scb", LPC32xx SoC name is already known from the context. When it's done, feel free to add to the next version my

[PATCH v6] clk: lpc32xx: Set name of regmap_config

We are now allowing to register debugfs without a valid device, and not having a valid name will end up using "dummy*" to create debugfs dir. Signed-off-by: Jeffy Chen Acked-by: Vladimir Zapolskiy --- Changes in v6: Modify name as Vladimir suggested.

[PATCH v6] clk: lpc32xx: Set name of regmap_config

We are now allowing to register debugfs without a valid device, and not having a valid name will end up using "dummy*" to create debugfs dir. Signed-off-by: Jeffy Chen Acked-by: Vladimir Zapolskiy --- Changes in v6: Modify name as Vladimir suggested. drivers/clk/nxp/clk-lpc32xx.c | 1 + 1

Re: linux-next: manual merge of the kvms390 tree with the nds32 tree

Hi all, On Mon, 26 Feb 2018 13:34:45 +1100 Stephen Rothwell wrote: > > Today's linux-next merge of the kvms390 tree got a conflict in: > > drivers/video/console/Kconfig > > between commit: > > 2312dbf7462b ("drivers/video/concole: add negative dependency for >

[PATCH 1/2] staging: typec: rt1711h typec chip driver

From: ShuFan Lee Richtek RT1711H Type-C chip driver that works with Type-C Port Controller Manager to provide USB PD and USB Type-C functionalities. Add definition of TCPC_CC_STATUS_TOGGLING. Signed-off-by: ShuFan Lee ---

[PATCH 1/2] staging: typec: rt1711h typec chip driver

From: ShuFan Lee Richtek RT1711H Type-C chip driver that works with Type-C Port Controller Manager to provide USB PD and USB Type-C functionalities. Add definition of TCPC_CC_STATUS_TOGGLING. Signed-off-by: ShuFan Lee --- drivers/staging/typec/Kconfig | 8 +

Re: linux-next: manual merge of the kvms390 tree with the nds32 tree

Hi all, On Mon, 26 Feb 2018 13:34:45 +1100 Stephen Rothwell wrote: > > Today's linux-next merge of the kvms390 tree got a conflict in: > > drivers/video/console/Kconfig > > between commit: > > 2312dbf7462b ("drivers/video/concole: add negative dependency for > VGA_CONSOLE on nds32") >

[PATCH 0/2] staging: typec: rt1711h typec driver and dt-bindings

From: ShuFan Lee This patch series add rt1711h typec chip driver and dt-bindings changelogs between v1 & v2 - use gpiod_* instead of gpio_* changelogs between v2 & v3 - add dt-bindings for rt1711h typec driver ShuFan Lee (2): staging: typec: rt1711h typec chip driver

[PATCH 2/2] dt-bindings: usb: rt1711h device tree binding document

From: ShuFan Lee Add device tree binding document for Richtek RT1711H Type-C chip driver Signed-off-by: ShuFan Lee --- .../devicetree/bindings/usb/richtek,rt1711h.txt| 30 ++ 1 file changed, 30 insertions(+) create mode

[PATCH 0/2] staging: typec: rt1711h typec driver and dt-bindings

From: ShuFan Lee This patch series add rt1711h typec chip driver and dt-bindings changelogs between v1 & v2 - use gpiod_* instead of gpio_* changelogs between v2 & v3 - add dt-bindings for rt1711h typec driver ShuFan Lee (2): staging: typec: rt1711h typec chip driver dt-bindings: usb:

[PATCH 2/2] dt-bindings: usb: rt1711h device tree binding document

From: ShuFan Lee Add device tree binding document for Richtek RT1711H Type-C chip driver Signed-off-by: ShuFan Lee --- .../devicetree/bindings/usb/richtek,rt1711h.txt| 30 ++ 1 file changed, 30 insertions(+) create mode 100644

Re: [PATCH 4.14 056/109] clk: ti: clkctrl: add support for retrying failed init

On Fri, Mar 16, 2018 at 04:23:25PM +0100, Greg Kroah-Hartman wrote: > 4.14-stable review patch. If anyone has any objections, please let me know. > > -- > > From: Tero Kristo > > > [ Upstream commit 729e13bf58e643b9accd2a14c55b555958702fb0 ] > > In case the

Re: [PATCH 1/2] pci: host: pci-hyperv: Replace GFP_ATOMIC with GFP_KERNEL in hv_pci_onchannelcallback

On 2018/3/19 10:52, KY Srinivasan wrote: -Original Message- From: Jia-Ju Bai Sent: Sunday, March 18, 2018 7:53 AM To: KY Srinivasan ; Haiyang Zhang ; Stephen Hemminger ; bhelg...@google.com

Re: [PATCH 4.14 056/109] clk: ti: clkctrl: add support for retrying failed init

On Fri, Mar 16, 2018 at 04:23:25PM +0100, Greg Kroah-Hartman wrote: > 4.14-stable review patch. If anyone has any objections, please let me know. > > -- > > From: Tero Kristo > > > [ Upstream commit 729e13bf58e643b9accd2a14c55b555958702fb0 ] > > In case the clkctrl node

Re: [PATCH 1/2] pci: host: pci-hyperv: Replace GFP_ATOMIC with GFP_KERNEL in hv_pci_onchannelcallback

On 2018/3/19 10:52, KY Srinivasan wrote: -Original Message- From: Jia-Ju Bai Sent: Sunday, March 18, 2018 7:53 AM To: KY Srinivasan ; Haiyang Zhang ; Stephen Hemminger ; bhelg...@google.com Cc: de...@linuxdriverproject.org; linux-...@vger.kernel.org; linux- ker...@vger.kernel.org;

RE: [PATCH] vmbus: use put_device() if device_register fail

> -Original Message- > From: linux-kernel-ow...@vger.kernel.org > On Behalf > Of KY Srinivasan > Sent: Sunday, March 18, 2018 8:02 PM > To: Arvind Yadav ; Stephen Hemminger > ; Haiyang Zhang

RE: [PATCH] vmbus: use put_device() if device_register fail

> -Original Message- > From: linux-kernel-ow...@vger.kernel.org > On Behalf > Of KY Srinivasan > Sent: Sunday, March 18, 2018 8:02 PM > To: Arvind Yadav ; Stephen Hemminger > ; Haiyang Zhang > Cc: de...@linuxdriverproject.org; linux-kernel@vger.kernel.org > Subject: RE: [PATCH] vmbus:

Re: [PATCH 4.15 000/128] 4.15.11-stable review

On Sun, Mar 18, 2018 at 12:15:23PM +0100, Greg Kroah-Hartman wrote: > On Sun, Mar 18, 2018 at 11:25:26AM +0100, Greg Kroah-Hartman wrote: > > On Fri, Mar 16, 2018 at 04:22:21PM +0100, Greg Kroah-Hartman wrote: > > > This is the start of the stable review cycle for the 4.15.11 release. > > > There

Re: [PATCH 4.15 000/128] 4.15.11-stable review

On Sun, Mar 18, 2018 at 12:15:23PM +0100, Greg Kroah-Hartman wrote: > On Sun, Mar 18, 2018 at 11:25:26AM +0100, Greg Kroah-Hartman wrote: > > On Fri, Mar 16, 2018 at 04:22:21PM +0100, Greg Kroah-Hartman wrote: > > > This is the start of the stable review cycle for the 4.15.11 release. > > > There

Re: [PATCH v2 3/3] dt-bindings: phy-mtk-tphy: add properties for U2 slew rate calibrate

On Sun, 2018-03-18 at 07:48 -0500, Rob Herring wrote: > On Mon, Mar 12, 2018 at 01:25:40PM +0800, Chunfeng Yun wrote: > > Add two properties of ref_clk and coefficient used by U2 slew rate > > calibrate which may vary on different SoCs > > > > Signed-off-by: Chunfeng Yun

Re: [PATCH v2 3/3] dt-bindings: phy-mtk-tphy: add properties for U2 slew rate calibrate

On Sun, 2018-03-18 at 07:48 -0500, Rob Herring wrote: > On Mon, Mar 12, 2018 at 01:25:40PM +0800, Chunfeng Yun wrote: > > Add two properties of ref_clk and coefficient used by U2 slew rate > > calibrate which may vary on different SoCs > > > > Signed-off-by: Chunfeng Yun > > --- > >

[PATCH] irqchip: irq-gic-v4: return real error code

__irq_domain_alloc_irqs will return some different error code, so we should return real error code in its_alloc_vcpu_irqs. Signed-off-by: Peng Hao --- drivers/irqchip/irq-gic-v4.c | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git

[PATCH] irqchip: irq-gic-v4: return real error code

__irq_domain_alloc_irqs will return some different error code, so we should return real error code in its_alloc_vcpu_irqs. Signed-off-by: Peng Hao --- drivers/irqchip/irq-gic-v4.c | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/drivers/irqchip/irq-gic-v4.c

[PATCH] ARM: dts: imx7d-pinfunc: update sai select input value

Update SAI select input daisy chain value according to Reference Manual. Signed-off-by: Anson Huang Signed-off-by: Shengjiu Wang --- arch/arm/boot/dts/imx7d-pinfunc.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

[PATCH] ARM: dts: imx7d-pinfunc: update sai select input value

Update SAI select input daisy chain value according to Reference Manual. Signed-off-by: Anson Huang Signed-off-by: Shengjiu Wang --- arch/arm/boot/dts/imx7d-pinfunc.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/arch/arm/boot/dts/imx7d-pinfunc.h

Re: [PATCH] mm: add config for readahead window

On Sun, Mar 18, 2018 at 7:37 PM Huang, Ying wrote: > Wei Wang writes: > > Android devices boot time benefits by bigger readahead window setting from > > init. This patch will make readahead window a config so early boot can > > benefit by it as well. >

Re: [PATCH] mm: add config for readahead window

On Sun, Mar 18, 2018 at 7:37 PM Huang, Ying wrote: > Wei Wang writes: > > Android devices boot time benefits by bigger readahead window setting from > > init. This patch will make readahead window a config so early boot can > > benefit by it as well. > Can you change the source code of init

Re: [PATCH] f2fs: don't put dentry page in pagecache into highmem

Hi, Jaegeuk, I find this patch is removed from current branch of dev-test recently, why? Any bugs? On 2018/2/28 20:31, Yunlong Song wrote: Previous dentry page uses highmem, which will cause panic in platforms using highmem (such as arm), since the address space of dentry pages from highmem

Re: [PATCH] f2fs: don't put dentry page in pagecache into highmem

Hi, Jaegeuk, I find this patch is removed from current branch of dev-test recently, why? Any bugs? On 2018/2/28 20:31, Yunlong Song wrote: Previous dentry page uses highmem, which will cause panic in platforms using highmem (such as arm), since the address space of dentry pages from highmem

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

Hi all, Today's linux-next merge of the tip tree got a conflict in: drivers/bus/arm-cci.c between commit: 3de6be7a3dd8 ("drivers/bus: Split Arm CCI driver") from the arm-soc tree and commit: edb39592a587 ("perf: Fix sibling iteration") from the tip tree. I fixed it up (I added the

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

Hi all, Today's linux-next merge of the tip tree got a conflict in: drivers/bus/arm-cci.c between commit: 3de6be7a3dd8 ("drivers/bus: Split Arm CCI driver") from the arm-soc tree and commit: edb39592a587 ("perf: Fix sibling iteration") from the tip tree. I fixed it up (I added the

Re: [PATCH 4.14 064/109] dmaengine: bcm2835-dma: Use vchan_terminate_vdesc() instead of desc_free

On Sun, Mar 18, 2018 at 11:44:51AM +0100, Greg Kroah-Hartman wrote: > On Sun, Mar 18, 2018 at 11:24:17AM +0100, Greg Kroah-Hartman wrote: > > > > This patch is causing a build error on arm and arm64 per i.e. > > > > https://kernelci.org/build/id/5aac017e59b5141cb1b3a4d5/ > > > > > > > > Builds

Re: [PATCH 4.14 064/109] dmaengine: bcm2835-dma: Use vchan_terminate_vdesc() instead of desc_free

On Sun, Mar 18, 2018 at 11:44:51AM +0100, Greg Kroah-Hartman wrote: > On Sun, Mar 18, 2018 at 11:24:17AM +0100, Greg Kroah-Hartman wrote: > > > > This patch is causing a build error on arm and arm64 per i.e. > > > > https://kernelci.org/build/id/5aac017e59b5141cb1b3a4d5/ > > > > > > > > Builds

RE: [PATCH] vmbus: use put_device() if device_register fail

> -Original Message- > From: devel On Behalf > Of Arvind Yadav > Sent: Saturday, March 17, 2018 11:48 PM > To: Stephen Hemminger ; Haiyang Zhang > > Cc: de...@linuxdriverproject.org;

RE: [PATCH] vmbus: use put_device() if device_register fail

> -Original Message- > From: devel On Behalf > Of Arvind Yadav > Sent: Saturday, March 17, 2018 11:48 PM > To: Stephen Hemminger ; Haiyang Zhang > > Cc: de...@linuxdriverproject.org; linux-kernel@vger.kernel.org > Subject: [PATCH] vmbus: use put_device() if device_register fail > > if

[PATCH] init: no need to wait device probe

From: Zhang Ning there are 2 reasons for no need to wait device probe reason 1: mount root device is very late in kernel initial stage. all initcalls are finished. that means most of probe functions are returned. and deferred probe are also finished by late_initcall.

[PATCH] init: no need to wait device probe

From: Zhang Ning there are 2 reasons for no need to wait device probe reason 1: mount root device is very late in kernel initial stage. all initcalls are finished. that means most of probe functions are returned. and deferred probe are also finished by late_initcall. only async probe driver

RE: [PATCH 1/2] pci: host: pci-hyperv: Replace GFP_ATOMIC with GFP_KERNEL in hv_pci_onchannelcallback

> -Original Message- > From: Jia-Ju Bai > Sent: Sunday, March 18, 2018 7:53 AM > To: KY Srinivasan ; Haiyang Zhang > ; Stephen Hemminger > ; bhelg...@google.com > Cc:

RE: [PATCH 1/2] pci: host: pci-hyperv: Replace GFP_ATOMIC with GFP_KERNEL in hv_pci_onchannelcallback

> -Original Message- > From: Jia-Ju Bai > Sent: Sunday, March 18, 2018 7:53 AM > To: KY Srinivasan ; Haiyang Zhang > ; Stephen Hemminger > ; bhelg...@google.com > Cc: de...@linuxdriverproject.org; linux-...@vger.kernel.org; linux- > ker...@vger.kernel.org; Jia-Ju Bai > Subject: [PATCH

Re: [PATCH v1 02/19] dt-bindings: cpufreq: mediatek: use - instead of _ in examples

Hi, Matthias I'm worried you missed the patch which already got both tags Reviewed-by from Rob and Acked-by: Viresh and thus I thought it should be ready for your tree. For the other patches in the same series, I will have v2 to refine them according to these suggestions and comments in v1 and

Re: [PATCH v1 02/19] dt-bindings: cpufreq: mediatek: use - instead of _ in examples

Hi, Matthias I'm worried you missed the patch which already got both tags Reviewed-by from Rob and Acked-by: Viresh and thus I thought it should be ready for your tree. For the other patches in the same series, I will have v2 to refine them according to these suggestions and comments in v1 and

Re: kbuild: move cc-option and cc-disable-warning after incl. arch Makefile

2018-03-19 9:41 GMT+09:00 Stefan Agner : > Hi Masahiro, > > On 27.11.2017 13:15, Masahiro Yamada wrote: >> Geert reported commit ae6b289a3789 ("kbuild: Set KBUILD_CFLAGS before >> incl. arch Makefile") broke cross-compilation using a cross-compiler >> that supports less compiler

Re: kbuild: move cc-option and cc-disable-warning after incl. arch Makefile

2018-03-19 9:41 GMT+09:00 Stefan Agner : > Hi Masahiro, > > On 27.11.2017 13:15, Masahiro Yamada wrote: >> Geert reported commit ae6b289a3789 ("kbuild: Set KBUILD_CFLAGS before >> incl. arch Makefile") broke cross-compilation using a cross-compiler >> that supports less compiler options than the

Re: [PATCH] f2fs: Set GF_NOFS in read_cache_page_gfp while doing f2fs_quota_read

On 2018/3/16 21:23, Ritesh Harjani wrote: > Quota code itself is serializing the operations by taking mutex_lock. > It seems a below deadlock can happen if GF_NOFS is not used in > f2fs_quota_read > > __switch_to+0x88 > __schedule+0x5b0 > schedule+0x78 > schedule_preempt_disabled+0x20 >

Re: [PATCH] f2fs: Set GF_NOFS in read_cache_page_gfp while doing f2fs_quota_read

On 2018/3/16 21:23, Ritesh Harjani wrote: > Quota code itself is serializing the operations by taking mutex_lock. > It seems a below deadlock can happen if GF_NOFS is not used in > f2fs_quota_read > > __switch_to+0x88 > __schedule+0x5b0 > schedule+0x78 > schedule_preempt_disabled+0x20 >

Re: [PATCH] mm: add config for readahead window

Wei Wang writes: > Android devices boot time benefits by bigger readahead window setting from > init. This patch will make readahead window a config so early boot can > benefit by it as well. Can you change the source code of init to call ioctl(BLKRASET) early? Best Regards,

Re: [PATCH] mm: add config for readahead window

Wei Wang writes: > Android devices boot time benefits by bigger readahead window setting from > init. This patch will make readahead window a config so early boot can > benefit by it as well. Can you change the source code of init to call ioctl(BLKRASET) early? Best Regards, Huang, Ying

[PATCH V2 1/2] clk: imx6sx: add missing lvds2 clock to the clock tree

i.MX6SX has lvds2 (analog clock2), an I/O clock like lvds1. And this lvds2, along with lvds1, can be used to provide external clock source to the internal pll, such as pll4_audio and pll5_video. This patch mainly adds the lvds2 to the clock tree and fix its relationship with pll accordingly.

[PATCH V2 1/2] clk: imx6sx: add missing lvds2 clock to the clock tree

i.MX6SX has lvds2 (analog clock2), an I/O clock like lvds1. And this lvds2, along with lvds1, can be used to provide external clock source to the internal pll, such as pll4_audio and pll5_video. This patch mainly adds the lvds2 to the clock tree and fix its relationship with pll accordingly.

[PATCH V2 2/2] ARM: dts: imx6sx-sabreauto: add external 24MHz clock source

On i.MX6SX SabreAuto board, there is external 24MHz clock source for analog clock2, add this clock source to clock tree. Signed-off-by: Anson Huang --- changes since V1: remove unnecessary clocks container. arch/arm/boot/dts/imx6sx-sabreauto.dts | 6 ++ 1 file

[PATCH V2 2/2] ARM: dts: imx6sx-sabreauto: add external 24MHz clock source

On i.MX6SX SabreAuto board, there is external 24MHz clock source for analog clock2, add this clock source to clock tree. Signed-off-by: Anson Huang --- changes since V1: remove unnecessary clocks container. arch/arm/boot/dts/imx6sx-sabreauto.dts | 6 ++ 1 file changed, 6

[PATCH] vfio iommu type1: improve memory pinning process for raw PFN mapping

When using vfio to pass through a PCIe device (e.g. a GPU card) that has a huge BAR (e.g. 16GB), a lot of cycles are wasted on memory pinning because PFNs of PCI BAR are not backed by struct page, and the corresponding VMA has flag VM_PFNMAP. With this change, when pinning a region which is a raw

[PATCH] vfio iommu type1: improve memory pinning process for raw PFN mapping

When using vfio to pass through a PCIe device (e.g. a GPU card) that has a huge BAR (e.g. 16GB), a lot of cycles are wasted on memory pinning because PFNs of PCI BAR are not backed by struct page, and the corresponding VMA has flag VM_PFNMAP. With this change, when pinning a region which is a raw

Re: [PATCH 0/2] drm/sun4i: Fix some error handling paths in 'sun4i_hdmi_bind()'

On Mon, Mar 19, 2018 at 6:48 AM, Christophe JAILLET wrote: > I've splitted these fixes into 2 patches becasue they do not fixe the same > commit. > > Christophe JAILLET (2): > drm/sun4i: hdmi: Fix an error handling path in 'sun4i_hdmi_bind()' > drm/sun4i: hdmi:

Re: [PATCH 0/2] drm/sun4i: Fix some error handling paths in 'sun4i_hdmi_bind()'

On Mon, Mar 19, 2018 at 6:48 AM, Christophe JAILLET wrote: > I've splitted these fixes into 2 patches becasue they do not fixe the same > commit. > > Christophe JAILLET (2): > drm/sun4i: hdmi: Fix an error handling path in 'sun4i_hdmi_bind()' > drm/sun4i: hdmi: Fix another error handling path

  1   2   3   4   5   6   7   8   9   >