Re: [PATCH] ARM: dts: imx6qdl-udoo: disable AC'97 input pins pad drivers

On Mon, Nov 20, 2017 at 08:08:30PM +0100, Maciej S. Szmigiero wrote: > AC'97 interface RXD and TXC pins are only used as SoC inputs, let's disable > pad drivers for them so we will be protected if, for example, TCLKDIR is > set by mistake in AUDMUX and causes TXC pin to be configured as an output.

linux-next: Tree for Nov 29

Hi all, Changes since 20171128: New trees: bpf, bpf-next Renamed tree: kvm-master to kvm-fixes Dropped tree: vfs (badly conflicting commit) The vfs tree gained conflicts against Linus' tree so I dropped it for today. The i2c tree lost its build failure. The etnaviv tree still had its

Re: drm/amd/display: Restructuring and cleaning up DML

On Sat, Nov 18, 2017 at 12:02:01AM +, Linux Kernel wrote: > Web: > https://git.kernel.org/torvalds/c/6d04ee9dc10149db842d41de66eca201c9d91b60 > Commit: 6d04ee9dc10149db842d41de66eca201c9d91b60 > Parent: 19b7fe4a48efbe0f7e8c496b040c4eb16ff02313 > Refname:

Re: drm/amd/display: Restructuring and cleaning up DML

On Sat, Nov 18, 2017 at 12:02:01AM +, Linux Kernel wrote: > Web: > https://git.kernel.org/torvalds/c/6d04ee9dc10149db842d41de66eca201c9d91b60 > Commit: 6d04ee9dc10149db842d41de66eca201c9d91b60 > Parent: 19b7fe4a48efbe0f7e8c496b040c4eb16ff02313 > Refname:

Re: [PATCH v2] arm64: dts: ls1088a: add fsl-mc hardware resource manager node

On Fri, Nov 17, 2017 at 04:05:26PM +0200, Ioana Ciornei wrote: > Add the fsl-mc node in the LS1088A device tree. > > Signed-off-by: Ioana Ciornei Applied, thanks.

Re: [PATCH v2] arm64: dts: ls1088a: add fsl-mc hardware resource manager node

On Fri, Nov 17, 2017 at 04:05:26PM +0200, Ioana Ciornei wrote: > Add the fsl-mc node in the LS1088A device tree. > > Signed-off-by: Ioana Ciornei Applied, thanks.

[PATCH] 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] 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] pwm: meson: fix harware duty calculation

From: Jian Hu The actual HIGH/LOW signal output from the PWM is equal to the value programed to HW register plus one, this is designed by HW. This fix should apply to all Meson SoC(include GX/GXL/GXBB, Meson6,8) Fixes: 211ed630753d ("pwm: Add support for Meson PWM

[PATCH] pwm: meson: fix harware duty calculation

From: Jian Hu The actual HIGH/LOW signal output from the PWM is equal to the value programed to HW register plus one, this is designed by HW. This fix should apply to all Meson SoC(include GX/GXL/GXBB, Meson6,8) Fixes: 211ed630753d ("pwm: Add support for Meson PWM Controller") Signed-off-by:

[PATCH v1 0/2] DRM driver for Sitronix ST7735R display panels

This series adds a new DRM/TinyDRM driver for Sitronix ST7735R, specifically the Adafruit 1.8" TFT. Nothing fancy here. Just mostly TinyDRM boilerplate with the init sequence from the fbtft driver for the same panel. I'm assuming that since it says so here[1], that the "R" suffix is important,

[PATCH v1 0/2] DRM driver for Sitronix ST7735R display panels

This series adds a new DRM/TinyDRM driver for Sitronix ST7735R, specifically the Adafruit 1.8" TFT. Nothing fancy here. Just mostly TinyDRM boilerplate with the init sequence from the fbtft driver for the same panel. I'm assuming that since it says so here[1], that the "R" suffix is important,

Re: [PATCH 08/10] staging: lustre: lov: use list_for_each_entry in lov_obd.c

Subject: [PATCH] staging: lustre: lov: use list_for_each_entry in lov_obd.c Using the *_entry macro simplifies the code slightly. Signed-off-by: NeilBrown --- Resubmitted with non-empty changelog text. Thanks, NeilBrown drivers/staging/lustre/lustre/lov/lov_obd.c | 6 ++

Re: [PATCH 08/10] staging: lustre: lov: use list_for_each_entry in lov_obd.c

Subject: [PATCH] staging: lustre: lov: use list_for_each_entry in lov_obd.c Using the *_entry macro simplifies the code slightly. Signed-off-by: NeilBrown --- Resubmitted with non-empty changelog text. Thanks, NeilBrown drivers/staging/lustre/lustre/lov/lov_obd.c | 6 ++ 1 file changed,

[PATCH v1 1/2] dt-bindings: Add binding for Sitronix ST7735R display panels

This adds a new device tree binding for Sitronix ST7735R display panels, such as the Adafruit 1.8" TFT. Signed-off-by: David Lechner --- .../bindings/display/sitronix,st7735r.txt | 35 ++ 1 file changed, 35 insertions(+) create mode 100644

[PATCH v1 1/2] dt-bindings: Add binding for Sitronix ST7735R display panels

This adds a new device tree binding for Sitronix ST7735R display panels, such as the Adafruit 1.8" TFT. Signed-off-by: David Lechner --- .../bindings/display/sitronix,st7735r.txt | 35 ++ 1 file changed, 35 insertions(+) create mode 100644

[PATCH v1 2/2] drm/tinydrm: add driver for ST7735R panels

ct drm_driver st7735r_driver = { + .driver_features= DRIVER_GEM | DRIVER_MODESET | DRIVER_PRIME | + DRIVER_ATOMIC, + .fops = _fops, + TINYDRM_GEM_DRIVER_OPS, + .lastclose = tinydrm_lastclose, + .name =

[PATCH v1 2/2] drm/tinydrm: add driver for ST7735R panels

| + DRIVER_ATOMIC, + .fops = _fops, + TINYDRM_GEM_DRIVER_OPS, + .lastclose = tinydrm_lastclose, + .name = "st7735r", + .desc = "Sitronix S

Re: [PATCH] arm, ls1021a: add support for Moxa UC-8410A open platform

On Thu, Nov 16, 2017 at 10:58:57PM +0800, SZ Lin wrote: > Add support for Moxa UC-8410A open platform > > The UC-8410A computing platform is designed > for embedded communication-centric industrial applications > > The features of UC-8410A are: > * QSPI flash > * SD slot > * 3x LAN > * 8x

Re: [PATCH] arm, ls1021a: add support for Moxa UC-8410A open platform

On Thu, Nov 16, 2017 at 10:58:57PM +0800, SZ Lin wrote: > Add support for Moxa UC-8410A open platform > > The UC-8410A computing platform is designed > for embedded communication-centric industrial applications > > The features of UC-8410A are: > * QSPI flash > * SD slot > * 3x LAN > * 8x

Re: [PATCH 3/3] autofs - fix AT_NO_AUTOMOUNT not being honored

Adding Al Viro to the Cc list as I believe Stephen Whitehouse and Al have discussed something similar, please feel free to chime in with your thoughts Al. On 29/11/17 09:17, NeilBrown wrote: > On Tue, Nov 28 2017, Mike Marion wrote: > >> On Tue, Nov 28, 2017 at 07:43:05AM +0800, Ian Kent wrote:

Re: [PATCH 3/3] autofs - fix AT_NO_AUTOMOUNT not being honored

Adding Al Viro to the Cc list as I believe Stephen Whitehouse and Al have discussed something similar, please feel free to chime in with your thoughts Al. On 29/11/17 09:17, NeilBrown wrote: > On Tue, Nov 28 2017, Mike Marion wrote: > >> On Tue, Nov 28, 2017 at 07:43:05AM +0800, Ian Kent wrote:

Re: [PATCH v4 1/8] dt-bindings: Add Cavium Octeon Common Ethernet Interface.

On 11/28/2017 06:01 PM, Andrew Lunn wrote: On Tue, Nov 28, 2017 at 04:55:33PM -0800, David Daney wrote: From: Carlos Munoz Add bindings for Common Ethernet Interface (BGX) block. Acked-by: Rob Herring Signed-off-by: Carlos Munoz

Re: [PATCH v4 1/8] dt-bindings: Add Cavium Octeon Common Ethernet Interface.

On 11/28/2017 06:01 PM, Andrew Lunn wrote: On Tue, Nov 28, 2017 at 04:55:33PM -0800, David Daney wrote: From: Carlos Munoz Add bindings for Common Ethernet Interface (BGX) block. Acked-by: Rob Herring Signed-off-by: Carlos Munoz Signed-off-by: Steven J. Hill Signed-off-by: David Daney

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

Hi Paul, Signed-off-by: Lihao Liang Many thanks, Lihao. On 2017/11/29 9:14, Paul E. McKenney wrote: > On Wed, Nov 29, 2017 at 11:51:51AM +1100, Stephen Rothwell wrote: >> Hi Paul, >> >> Commit >> >> d7e182c9c324 ("rcu: Remove unnecessary spinlock in >>

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

Hi Paul, Signed-off-by: Lihao Liang Many thanks, Lihao. On 2017/11/29 9:14, Paul E. McKenney wrote: > On Wed, Nov 29, 2017 at 11:51:51AM +1100, Stephen Rothwell wrote: >> Hi Paul, >> >> Commit >> >> d7e182c9c324 ("rcu: Remove unnecessary spinlock in >> rcu_boot_init_percpu_data()") >> >> is

Re: [PATCH 3/3] autofs - fix AT_NO_AUTOMOUNT not being honored

On Wed, Nov 29 2017, Ian Kent wrote: > On 29/11/17 10:13, Mike Marion wrote: >> On Wed, Nov 29, 2017 at 12:17:27PM +1100, NeilBrown wrote: >> >>> How big do people see /proc/self/mount* getting? What size reads >>> does 'strace' show the various programs using to read it? >> >> We already have

Re: [PATCH 3/3] autofs - fix AT_NO_AUTOMOUNT not being honored

On Wed, Nov 29 2017, Ian Kent wrote: > On 29/11/17 10:13, Mike Marion wrote: >> On Wed, Nov 29, 2017 at 12:17:27PM +1100, NeilBrown wrote: >> >>> How big do people see /proc/self/mount* getting? What size reads >>> does 'strace' show the various programs using to read it? >> >> We already have

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

On 11/28/17 at 10:58pm, Jiri Bohac wrote: > Hi Baoquan, > > On Sun, Nov 12, 2017 at 04:04:26PM +0800, Baoquan He wrote: > > Solution: > > 1) Remove the code which support GART IOMMU when it's not enabled in > > BIOS. This has been done in the new generation of hardware IOMMU like > > intel vt-d

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

On 11/28/17 at 10:58pm, Jiri Bohac wrote: > Hi Baoquan, > > On Sun, Nov 12, 2017 at 04:04:26PM +0800, Baoquan He wrote: > > Solution: > > 1) Remove the code which support GART IOMMU when it's not enabled in > > BIOS. This has been done in the new generation of hardware IOMMU like > > intel vt-d

Re: [PATCH v3] kbuild: Set KBUILD_CFLAGS before incl. arch Makefile

Hi Nick, 2017-11-29 3:18 GMT+09:00 Nick Desaulniers : > Hi Masahiro, > > Thanks for merging Chris' patch, and sorry for taking so long to respond. > > On Wed, Nov 22, 2017 at 8:24 PM, Masahiro Yamada > wrote: >> Linus suggests to move

Re: [PATCH v3] kbuild: Set KBUILD_CFLAGS before incl. arch Makefile

Hi Nick, 2017-11-29 3:18 GMT+09:00 Nick Desaulniers : > Hi Masahiro, > > Thanks for merging Chris' patch, and sorry for taking so long to respond. > > On Wed, Nov 22, 2017 at 8:24 PM, Masahiro Yamada > wrote: >> Linus suggests to move compiler flag testing to Kconfig. > > Do you have an LKML

Re: [PATCH V11 2/5] vsprintf: refactor %pK code out of pointer()

On Wed, 29 Nov 2017 13:05:02 +1100 "Tobin C. Harding" wrote: > + /* > + * kptr_restrict==1 cannot be used in IRQ context > + * because its test for CAP_SYSLOG would be meaningless. > + */ > + if (in_irq() ||

Re: [PATCH V11 2/5] vsprintf: refactor %pK code out of pointer()

On Wed, 29 Nov 2017 13:05:02 +1100 "Tobin C. Harding" wrote: > + /* > + * kptr_restrict==1 cannot be used in IRQ context > + * because its test for CAP_SYSLOG would be meaningless. > + */ > + if (in_irq() || in_serving_softirq() ||

[PATCH] ASoC: soc-core: add missing EXPORT_SYMBOL_GPL() for snd_soc_disconnect_sync

From: Kuninori Morimoto Signed-off-by: Kuninori Morimoto --- Hi Stephen Thank you for reporting. I think your issue will be solved by this patch sound/soc/soc-core.c | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH] ASoC: soc-core: add missing EXPORT_SYMBOL_GPL() for snd_soc_disconnect_sync

From: Kuninori Morimoto Signed-off-by: Kuninori Morimoto --- Hi Stephen Thank you for reporting. I think your issue will be solved by this patch sound/soc/soc-core.c | 1 + 1 file changed, 1 insertion(+) diff --git a/sound/soc/soc-core.c b/sound/soc/soc-core.c index 9047046..345baa4 100644

Re: [PATCH] hugetlbfs: change put_page/unlock_page order in hugetlbfs_fallocate()

On Sat, Aug 26, 2017 at 12:11:24PM -0700, Nadav Amit wrote: > hugetlfs_fallocate() currently performs put_page() before unlock_page(). > This scenario opens a small time window, from the time the page is added > to the page cache, until it is unlocked, in which the page might be > removed from the

Re: [PATCH] hugetlbfs: change put_page/unlock_page order in hugetlbfs_fallocate()

On Sat, Aug 26, 2017 at 12:11:24PM -0700, Nadav Amit wrote: > hugetlfs_fallocate() currently performs put_page() before unlock_page(). > This scenario opens a small time window, from the time the page is added > to the page cache, until it is unlocked, in which the page might be > removed from the

Re: [PATCH 3/3] autofs - fix AT_NO_AUTOMOUNT not being honored

On 29/11/17 10:13, Mike Marion wrote: > On Wed, Nov 29, 2017 at 12:17:27PM +1100, NeilBrown wrote: > >> How big do people see /proc/self/mount* getting? What size reads >> does 'strace' show the various programs using to read it? > > We already have line counts into 5 figures. This wasn't an

Re: [PATCH 3/3] autofs - fix AT_NO_AUTOMOUNT not being honored

On 29/11/17 10:13, Mike Marion wrote: > On Wed, Nov 29, 2017 at 12:17:27PM +1100, NeilBrown wrote: > >> How big do people see /proc/self/mount* getting? What size reads >> does 'strace' show the various programs using to read it? > > We already have line counts into 5 figures. This wasn't an

Re: [PATCH V11 4/5] vsprintf: add printk specifier %px

On Tue, Nov 28, 2017 at 6:05 PM, Tobin C. Harding wrote: > >Let's add specifier %px as a > clear, opt-in, way to print a pointer and maintain some level of > isolation from all the other hex integer output within the Kernel. Yes, I like this model. It's easy and it's obvious

Re: [PATCH V11 4/5] vsprintf: add printk specifier %px

On Tue, Nov 28, 2017 at 6:05 PM, Tobin C. Harding wrote: > >Let's add specifier %px as a > clear, opt-in, way to print a pointer and maintain some level of > isolation from all the other hex integer output within the Kernel. Yes, I like this model. It's easy and it's obvious ("'x' for hex"),

Re: [PATCH] hwmon: (pmbus/lm25066) Default coefficients for low current limit

On 11/28/2017 10:39 AM, Rob Lippert wrote: On Mon, Nov 27, 2017 at 8:26 PM, Guenter Roeck wrote: On 11/27/2017 04:28 PM, Robert Lippert wrote: There seems to be no way to detect the value of the CL/GAIN pin from the device using PMBus. Low current mode seems to be

Re: [PATCH] hwmon: (pmbus/lm25066) Default coefficients for low current limit

On 11/28/2017 10:39 AM, Rob Lippert wrote: On Mon, Nov 27, 2017 at 8:26 PM, Guenter Roeck wrote: On 11/27/2017 04:28 PM, Robert Lippert wrote: There seems to be no way to detect the value of the CL/GAIN pin from the device using PMBus. Low current mode seems to be recommended (from LM5066

Re: [PATCH] certs: always use secondary keyring first if possible

On 11/18/17 at 12:47pm, Dave Young wrote: > Commit d3bfe84129f6 introduced secondary_trusted_keys keyring, current > users of verify_pkcs7_signature are below: > net/wireless/reg.c : uses its own trusted_keys > kernel/module_signing.c : pass NULL trusted_keys >

Re: [PATCH] certs: always use secondary keyring first if possible

On 11/18/17 at 12:47pm, Dave Young wrote: > Commit d3bfe84129f6 introduced secondary_trusted_keys keyring, current > users of verify_pkcs7_signature are below: > net/wireless/reg.c : uses its own trusted_keys > kernel/module_signing.c : pass NULL trusted_keys >

Re: [PATCH 3/3] autofs - fix AT_NO_AUTOMOUNT not being honored

On Wed, Nov 29, 2017 at 12:17:27PM +1100, NeilBrown wrote: > How big do people see /proc/self/mount* getting? What size reads > does 'strace' show the various programs using to read it? We already have line counts into 5 figures. This wasn't an issue until the change of /etc/mtab to a link.

Re: [PATCH 3/3] autofs - fix AT_NO_AUTOMOUNT not being honored

On Wed, Nov 29, 2017 at 12:17:27PM +1100, NeilBrown wrote: > How big do people see /proc/self/mount* getting? What size reads > does 'strace' show the various programs using to read it? We already have line counts into 5 figures. This wasn't an issue until the change of /etc/mtab to a link.

Re: [PATCH v3 2/5] drm/stm: dsi: Adjust dw_mipi_dsi_probe and remove

On Tue, Nov 28, 2017 at 10:41:29AM -0800, Brian Norris wrote: > Hi Nickey, > > On Tue, Nov 28, 2017 at 07:20:03PM +0800, Nickey Yang wrote: > > Bridge drivers/helpers shouldn't be clobbering the drvdata, since a > > parent driver might need to own this. Instead, let's return our > > Other

Re: [PATCH v3 2/5] drm/stm: dsi: Adjust dw_mipi_dsi_probe and remove

On Tue, Nov 28, 2017 at 10:41:29AM -0800, Brian Norris wrote: > Hi Nickey, > > On Tue, Nov 28, 2017 at 07:20:03PM +0800, Nickey Yang wrote: > > Bridge drivers/helpers shouldn't be clobbering the drvdata, since a > > parent driver might need to own this. Instead, let's return our > > Other

[PATCH V11 2/5] vsprintf: refactor %pK code out of pointer()

Currently code to handle %pK is all within the switch statement in pointer(). This is the wrong level of abstraction. Each of the other switch clauses call a helper function, pK should do the same. Refactor code out of pointer() to new function restricted_pointer(). Signed-off-by: Tobin C.

[PATCH V11 2/5] vsprintf: refactor %pK code out of pointer()

Currently code to handle %pK is all within the switch statement in pointer(). This is the wrong level of abstraction. Each of the other switch clauses call a helper function, pK should do the same. Refactor code out of pointer() to new function restricted_pointer(). Signed-off-by: Tobin C.

[PATCH V11 5/5] kasan: use %px to print addresses instead of %p

Pointers printed with %p are now hashed by default. Kasan needs the actual address. We can use the new printk specifier %px for this purpose. Use %px instead of %p to print addresses. Signed-off-by: Tobin C. Harding --- mm/kasan/report.c | 8 1 file changed, 4

[PATCH V11 5/5] kasan: use %px to print addresses instead of %p

Pointers printed with %p are now hashed by default. Kasan needs the actual address. We can use the new printk specifier %px for this purpose. Use %px instead of %p to print addresses. Signed-off-by: Tobin C. Harding --- mm/kasan/report.c | 8 1 file changed, 4 insertions(+), 4

[PATCH V11 4/5] vsprintf: add printk specifier %px

printk specifier %p now hashes all addresses before printing. Sometimes we need to see the actual unmodified address. This can be achieved using %lx but then we face the risk that if in future we want to change the way the Kernel handles printing of pointers we will have to grep through the

[PATCH V11 4/5] vsprintf: add printk specifier %px

printk specifier %p now hashes all addresses before printing. Sometimes we need to see the actual unmodified address. This can be achieved using %lx but then we face the risk that if in future we want to change the way the Kernel handles printing of pointers we will have to grep through the

[PATCH V11 1/5] docs: correct documentation for %pK

Current documentation indicates that %pK prints a leading '0x'. This is not the case. Correct documentation for printk specifier %pK. Signed-off-by: Tobin C. Harding --- Documentation/printk-formats.txt | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git

[PATCH V11 1/5] docs: correct documentation for %pK

Current documentation indicates that %pK prints a leading '0x'. This is not the case. Correct documentation for printk specifier %pK. Signed-off-by: Tobin C. Harding --- Documentation/printk-formats.txt | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git

[PATCH V11 3/5] printk: hash addresses printed with %p

Currently there exist approximately 14 000 places in the kernel where addresses are being printed using an unadorned %p. This potentially leaks sensitive information regarding the Kernel layout in memory. Many of these calls are stale, instead of fixing every call lets hash the address by default

[PATCH V11 3/5] printk: hash addresses printed with %p

Currently there exist approximately 14 000 places in the kernel where addresses are being printed using an unadorned %p. This potentially leaks sensitive information regarding the Kernel layout in memory. Many of these calls are stale, instead of fixing every call lets hash the address by default

[PATCH V11 0/5] hash addresses printed with %p

Currently there exist approximately 14 000 places in the Kernel where addresses are being printed using an unadorned %p. This potentially leaks sensitive information regarding the Kernel layout in memory. Many of these calls are stale, instead of fixing every call lets hash the address by default

[PATCH V11 0/5] hash addresses printed with %p

Currently there exist approximately 14 000 places in the Kernel where addresses are being printed using an unadorned %p. This potentially leaks sensitive information regarding the Kernel layout in memory. Many of these calls are stale, instead of fixing every call lets hash the address by default

[PATCH v2] crypto: hmac - require that the underlying hash algorithm is unkeyed

From: Eric Biggers Because the HMAC template didn't check that its underlying hash algorithm is unkeyed, trying to use "hmac(hmac(sha3-512-generic))" through AF_ALG or through KEYCTL_DH_COMPUTE resulted in the inner HMAC being used without having been keyed, resulting in

[PATCH v2] crypto: hmac - require that the underlying hash algorithm is unkeyed

From: Eric Biggers Because the HMAC template didn't check that its underlying hash algorithm is unkeyed, trying to use "hmac(hmac(sha3-512-generic))" through AF_ALG or through KEYCTL_DH_COMPUTE resulted in the inner HMAC being used without having been keyed, resulting in sha3_update() being

Re: [PATCH v4 1/8] dt-bindings: Add Cavium Octeon Common Ethernet Interface.

On Tue, Nov 28, 2017 at 04:55:33PM -0800, David Daney wrote: > From: Carlos Munoz > > Add bindings for Common Ethernet Interface (BGX) block. > > Acked-by: Rob Herring > Signed-off-by: Carlos Munoz > Signed-off-by: Steven J. Hill

Re: [PATCH v4 1/8] dt-bindings: Add Cavium Octeon Common Ethernet Interface.

On Tue, Nov 28, 2017 at 04:55:33PM -0800, David Daney wrote: > From: Carlos Munoz > > Add bindings for Common Ethernet Interface (BGX) block. > > Acked-by: Rob Herring > Signed-off-by: Carlos Munoz > Signed-off-by: Steven J. Hill > Signed-off-by: David Daney > --- >

Re: [PATCH v3 4/5] drm/rockchip: Add ROCKCHIP DW MIPI DSI controller driver

On Tue, Nov 28, 2017 at 02:55:41PM -0800, Brian Norris wrote: > Hi Nickey, > > On Tue, Nov 28, 2017 at 12:48:43PM -0800, Matthias Kaehlcke wrote: > > El Tue, Nov 28, 2017 at 07:20:05PM +0800 Nickey Yang ha dit: > > > > > Add the ROCKCHIP DSI controller driver that uses the Synopsys DesignWare >

Re: [PATCH v3 4/5] drm/rockchip: Add ROCKCHIP DW MIPI DSI controller driver

On Tue, Nov 28, 2017 at 02:55:41PM -0800, Brian Norris wrote: > Hi Nickey, > > On Tue, Nov 28, 2017 at 12:48:43PM -0800, Matthias Kaehlcke wrote: > > El Tue, Nov 28, 2017 at 07:20:05PM +0800 Nickey Yang ha dit: > > > > > Add the ROCKCHIP DSI controller driver that uses the Synopsys DesignWare >

Test Mail

Hello, This is just a test mail. Sorry for the inconvenience. Tim 保密声明： 本邮件含有保密或专有信息，仅供指定收件人使用。严禁对本邮件或其内容做任何未经授权的查阅、使用、复制或转发。 CONFIDENTIAL NOTE: This email contains confidential or legally privileged information and is for the sole use of its intended recipient. Any

Test Mail

Hello, This is just a test mail. Sorry for the inconvenience. Tim 保密声明： 本邮件含有保密或专有信息，仅供指定收件人使用。严禁对本邮件或其内容做任何未经授权的查阅、使用、复制或转发。 CONFIDENTIAL NOTE: This email contains confidential or legally privileged information and is for the sole use of its intended recipient. Any

Re: [GIT PULL] seccomp updates for next

On Tue, 28 Nov 2017, Kees Cook wrote: > Hi James, > > Please pull these seccomp changes for next. This implements an interface > for examining seccomp filter metadata when using CRIU. > Applied to next-testing and next-seccomp at:

Re: [GIT PULL] seccomp updates for next

On Tue, 28 Nov 2017, Kees Cook wrote: > Hi James, > > Please pull these seccomp changes for next. This implements an interface > for examining seccomp filter metadata when using CRIU. > Applied to next-testing and next-seccomp at:

Re: KASAN: stack-out-of-bounds Write in sha3_update

On Tue, Nov 28, 2017 at 12:58:45PM -0800, Eric Biggers wrote: > diff --git a/crypto/hmac.c b/crypto/hmac.c > index 92871dc2a63e..82436db6b6a6 100644 > --- a/crypto/hmac.c > +++ b/crypto/hmac.c > @@ -196,6 +196,11 @@ static int hmac_create(struct crypto_template *tmpl, > struct rtattr **tb) >

Re: KASAN: stack-out-of-bounds Write in sha3_update

On Tue, Nov 28, 2017 at 12:58:45PM -0800, Eric Biggers wrote: > diff --git a/crypto/hmac.c b/crypto/hmac.c > index 92871dc2a63e..82436db6b6a6 100644 > --- a/crypto/hmac.c > +++ b/crypto/hmac.c > @@ -196,6 +196,11 @@ static int hmac_create(struct crypto_template *tmpl, > struct rtattr **tb) >

Re: [PATCH v2 2/5] mm: memory_hotplug: Remove assumption on memory state before hotremove

On Wed, Nov 29, 2017 at 08:49:13AM +0800, joeyli wrote: > Hi Andrea, > > On Fri, Nov 24, 2017 at 10:22:35AM +, Andrea Reale wrote: > > Resending the patch adding linux-acpi in CC, as suggested by Rafael. > > Everyone else: apologies for the noise. > > > > Commit 242831eb15a0 ("Memory

Re: [PATCH net,stable] vhost: fix skb leak in handle_rx()

On 2017年11月29日 01:17, w...@redhat.com wrote: From: Wei Xu Matthew found a roughly 40% tcp throughput regression with commit c67df11f(vhost_net: try batch dequing from skb array) as discussed in the following thread:

Re: [PATCH v2 2/5] mm: memory_hotplug: Remove assumption on memory state before hotremove

On Wed, Nov 29, 2017 at 08:49:13AM +0800, joeyli wrote: > Hi Andrea, > > On Fri, Nov 24, 2017 at 10:22:35AM +, Andrea Reale wrote: > > Resending the patch adding linux-acpi in CC, as suggested by Rafael. > > Everyone else: apologies for the noise. > > > > Commit 242831eb15a0 ("Memory

Re: [PATCH net,stable] vhost: fix skb leak in handle_rx()

On 2017年11月29日 01:17, w...@redhat.com wrote: From: Wei Xu Matthew found a roughly 40% tcp throughput regression with commit c67df11f(vhost_net: try batch dequing from skb array) as discussed in the following thread: https://www.mail-archive.com/netdev@vger.kernel.org/msg187936.html

Re: [PATCH v3 1/5] drm/bridge/synopsys: stop clobbering drvdata

On Tue, Nov 28, 2017 at 07:20:02PM +0800, Nickey Yang wrote: Looks like you paved the author. This should be From: Brian. Sean > Bridge drivers/helpers shouldn't be clobbering the drvdata, since a > parent driver might need to own this. Instead, let's return our > 'dw_mipi_dsi' object and have

Re: [PATCH v3 1/5] drm/bridge/synopsys: stop clobbering drvdata

On Tue, Nov 28, 2017 at 07:20:02PM +0800, Nickey Yang wrote: Looks like you paved the author. This should be From: Brian. Sean > Bridge drivers/helpers shouldn't be clobbering the drvdata, since a > parent driver might need to own this. Instead, let's return our > 'dw_mipi_dsi' object and have

[RFC PATCH v2 2/7] ASoC: Intel: Kconfig: Simplify-clarify ACPI/PCI dependencies

PCI/ACPI selections should not happen in Kconfig for machine drivers, move to SOC selections. Add distinction between PCI and ACPI HiFi2 platforms and help text. There should be no functionality change. The PCI-based platforms may be removed at some point since Medfield is not really supported

[RFC PATCH v2 2/7] ASoC: Intel: Kconfig: Simplify-clarify ACPI/PCI dependencies

PCI/ACPI selections should not happen in Kconfig for machine drivers, move to SOC selections. Add distinction between PCI and ACPI HiFi2 platforms and help text. There should be no functionality change. The PCI-based platforms may be removed at some point since Medfield is not really supported

[RFC PATCH v2 1/7] ASoC: Intel: Fix Kconfig with top-level selector

Follow network example suggested by Linus, move Intel definitions in if/endif block and clarify in help text which options distro configurations should enable - everything except legacy Baytrail stuff and NOCODEC (test only) There should be no functionality change - except that sound capabilities

[RFC PATCH v2 1/7] ASoC: Intel: Fix Kconfig with top-level selector

Follow network example suggested by Linus, move Intel definitions in if/endif block and clarify in help text which options distro configurations should enable - everything except legacy Baytrail stuff and NOCODEC (test only) There should be no functionality change - except that sound capabilities

[RFC PATCH v2 3/7] ASoC: Intel: document what Kconfig options do

Document in comments what the options are supposed to mean, before clean-up in next patch. No functionality change here. Signed-off-by: Pierre-Louis Bossart --- sound/soc/intel/Kconfig | 15 --- 1 file changed, 12 insertions(+), 3 deletions(-)

[RFC PATCH v2 3/7] ASoC: Intel: document what Kconfig options do

Document in comments what the options are supposed to mean, before clean-up in next patch. No functionality change here. Signed-off-by: Pierre-Louis Bossart --- sound/soc/intel/Kconfig | 15 --- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/sound/soc/intel/Kconfig

[RFC PATCH v2 4/7] ASoC: Intel: Fix nested/unnecessary Kconfig dependencies

This patch fixes a number of issues: 1. IOSF_MBI is only needed for byt-cr detection, which is only supported on Baytrail/Cherrytrail, move to HiFi2 config 2. SND_SOC_INTEL_SST should not select SND_SOC_INTEL_SST_ACPI, the latter config is only valid for Haswell/Baytrail legacy but not needed by

[RFC PATCH v2 4/7] ASoC: Intel: Fix nested/unnecessary Kconfig dependencies

This patch fixes a number of issues: 1. IOSF_MBI is only needed for byt-cr detection, which is only supported on Baytrail/Cherrytrail, move to HiFi2 config 2. SND_SOC_INTEL_SST should not select SND_SOC_INTEL_SST_ACPI, the latter config is only valid for Haswell/Baytrail legacy but not needed by

[RFC PATCH v2 5/7] ASoC: Intel: boards: align Kconfig dependencies for Haswell/Broadwell

Make sure that the same I2C/I2C_DESIGNWARE_PLATFORM are selected. The latter might actually need to be moved to the SOC side of things, it really has no place in a machine driver dependency Signed-off-by: Pierre-Louis Bossart ---

[RFC PATCH v2 5/7] ASoC: Intel: boards: align Kconfig dependencies for Haswell/Broadwell

Make sure that the same I2C/I2C_DESIGNWARE_PLATFORM are selected. The latter might actually need to be moved to the SOC side of things, it really has no place in a machine driver dependency Signed-off-by: Pierre-Louis Bossart --- sound/soc/intel/boards/Kconfig | 2 +- 1 file changed, 1

[RFC PATCH v2 6/7] ASoC: Intel: boards: align Kconfig configurations for HiFi2

Make sure all the configs are aligned Also add the missing dependencies on SOC_ACPI stuff used to fix DAI names based on HID and fix a couple of indentation issues Signed-off-by: Pierre-Louis Bossart --- sound/soc/intel/boards/Kconfig | 33

Re: [PATCH v2 2/2] ASoC: fsl_ssi: call _fsl_ssi_set_dai_fmt() just once in AC'97 mode

On Wed, Nov 22, 2017 at 12:55:14AM +0100, Maciej S. Szmigiero wrote: > In AC'97 mode we configure and start SSI RX / TX on probe path via > a call to _fsl_ssi_set_dai_fmt() function. > We don't need to call this function again later and in fact don't want to > do it since this function temporarily

[RFC PATCH v2 6/7] ASoC: Intel: boards: align Kconfig configurations for HiFi2

Make sure all the configs are aligned Also add the missing dependencies on SOC_ACPI stuff used to fix DAI names based on HID and fix a couple of indentation issues Signed-off-by: Pierre-Louis Bossart --- sound/soc/intel/boards/Kconfig | 33 +++-- 1 file changed, 19

Re: [PATCH v2 2/2] ASoC: fsl_ssi: call _fsl_ssi_set_dai_fmt() just once in AC'97 mode

On Wed, Nov 22, 2017 at 12:55:14AM +0100, Maciej S. Szmigiero wrote: > In AC'97 mode we configure and start SSI RX / TX on probe path via > a call to _fsl_ssi_set_dai_fmt() function. > We don't need to call this function again later and in fact don't want to > do it since this function temporarily

[RFC PATCH v2 7/7] ASoC: Intel: boards: align/fix SKL/BXT/KBL Kconfigs

No reason why SND_SOC_INTEL_SST should be set here. Also make sure same dependencies are used everywhere (only last one has SPI in addition). Replace X86_INTEL_LPSS by MFD_INTEL_LPSS since the former makes no sense for Skylake+ devices Signed-off-by: Pierre-Louis Bossart

[RFC PATCH v2 7/7] ASoC: Intel: boards: align/fix SKL/BXT/KBL Kconfigs

No reason why SND_SOC_INTEL_SST should be set here. Also make sure same dependencies are used everywhere (only last one has SPI in addition). Replace X86_INTEL_LPSS by MFD_INTEL_LPSS since the former makes no sense for Skylake+ devices Signed-off-by: Pierre-Louis Bossart ---

Re: [alsa-devel] [PATCH v2 1/2] ASoC: fsl_ssi: only enable proper channel slots in AC'97 mode

On Wed, Nov 22, 2017 at 12:54:26AM +0100, Maciej S. Szmigiero wrote: > We need to make sure that only proper channel slots (in SACCST register) > are enabled at playback start time since some AC'97 CODECs (like VT1613 on > UDOO board) were observed requesting via SLOTREQ spurious ones just after >

[RFC PATCH v2 0/7] Fix Intel audio Kconfig issues

The first patch implements what Linus, Takashi and Mark requested: a top-level selector defaulting to 'y' to easily filter all other options and with no impact on code generation. There should be no functionality change and will avoid breaking audio for people using make oldnoconfig. The rest of

Re: [alsa-devel] [PATCH v2 1/2] ASoC: fsl_ssi: only enable proper channel slots in AC'97 mode

On Wed, Nov 22, 2017 at 12:54:26AM +0100, Maciej S. Szmigiero wrote: > We need to make sure that only proper channel slots (in SACCST register) > are enabled at playback start time since some AC'97 CODECs (like VT1613 on > UDOO board) were observed requesting via SLOTREQ spurious ones just after >

[RFC PATCH v2 0/7] Fix Intel audio Kconfig issues

The first patch implements what Linus, Takashi and Mark requested: a top-level selector defaulting to 'y' to easily filter all other options and with no impact on code generation. There should be no functionality change and will avoid breaking audio for people using make oldnoconfig. The rest of

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