Re: [PATCH v2] ARM: dts: add reset property for rk3066a-rayeager emac phy

Hi Heiko Thanks :) On 2017??12??17?? 04:11, Heiko Stuebner wrote: Hi Chris, Am Mittwoch, 8. November 2017, 17:50:41 CET schrieb Chris Zhong: The ethernet phy of rk3066a-rayeager has a reset pin, it controlled by GPIO1_D6, this pin should be pull down then pull up to reset the phy. Add a

Re: [PATCH v2] ARM: dts: add reset property for rk3066a-rayeager emac phy

Hi Heiko Thanks :) On 2017??12??17?? 04:11, Heiko Stuebner wrote: Hi Chris, Am Mittwoch, 8. November 2017, 17:50:41 CET schrieb Chris Zhong: The ethernet phy of rk3066a-rayeager has a reset pin, it controlled by GPIO1_D6, this pin should be pull down then pull up to reset the phy. Add a

[PATCH v4 2/2] drm: rcar-du: calculate DPLLCR to be more small jitter

From: Kuninori Morimoto In general, PLL has VCO (= Voltage controlled oscillator), one of the very important electronic feature called as "jitter" is related to this VCO. In academic generalism, VCO should be maximum to be more small jitter. In high frequency

[PATCH v4 2/2] drm: rcar-du: calculate DPLLCR to be more small jitter

From: Kuninori Morimoto In general, PLL has VCO (= Voltage controlled oscillator), one of the very important electronic feature called as "jitter" is related to this VCO. In academic generalism, VCO should be maximum to be more small jitter. In high frequency clock, jitter will be large impact.

[PATCH v4 1/2] drm: rcar-du: use 1000 to avoid misunderstanding in rcar_du_dpll_divider()

From: Kuninori Morimoto It is difficult to understand its scale if number has many 0s. This patch uses "* 1000" to avoid it in rcar_du_dpll_divider(). Signed-off-by: Kuninori Morimoto --- v3 -> v4 - no change

[PATCH v4 1/2] drm: rcar-du: use 1000 to avoid misunderstanding in rcar_du_dpll_divider()

From: Kuninori Morimoto It is difficult to understand its scale if number has many 0s. This patch uses "* 1000" to avoid it in rcar_du_dpll_divider(). Signed-off-by: Kuninori Morimoto --- v3 -> v4 - no change drivers/gpu/drm/rcar-du/rcar_du_crtc.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH v4 0/2] drm: rcar-du: calculate DPLLCR to be more small jitter

Hi Laurent, David These are v4 of DPLLCR patch for rcar-du. Mainly fixuped 2000 -> 2kHz to unambiguous Kuninori Morimoto (2): drm: rcar-du: use 1000 to avoid misunderstanding in rcar_du_dpll_divider() drm: rcar-du: calculate DPLLCR to be more small jitter

[PATCH v4 0/2] drm: rcar-du: calculate DPLLCR to be more small jitter

Hi Laurent, David These are v4 of DPLLCR patch for rcar-du. Mainly fixuped 2000 -> 2kHz to unambiguous Kuninori Morimoto (2): drm: rcar-du: use 1000 to avoid misunderstanding in rcar_du_dpll_divider() drm: rcar-du: calculate DPLLCR to be more small jitter

[trivial PATCH] treewide: Align function definition open/close braces

Some functions definitions have either the initial open brace and/or the closing brace outside of column 1. Move those braces to column 1. This allows various function analyzers like gnu complexity to work properly for these modified functions. Miscellanea: o Remove extra trailing ; and blank

[trivial PATCH] treewide: Align function definition open/close braces

Some functions definitions have either the initial open brace and/or the closing brace outside of column 1. Move those braces to column 1. This allows various function analyzers like gnu complexity to work properly for these modified functions. Miscellanea: o Remove extra trailing ; and blank

Re: [PATCH 2/3] vsprintf: print if symbol not found

On Mon, 2017-12-18 at 10:53 +1100, Tobin C. Harding wrote: > Depends on: commit bd6b239cdbb2 ("kallsyms: don't leak address when > symbol not found") > > Currently vsprintf for specifiers %p[SsB] relies on the behaviour of > kallsyms (sprint_symbol()) and prints the actual address if a symbol is

Re: [PATCH 2/3] vsprintf: print if symbol not found

On Mon, 2017-12-18 at 10:53 +1100, Tobin C. Harding wrote: > Depends on: commit bd6b239cdbb2 ("kallsyms: don't leak address when > symbol not found") > > Currently vsprintf for specifiers %p[SsB] relies on the behaviour of > kallsyms (sprint_symbol()) and prints the actual address if a symbol is

Re: [PATCH v2 0/3] doc: update printk documentation

On Sun, Dec 17, 2017 at 02:34:25PM -0800, Joe Perches wrote: > On Mon, 2017-12-18 at 09:30 +1100, Tobin C. Harding wrote: > > This set converts printk-formats.txt -> core-api/printk-formats.rst > > > > We also update the documentation around printing kernel addresses. > > Please also update the

Re: [PATCH v2 0/3] doc: update printk documentation

On Sun, Dec 17, 2017 at 02:34:25PM -0800, Joe Perches wrote: > On Mon, 2017-12-18 at 09:30 +1100, Tobin C. Harding wrote: > > This set converts printk-formats.txt -> core-api/printk-formats.rst > > > > We also update the documentation around printing kernel addresses. > > Please also update the

[PATCH 2/3] vsprintf: print if symbol not found

Depends on: commit bd6b239cdbb2 ("kallsyms: don't leak address when symbol not found") Currently vsprintf for specifiers %p[SsB] relies on the behaviour of kallsyms (sprint_symbol()) and prints the actual address if a symbol is not found. Previous patch changes this behaviour so tha

[PATCH 2/3] vsprintf: print if symbol not found

Depends on: commit bd6b239cdbb2 ("kallsyms: don't leak address when symbol not found") Currently vsprintf for specifiers %p[SsB] relies on the behaviour of kallsyms (sprint_symbol()) and prints the actual address if a symbol is not found. Previous patch changes this behaviour so tha

[PATCH 3/3] trace: print address if symbol not found

Fixes behaviour modified by: commit bd6b239cdbb2 ("kallsyms: don't leak address when symbol not found") Previous patch changed behaviour of kallsyms function sprint_symbol() to return an error code instead of printing the address if a symbol was not found. Ftrace relies on the original behaviour.

[PATCH 1/3] kallsyms: don't leak address when symbol not found

Currently if kallsyms_lookup() fails to find the symbol then the address is printed. This potentially leaks sensitive information. Instead of printing the address we can return an error, giving the calling code the option to print the address or print some sanitized message. Return error instead

[PATCH 3/3] trace: print address if symbol not found

Fixes behaviour modified by: commit bd6b239cdbb2 ("kallsyms: don't leak address when symbol not found") Previous patch changed behaviour of kallsyms function sprint_symbol() to return an error code instead of printing the address if a symbol was not found. Ftrace relies on the original behaviour.

[PATCH 1/3] kallsyms: don't leak address when symbol not found

Currently if kallsyms_lookup() fails to find the symbol then the address is printed. This potentially leaks sensitive information. Instead of printing the address we can return an error, giving the calling code the option to print the address or print some sanitized message. Return error instead

[PATCH 0/3] kallsyms: don't leak address

This set plugs a kernel address leak that occurs if kallsyms symbol look up fails. This set was prompted by a leaking address found using scripts/leaking_addresses.pl on a PowerPC machine in the wild. Patch set does not change behaviour when KALLSYMS is not defined (suggested by Linus). RFC has

[PATCH 0/3] kallsyms: don't leak address

This set plugs a kernel address leak that occurs if kallsyms symbol look up fails. This set was prompted by a leaking address found using scripts/leaking_addresses.pl on a PowerPC machine in the wild. Patch set does not change behaviour when KALLSYMS is not defined (suggested by Linus). RFC has

Re: [Y2038] [PATCH v2 08/10] fix get_timespec64() for y2038 safe compat interfaces

On Fri, 2017-12-15 at 13:02 +0100, Arnd Bergmann wrote: [...] > - I had an idea to handle the copying of timespec/timeval with a > one-size-fits-all >   function and multiple wrappers around it, such as > > enum user_ts_type { >   USER_TS_TIMEVAL = 1, >   USER_TS_32 = 2, >   

Re: [Y2038] [PATCH v2 08/10] fix get_timespec64() for y2038 safe compat interfaces

On Fri, 2017-12-15 at 13:02 +0100, Arnd Bergmann wrote: [...] > - I had an idea to handle the copying of timespec/timeval with a > one-size-fits-all >   function and multiple wrappers around it, such as > > enum user_ts_type { >   USER_TS_TIMEVAL = 1, >   USER_TS_32 = 2, >   

Re: [PATCH v3 2/2] drm: rcar-du: calculate DPLLCR to be more small jitter

Hi Geert > >> > From: Kuninori Morimoto > >> > In general, PLL has VCO (= Voltage controlled oscillator), > >> > one of the very important electronic feature called as "jitter" > >> > is related to this VCO. > >> > In academic generalism, VCO should be maximum

Re: [PATCH v3 2/2] drm: rcar-du: calculate DPLLCR to be more small jitter

Hi Geert > >> > From: Kuninori Morimoto > >> > In general, PLL has VCO (= Voltage controlled oscillator), > >> > one of the very important electronic feature called as "jitter" > >> > is related to this VCO. > >> > In academic generalism, VCO should be maximum to be more small jitter. > >> > In

Re: PROBLEM: NULL pointer dereference in kernel 4.14.6

On Sun, Dec 17, 2017 at 05:49:44PM +, Bronek Kozicki wrote: > I just upgraded to 4.14.7 and tried to reproduce this error, this time under > strace. As you can see this happens when systemctl tries to read a specific > entry under /sys/fs . In case this matters, the entry is for a small

Re: PROBLEM: NULL pointer dereference in kernel 4.14.6

On Sun, Dec 17, 2017 at 05:49:44PM +, Bronek Kozicki wrote: > I just upgraded to 4.14.7 and tried to reproduce this error, this time under > strace. As you can see this happens when systemctl tries to read a specific > entry under /sys/fs . In case this matters, the entry is for a small

Re: [PATCH 1/5] media: rc: update sunxi-ir driver to get base clock frequency from devicetree

On Sun, Dec 17, 2017 at 11:45:43PM +0100, Philipp Rossak wrote: > This patch updates the sunxi-ir driver to set the base clock frequency from > devicetree. > > This is neccessary since there are different ir recievers on the > market, that operate with different frequencys. So this value could be

Re: [PATCH 1/5] media: rc: update sunxi-ir driver to get base clock frequency from devicetree

On Sun, Dec 17, 2017 at 11:45:43PM +0100, Philipp Rossak wrote: > This patch updates the sunxi-ir driver to set the base clock frequency from > devicetree. > > This is neccessary since there are different ir recievers on the > market, that operate with different frequencys. So this value could be

Re: [PATCH v2 9/9] ARM: dts: imx7: add Toradex Colibri iMX7D 1GB (eMMC) support

Fabio, On Sun, Dec 17, 2017 at 10:59 PM, Fabio Estevam wrote: > Hi Stefan, > > On Sun, Dec 17, 2017 at 6:37 PM, Stefan Agner wrote: > >> --- /dev/null >> +++ b/arch/arm/boot/dts/imx7d-colibri-emmc-eval-v3.dts >> @@ -0,0 +1,20 @@ >> +/* >> + * Copyright 2017

Re: [PATCH v2 9/9] ARM: dts: imx7: add Toradex Colibri iMX7D 1GB (eMMC) support

Fabio, On Sun, Dec 17, 2017 at 10:59 PM, Fabio Estevam wrote: > Hi Stefan, > > On Sun, Dec 17, 2017 at 6:37 PM, Stefan Agner wrote: > >> --- /dev/null >> +++ b/arch/arm/boot/dts/imx7d-colibri-emmc-eval-v3.dts >> @@ -0,0 +1,20 @@ >> +/* >> + * Copyright 2017 Toradex AG >> + * >> + *

[PATCH 3/5] arm: dts: sun8i: a83t: Add the ir pin for the A83T

The CIR Pin of the A83T is located at PL12. Signed-off-by: Philipp Rossak --- arch/arm/boot/dts/sun8i-a83t.dtsi | 5 + 1 file changed, 5 insertions(+) diff --git a/arch/arm/boot/dts/sun8i-a83t.dtsi b/arch/arm/boot/dts/sun8i-a83t.dtsi index a384b766f3dc..954c2393325f

[PATCH 3/5] arm: dts: sun8i: a83t: Add the ir pin for the A83T

The CIR Pin of the A83T is located at PL12. Signed-off-by: Philipp Rossak --- arch/arm/boot/dts/sun8i-a83t.dtsi | 5 + 1 file changed, 5 insertions(+) diff --git a/arch/arm/boot/dts/sun8i-a83t.dtsi b/arch/arm/boot/dts/sun8i-a83t.dtsi index a384b766f3dc..954c2393325f 100644 ---

[PATCH 1/5] media: rc: update sunxi-ir driver to get base clock frequency from devicetree

This patch updates the sunxi-ir driver to set the base clock frequency from devicetree. This is neccessary since there are different ir recievers on the market, that operate with different frequencys. So this value could be set if the attached ir receiver needs an other base clock frequency, than

[PATCH 1/5] media: rc: update sunxi-ir driver to get base clock frequency from devicetree

This patch updates the sunxi-ir driver to set the base clock frequency from devicetree. This is neccessary since there are different ir recievers on the market, that operate with different frequencys. So this value could be set if the attached ir receiver needs an other base clock frequency, than

[PATCH 4/5] arm: dts: sun8i: a83t: Add support for the ir interface

The ir interface is like on the H3 located at 0x01f02000 and is exactly the same. This patch adds support for the ir interface on the A83T. Signed-off-by: Philipp Rossak --- arch/arm/boot/dts/sun8i-a83t.dtsi | 10 ++ 1 file changed, 10 insertions(+) diff --git

[PATCH 4/5] arm: dts: sun8i: a83t: Add support for the ir interface

The ir interface is like on the H3 located at 0x01f02000 and is exactly the same. This patch adds support for the ir interface on the A83T. Signed-off-by: Philipp Rossak --- arch/arm/boot/dts/sun8i-a83t.dtsi | 10 ++ 1 file changed, 10 insertions(+) diff --git

[PATCH 5/5] arm: dts: sun8i: a83t: bananapi-m3: Enable IR controller

The Bananapi M3 has an onboard IR receiver. This enables the onboard IR receiver subnode. Other than the other IR receivers this one needs a base clock frequency of 300 Hz (3 MHz), to be able to work. Signed-off-by: Philipp Rossak ---

[PATCH 5/5] arm: dts: sun8i: a83t: bananapi-m3: Enable IR controller

The Bananapi M3 has an onboard IR receiver. This enables the onboard IR receiver subnode. Other than the other IR receivers this one needs a base clock frequency of 300 Hz (3 MHz), to be able to work. Signed-off-by: Philipp Rossak --- arch/arm/boot/dts/sun8i-a83t-bananapi-m3.dts | 7 +++

[PATCH 2/5] media: dt: bindings: Update binding documentation for sunxi IR controller

This patch updates documentation for Device-Tree bindings for sunxi IR controller and adds the new optional property for the base clock frequency. Signed-off-by: Philipp Rossak --- Documentation/devicetree/bindings/media/sunxi-ir.txt | 2 ++ 1 file changed, 2 insertions(+)

[PATCH 0/5] arm: sunxi: IR support for A83T

This patch series adds support for the sunxi A83T ir module and enhances the sunxi-ir driver. Right now the base clock frequency for the ir driver is a hard coded define and is set to 8 MHz. This works for the most common ir receivers. On the Sinovoip Bananapi M3 the ir receiver needs, a 3 MHz

[PATCH 2/5] media: dt: bindings: Update binding documentation for sunxi IR controller

This patch updates documentation for Device-Tree bindings for sunxi IR controller and adds the new optional property for the base clock frequency. Signed-off-by: Philipp Rossak --- Documentation/devicetree/bindings/media/sunxi-ir.txt | 2 ++ 1 file changed, 2 insertions(+) diff --git

[PATCH 0/5] arm: sunxi: IR support for A83T

This patch series adds support for the sunxi A83T ir module and enhances the sunxi-ir driver. Right now the base clock frequency for the ir driver is a hard coded define and is set to 8 MHz. This works for the most common ir receivers. On the Sinovoip Bananapi M3 the ir receiver needs, a 3 MHz

Re: [PATCH v2 0/3] doc: update printk documentation

On Mon, 2017-12-18 at 09:30 +1100, Tobin C. Harding wrote: > This set converts printk-formats.txt -> core-api/printk-formats.rst > > We also update the documentation around printing kernel addresses. Please also update the comment in lib/vsprintf.c * ** Please update also

Re: [PATCH v2 0/3] doc: update printk documentation

On Mon, 2017-12-18 at 09:30 +1100, Tobin C. Harding wrote: > This set converts printk-formats.txt -> core-api/printk-formats.rst > > We also update the documentation around printing kernel addresses. Please also update the comment in lib/vsprintf.c * ** Please update also

Re: [RFC patch] checkpatch: Add a test for long function definitions (>200 lines)

On Sun, Dec 17, 2017 at 01:46:45PM -0800, Linus Torvalds wrote: > On Sat, Dec 16, 2017 at 5:26 PM, Joe Perches wrote: > >> > >>I'm not expecting you to be able to write a perl script that checks > >>the first line, but we have way too many 200-plus line functions in > >>

Re: [RFC patch] checkpatch: Add a test for long function definitions (>200 lines)

On Sun, Dec 17, 2017 at 01:46:45PM -0800, Linus Torvalds wrote: > On Sat, Dec 16, 2017 at 5:26 PM, Joe Perches wrote: > >> > >>I'm not expecting you to be able to write a perl script that checks > >>the first line, but we have way too many 200-plus line functions in > >>the kernel.

Re: [PATCH v2 2/7] i3c: Add core I3C infrastructure

On 12/14/17 07:16, Boris Brezillon wrote: > Add core infrastructure to support I3C in Linux and document it. > > Signed-off-by: Boris Brezillon > --- > drivers/Kconfig |2 + > drivers/Makefile|2 +- >

Re: [PATCH v2 2/7] i3c: Add core I3C infrastructure

On 12/14/17 07:16, Boris Brezillon wrote: > Add core infrastructure to support I3C in Linux and document it. > > Signed-off-by: Boris Brezillon > --- > drivers/Kconfig |2 + > drivers/Makefile|2 +- > drivers/i3c/Kconfig | 24 + >

[PATCH v2 0/3] doc: update printk documentation

This set converts printk-formats.txt -> core-api/printk-formats.rst We also update the documentation around printing kernel addresses. For v2 I have attempted to toe the line more in regards to 'make as few changes as possible to complete the conversion'. This is my first documentation

[PATCH v2 0/3] doc: update printk documentation

This set converts printk-formats.txt -> core-api/printk-formats.rst We also update the documentation around printing kernel addresses. For v2 I have attempted to toe the line more in regards to 'make as few changes as possible to complete the conversion'. This is my first documentation

[PATCH v2 2/3] doc: update kpt_restrict documentation

Recently the behaviour of printk specifier %pK was changed. The documentation does not currently mirror this. Update documentation for sysctl kpt_restrict. Signed-off-by: Tobin C. Harding --- Documentation/sysctl/kernel.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)

[PATCH v2 2/3] doc: update kpt_restrict documentation

Recently the behaviour of printk specifier %pK was changed. The documentation does not currently mirror this. Update documentation for sysctl kpt_restrict. Signed-off-by: Tobin C. Harding --- Documentation/sysctl/kernel.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git

[PATCH v2 1/3] doc: convert printk-formats.txt to rst

Documentation/printk-formats.txt is a candidate for conversion to ReStructuredText format. Some effort has already been made to do this conversion even thought the suffix is currently .txt Changes required to complete conversion - Move printk-formats.txt to core-api/printk-formats.rst - Add

[PATCH v2 3/3] doc: add documentation on printing kernel addresses

Hashing addresses printed with printk specifier %p was implemented recently. During development a number of issues were raised regarding leaking kernel addresses to userspace. Other documentation was updated but security/self-protection missed out. Add self-protection documentation regarding

[PATCH v2 1/3] doc: convert printk-formats.txt to rst

Documentation/printk-formats.txt is a candidate for conversion to ReStructuredText format. Some effort has already been made to do this conversion even thought the suffix is currently .txt Changes required to complete conversion - Move printk-formats.txt to core-api/printk-formats.rst - Add

[PATCH v2 3/3] doc: add documentation on printing kernel addresses

Hashing addresses printed with printk specifier %p was implemented recently. During development a number of issues were raised regarding leaking kernel addresses to userspace. Other documentation was updated but security/self-protection missed out. Add self-protection documentation regarding

Re: [RFC patch] checkpatch: Add a test for long function definitions (>200 lines)

On Sun, 2017-12-17 at 13:46 -0800, Linus Torvalds wrote: > On Sat, Dec 16, 2017 at 5:26 PM, Joe Perches wrote: > > > > > >I'm not expecting you to be able to write a perl script that checks > > >the first line, but we have way too many 200-plus line functions in > > >

Re: [RFC patch] checkpatch: Add a test for long function definitions (>200 lines)

On Sun, 2017-12-17 at 13:46 -0800, Linus Torvalds wrote: > On Sat, Dec 16, 2017 at 5:26 PM, Joe Perches wrote: > > > > > >I'm not expecting you to be able to write a perl script that checks > > >the first line, but we have way too many 200-plus line functions in > > >the kernel. I'd

[PATCH] hid: i2c-hid: Unify invariant post-power-on delay

This is result of debugging WCOM5020 on "Thinkpad 10 2nd" (2 HID devices - finger & pen), have random failures on any delay. Quirk-style fixes still wrong. I found this delay was too invariant (different after regulator_enable() & i2c command) and not even called in many i2c power-on places

[PATCH] hid: i2c-hid: Unify invariant post-power-on delay

This is result of debugging WCOM5020 on "Thinkpad 10 2nd" (2 HID devices - finger & pen), have random failures on any delay. Quirk-style fixes still wrong. I found this delay was too invariant (different after regulator_enable() & i2c command) and not even called in many i2c power-on places

Re: [PATCH v19 3/7] xbitmap: add more operations

On Sun, Dec 17, 2017 at 01:47:21PM +, Wang, Wei W wrote: > On Saturday, December 16, 2017 3:22 AM, Matthew Wilcox wrote: > > On Fri, Dec 15, 2017 at 10:49:15AM -0800, Matthew Wilcox wrote: > > > Here's the API I'm looking at right now. The user need take no lock; > > > the locking (spinlock)

Re: [PATCH v19 3/7] xbitmap: add more operations

On Sun, Dec 17, 2017 at 01:47:21PM +, Wang, Wei W wrote: > On Saturday, December 16, 2017 3:22 AM, Matthew Wilcox wrote: > > On Fri, Dec 15, 2017 at 10:49:15AM -0800, Matthew Wilcox wrote: > > > Here's the API I'm looking at right now. The user need take no lock; > > > the locking (spinlock)

Re: linux-next: Signed-off-by missing for commit in the chrome-platform tree

Hi Stephen, On Mon, Dec 18, 2017 at 07:57:20AM +1100, Stephen Rothwell wrote: > Hi Benson, > > Commit > > b2104e654703 ("platform/chrome: cros_ec_lpc: remove redundant pointer > request") > > is missing a Signed-off-by from its committer. Thanks for the catch. Fixed. -- Benson Leung

Re: linux-next: Signed-off-by missing for commit in the chrome-platform tree

Hi Stephen, On Mon, Dec 18, 2017 at 07:57:20AM +1100, Stephen Rothwell wrote: > Hi Benson, > > Commit > > b2104e654703 ("platform/chrome: cros_ec_lpc: remove redundant pointer > request") > > is missing a Signed-off-by from its committer. Thanks for the catch. Fixed. -- Benson Leung

Re: [GIT PULL] Page Table Isolation (PTI) v4.14 backporting base tree

Ok, so I've pulled the two prep trees, since they are obviously safe and don't change any code. I'm going to read through the actual real changes again one more time today, but as mentioned, I almost certainly won't actually pull them until after rc4. I'd like to have at least one calm rc here.

Re: [GIT PULL] Page Table Isolation (PTI) v4.14 backporting base tree

Ok, so I've pulled the two prep trees, since they are obviously safe and don't change any code. I'm going to read through the actual real changes again one more time today, but as mentioned, I almost certainly won't actually pull them until after rc4. I'd like to have at least one calm rc here.

Re: [PATCH v2 9/9] ARM: dts: imx7: add Toradex Colibri iMX7D 1GB (eMMC) support

Hi Stefan, On Sun, Dec 17, 2017 at 6:37 PM, Stefan Agner wrote: > --- /dev/null > +++ b/arch/arm/boot/dts/imx7d-colibri-emmc-eval-v3.dts > @@ -0,0 +1,20 @@ > +/* > + * Copyright 2017 Toradex AG > + * > + * SPDX-License-Identifier: (GPL-2.0+ OR MIT) > + */ In the previous patch

Re: [PATCH v2 9/9] ARM: dts: imx7: add Toradex Colibri iMX7D 1GB (eMMC) support

Hi Stefan, On Sun, Dec 17, 2017 at 6:37 PM, Stefan Agner wrote: > --- /dev/null > +++ b/arch/arm/boot/dts/imx7d-colibri-emmc-eval-v3.dts > @@ -0,0 +1,20 @@ > +/* > + * Copyright 2017 Toradex AG > + * > + * SPDX-License-Identifier: (GPL-2.0+ OR MIT) > + */ In the previous patch you used GPL-2.0

Re: [PATCH v2 8/9] ARM: dts: imx7-colibri: add MCP2515 CAN controller

On Sun, Dec 17, 2017 at 6:37 PM, Stefan Agner wrote: > The Colibri Evaluation Carrier Board provides a MCP2515 CAN > controller connected via SPI. Note that the i.MX 7 provides > an internal CAN controller which is much better suited for CAN > operations. Using the MCP2515 with a

Re: [PATCH v2 8/9] ARM: dts: imx7-colibri: add MCP2515 CAN controller

On Sun, Dec 17, 2017 at 6:37 PM, Stefan Agner wrote: > The Colibri Evaluation Carrier Board provides a MCP2515 CAN > controller connected via SPI. Note that the i.MX 7 provides > an internal CAN controller which is much better suited for CAN > operations. Using the MCP2515 with a Colibri iMX7

Re: [PATCH v2] x86/kexec: Exclude GART aperture from vmcore

On Sat, Dec 16, 2017 at 09:01:42AM +0800, Baoquan He wrote: > 2) If firmware is broken, you can't enable gart in firmware, will > firmware engineer fix this since it's a firmware bug? Slow down and get a reality check first please! A firmware engineer will fix a 10yr old BIOS?!? Yeah right. And

Re: [PATCH v2] x86/kexec: Exclude GART aperture from vmcore

On Sat, Dec 16, 2017 at 09:01:42AM +0800, Baoquan He wrote: > 2) If firmware is broken, you can't enable gart in firmware, will > firmware engineer fix this since it's a firmware bug? Slow down and get a reality check first please! A firmware engineer will fix a 10yr old BIOS?!? Yeah right. And

Re: [RFC patch] checkpatch: Add a test for long function definitions (>200 lines)

On Sat, Dec 16, 2017 at 5:26 PM, Joe Perches wrote: >> >>I'm not expecting you to be able to write a perl script that checks >>the first line, but we have way too many 200-plus line functions in >>the kernel. I'd like a warning on anything over 200 lines (a factor

Re: pxa3xx_nand times out in 4.14 with JFFS2

Hello Willy, On Sun, 17 Dec 2017 22:26:11 +0100 Boris Brezillon wrote: > +Miquel > > On Sun, 17 Dec 2017 22:16:50 +0100 > Willy Tarreau wrote: > > > On Sun, Dec 17, 2017 at 06:01:29PM -0300, Ezequiel Garcia wrote: > > > On 17 December 2017

Re: [RFC patch] checkpatch: Add a test for long function definitions (>200 lines)

On Sat, Dec 16, 2017 at 5:26 PM, Joe Perches wrote: >> >>I'm not expecting you to be able to write a perl script that checks >>the first line, but we have way too many 200-plus line functions in >>the kernel. I'd like a warning on anything over 200 lines (a factor >>of 4 over

Re: pxa3xx_nand times out in 4.14 with JFFS2

Hello Willy, On Sun, 17 Dec 2017 22:26:11 +0100 Boris Brezillon wrote: > +Miquel > > On Sun, 17 Dec 2017 22:16:50 +0100 > Willy Tarreau wrote: > > > On Sun, Dec 17, 2017 at 06:01:29PM -0300, Ezequiel Garcia wrote: > > > On 17 December 2017 at 16:00, Willy Tarreau wrote: > > > > On

Re: [PATCH v5 0/4] ARM: ep93xx: ts72xx: Add support for BK3 board

Hi Arnd, > On Sun, Dec 17, 2017 at 8:41 PM, Lukasz Majewski > wrote: > >> >> We also need to think about upholding support in GCC for > >> >> ARMv4(t) for the foreseeable future if there is a big web of > >> >> random deeply embedded systems out there that will need > >> >>

Re: [PATCH v5 0/4] ARM: ep93xx: ts72xx: Add support for BK3 board

Hi Arnd, > On Sun, Dec 17, 2017 at 8:41 PM, Lukasz Majewski > wrote: > >> >> We also need to think about upholding support in GCC for > >> >> ARMv4(t) for the foreseeable future if there is a big web of > >> >> random deeply embedded systems out there that will need > >> >> updates. > >> > >

Re: pxa3xx_nand times out in 4.14 with JFFS2

+Miquel On Sun, 17 Dec 2017 22:16:50 +0100 Willy Tarreau wrote: > On Sun, Dec 17, 2017 at 06:01:29PM -0300, Ezequiel Garcia wrote: > > On 17 December 2017 at 16:00, Willy Tarreau wrote: > > > On Sun, Dec 17, 2017 at 07:07:46PM +0100, Boris Brezillon wrote: > > >>

Re: pxa3xx_nand times out in 4.14 with JFFS2

+Miquel On Sun, 17 Dec 2017 22:16:50 +0100 Willy Tarreau wrote: > On Sun, Dec 17, 2017 at 06:01:29PM -0300, Ezequiel Garcia wrote: > > On 17 December 2017 at 16:00, Willy Tarreau wrote: > > > On Sun, Dec 17, 2017 at 07:07:46PM +0100, Boris Brezillon wrote: > > >> > > This would guarantee

Re: [GIT PULL REQUEST] watchdog - v4.15 Fixes

On Sun, Dec 17, 2017 at 12:12 PM, Linus Torvalds wrote: > > Also, all of these commits were committed less than an hour before > sending me the pull request, so I question the kind of testing they > got.. Oh, and equally importantly, it's an unsigned pull request

Re: [GIT PULL REQUEST] watchdog - v4.15 Fixes

On Sun, Dec 17, 2017 at 12:12 PM, Linus Torvalds wrote: > > Also, all of these commits were committed less than an hour before > sending me the pull request, so I question the kind of testing they > got.. Oh, and equally importantly, it's an unsigned pull request from a non-secured site, so I

Re: pxa3xx_nand times out in 4.14 with JFFS2

On Sun, Dec 17, 2017 at 06:01:29PM -0300, Ezequiel Garcia wrote: > On 17 December 2017 at 16:00, Willy Tarreau wrote: > > On Sun, Dec 17, 2017 at 07:07:46PM +0100, Boris Brezillon wrote: > >> > > This would guarantee that devices with factory bad blocks, > >> > > (and no BBT), would

Re: pxa3xx_nand times out in 4.14 with JFFS2

On Sun, Dec 17, 2017 at 06:01:29PM -0300, Ezequiel Garcia wrote: > On 17 December 2017 at 16:00, Willy Tarreau wrote: > > On Sun, Dec 17, 2017 at 07:07:46PM +0100, Boris Brezillon wrote: > >> > > This would guarantee that devices with factory bad blocks, > >> > > (and no BBT), would be OK with

Re: [PATCH 0/3] Use mm_struct and switch_mm() instead of manually

Hi Sai, On Sun, Dec 17, 2017 at 5:35 AM, Sai Praneeth Prakhya wrote: > From: Sai Praneeth > > Presently, in x86, to invoke any efi function like > efi_set_virtual_address_map() or any efi_runtime_service() the code path > typically

Re: [PATCH 0/3] Use mm_struct and switch_mm() instead of manually

Hi Sai, On Sun, Dec 17, 2017 at 5:35 AM, Sai Praneeth Prakhya wrote: > From: Sai Praneeth > > Presently, in x86, to invoke any efi function like > efi_set_virtual_address_map() or any efi_runtime_service() the code path > typically involves read_cr3() (save previous pgd), write_cr3() > (write

[PATCH] abx500_chargalg: Delete an error message for a failed memory allocation in abx500_chargalg_probe()

From: Markus Elfring Date: Sun, 17 Dec 2017 22:02:11 +0100 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH] abx500_chargalg: Delete an error message for a failed memory allocation in abx500_chargalg_probe()

From: Markus Elfring Date: Sun, 17 Dec 2017 22:02:11 +0100 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- drivers/power/supply/abx500_chargalg.c | 4 +--- 1 file changed, 1

Re: pxa3xx_nand times out in 4.14 with JFFS2

On 17 December 2017 at 16:00, Willy Tarreau wrote: > On Sun, Dec 17, 2017 at 07:07:46PM +0100, Boris Brezillon wrote: >> > > This would guarantee that devices with factory bad blocks, >> > > (and no BBT), would be OK with this patch. >> > >> > I see. I'm fine with trying provided I

Re: pxa3xx_nand times out in 4.14 with JFFS2

On 17 December 2017 at 16:00, Willy Tarreau wrote: > On Sun, Dec 17, 2017 at 07:07:46PM +0100, Boris Brezillon wrote: >> > > This would guarantee that devices with factory bad blocks, >> > > (and no BBT), would be OK with this patch. >> > >> > I see. I'm fine with trying provided I have

linux-next: Signed-off-by missing for commit in the scsi tree

Hi James, Commit 9188808c7760 ("scsi: hisi_sas: fix SAS_QUEUE_FULL problem while running IO") is missing a Signed-off-by from its author. -- Cheers, Stephen Rothwell

linux-next: Signed-off-by missing for commit in the scsi tree

Hi James, Commit 9188808c7760 ("scsi: hisi_sas: fix SAS_QUEUE_FULL problem while running IO") is missing a Signed-off-by from its author. -- Cheers, Stephen Rothwell

linux-next: Signed-off-by missing for commit in the chrome-platform tree

Hi Benson, Commit b2104e654703 ("platform/chrome: cros_ec_lpc: remove redundant pointer request") is missing a Signed-off-by from its committer. -- Cheers, Stephen Rothwell

linux-next: Signed-off-by missing for commit in the chrome-platform tree

Hi Benson, Commit b2104e654703 ("platform/chrome: cros_ec_lpc: remove redundant pointer request") is missing a Signed-off-by from its committer. -- Cheers, Stephen Rothwell

Re: [PATCH v2 2/3] backlight: tdo24m: add the reset line gpio

On Sat, Dec 16, 2017 at 12:39:50PM +0100, Robert Jarzmik wrote: > Daniel Thompson writes: > > On Fri, Oct 13, 2017 at 09:42:48PM +0200, Robert Jarzmik wrote: > >> The Toppoly panels have a global reset line. Add an optional gpio > >> control for this line, for

Re: [PATCH v2 2/3] backlight: tdo24m: add the reset line gpio

On Sat, Dec 16, 2017 at 12:39:50PM +0100, Robert Jarzmik wrote: > Daniel Thompson writes: > > On Fri, Oct 13, 2017 at 09:42:48PM +0200, Robert Jarzmik wrote: > >> The Toppoly panels have a global reset line. Add an optional gpio > >> control for this line, for platforms which have the ability to

Re: AMD erratum 665 on f15h processor?

On Sun, Dec 17, 2017 at 12:04:28PM +0300, Andrew Randrianasulu wrote: > Hello! > > I was trying to investigate why all my old kernels can't be booted on my > relatively new machine. Kernels 4.10+ naturally boot - I use 4.14.3 right now > - > but old kernels die early ... > > After some

Re: AMD erratum 665 on f15h processor?

On Sun, Dec 17, 2017 at 12:04:28PM +0300, Andrew Randrianasulu wrote: > Hello! > > I was trying to investigate why all my old kernels can't be booted on my > relatively new machine. Kernels 4.10+ naturally boot - I use 4.14.3 right now > - > but old kernels die early ... > > After some

<    1   2   3   4   5   6   7   8   9   >