[PATCH 3.18 57/93] media: v4l2-ioctl.c: dont copy back the result for -ENOTTY

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hans Verkuil commit 181a4a2d5a0a7b43cab08a70710d727e7764ccdd upstream. If the ioctl returned -ENOTTY, then don't bother copying back the result as there is no point. Signed-off-by: Hans

[PATCH 3.18 60/93] media: v4l2-compat-ioctl32.c: fix the indentation

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hans Verkuil commit b7b957d429f601d6d1942122b339474f31191d75 upstream. The indentation of this source is all over the place. Fix this. This patch only changes whitespace. Signed-off-by: Hans

[PATCH 3.18 17/93] can: cc770: Fix queue stall & dropped RTR reply

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Andri Yngvason commit 746201235b3f876792099079f4c6fea941d76183 upstream. While waiting for the TX object to send an RTR, an external message with a matching id can

[PATCH 3.18 17/93] can: cc770: Fix queue stall & dropped RTR reply

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Andri Yngvason commit 746201235b3f876792099079f4c6fea941d76183 upstream. While waiting for the TX object to send an RTR, an external message with a matching id can overwrite the TX data. In

[PATCH 3.18 35/93] s390/qeth: on channel error, reject further cmd requests

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Julian Wiedmann [ Upstream commit a6c3d93963e4b333c764fde69802c3ea9eaa9d5c ] When the IRQ handler determines that one of the cmd IO channels has failed and schedules

[PATCH 3.18 35/93] s390/qeth: on channel error, reject further cmd requests

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Julian Wiedmann [ Upstream commit a6c3d93963e4b333c764fde69802c3ea9eaa9d5c ] When the IRQ handler determines that one of the cmd IO channels has failed and schedules recovery, block any

[PATCH 3.18 24/93] ipv6: fix access to non-linear packet in ndisc_fill_redirect_hdr_option()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Lorenzo Bianconi [ Upstream commit 9f62c15f28b0d1d746734666d88a79f08ba1e43e ] Fix the following slab-out-of-bounds kasan report in ndisc_fill_redirect_hdr_option

[PATCH 3.18 24/93] ipv6: fix access to non-linear packet in ndisc_fill_redirect_hdr_option()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Lorenzo Bianconi [ Upstream commit 9f62c15f28b0d1d746734666d88a79f08ba1e43e ] Fix the following slab-out-of-bounds kasan report in ndisc_fill_redirect_hdr_option when the incoming ipv6

[PATCH 3.18 14/93] tracing: probeevent: Fix to support minus offset from symbol

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Masami Hiramatsu commit c5d343b6b7badd1f5fe0873eff2e8d63a193e732 upstream. In Documentation/trace/kprobetrace.txt, it says @SYM[+|-offs] : Fetch memory at SYM +|- offs

[PATCH 3.18 41/93] partitions/msdos: Unable to mount UFS 44bsd partitions

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Richard Narron commit 5f15684bd5e5ef39d4337988864fec8012471dda upstream. UFS partitions from newer versions of FreeBSD 10 and 11 use relative addressing for their

[PATCH 3.18 42/93] usb: gadget: define free_ep_req as universal function

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Felipe F. Tonello commit 079fe5a6da616891cca1a26e803e1df2a87e9ae5 upstream. This function is shared between gadget functions, so this avoid unnecessary duplicated code

[PATCH 3.18 41/93] partitions/msdos: Unable to mount UFS 44bsd partitions

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Richard Narron commit 5f15684bd5e5ef39d4337988864fec8012471dda upstream. UFS partitions from newer versions of FreeBSD 10 and 11 use relative addressing for their subpartitions. But older

[PATCH 3.18 42/93] usb: gadget: define free_ep_req as universal function

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Felipe F. Tonello commit 079fe5a6da616891cca1a26e803e1df2a87e9ae5 upstream. This function is shared between gadget functions, so this avoid unnecessary duplicated code and potentially avoid

[PATCH 3.18 14/93] tracing: probeevent: Fix to support minus offset from symbol

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Masami Hiramatsu commit c5d343b6b7badd1f5fe0873eff2e8d63a193e732 upstream. In Documentation/trace/kprobetrace.txt, it says @SYM[+|-offs] : Fetch memory at SYM +|- offs (SYM should be a data

[PATCH 3.18 09/93] libata: Apply NOLPM quirk to Crucial M500 480 and 960GB SSDs

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit 62ac3f7305470e3f52f159de448bc1a771717e88 upstream. There have been reports of the Crucial M500 480GB model not working with LPM set to min_power /

[PATCH 3.18 00/93] 3.18.103-stable review

This is the start of the stable review cycle for the 3.18.103 release. There are 93 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Sun Apr 8 08:42:04 UTC 2018. Anything

[PATCH 3.18 09/93] libata: Apply NOLPM quirk to Crucial M500 480 and 960GB SSDs

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit 62ac3f7305470e3f52f159de448bc1a771717e88 upstream. There have been reports of the Crucial M500 480GB model not working with LPM set to min_power / med_power_with_dipm

[PATCH 3.18 00/93] 3.18.103-stable review

This is the start of the stable review cycle for the 3.18.103 release. There are 93 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Sun Apr 8 08:42:04 UTC 2018. Anything

[PATCH 3.18 02/93] ALSA: aloop: Sync stale timer before release

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 67a01afaf3d34893cf7d2ea19b34555d6abb7cb0 upstream. The aloop driver tries to stop the pending timer via timer_del() in the trigger callback and in the close

[PATCH 3.18 07/93] libata: disable LPM for Crucial BX100 SSD 500GB drive

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Kai-Heng Feng commit b17e5729a630d8326a48ec34ef02e6b4464a6aef upstream. After Laptop Mode Tools starts to use min_power for LPM, a user found out Crucial BX100

[PATCH 3.18 01/93] ALSA: usb-audio: Fix parsing descriptor of UAC2 processing unit

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Kirill Marinushkin commit a6618f4aedb2b60932d766bd82ae7ce866e842aa upstream. Currently, the offsets in the UAC2 processing unit descriptor are calculated incorrectly.

[PATCH 3.18 07/93] libata: disable LPM for Crucial BX100 SSD 500GB drive

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Kai-Heng Feng commit b17e5729a630d8326a48ec34ef02e6b4464a6aef upstream. After Laptop Mode Tools starts to use min_power for LPM, a user found out Crucial BX100 SSD can't get mounted. Crucial

[PATCH 3.18 01/93] ALSA: usb-audio: Fix parsing descriptor of UAC2 processing unit

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Kirill Marinushkin commit a6618f4aedb2b60932d766bd82ae7ce866e842aa upstream. Currently, the offsets in the UAC2 processing unit descriptor are calculated incorrectly. It causes an issue when

[PATCH 3.18 02/93] ALSA: aloop: Sync stale timer before release

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 67a01afaf3d34893cf7d2ea19b34555d6abb7cb0 upstream. The aloop driver tries to stop the pending timer via timer_del() in the trigger callback and in the close callback. The

Re: Commit *driver core: emit uevents when device is bound to a driver* causes regression

Dear Greg, On 04/06/18 15:18, Greg Kroah-Hartman wrote: On Fri, Apr 06, 2018 at 02:20:40PM +0200, Paul Menzel wrote: Commit 1455cf8 (driver core: emit uevents when device is bound to a driver) [1], introduced in Linux 4.14-rc1, causes a regression in user space. After disconnecting USB

Re: Commit *driver core: emit uevents when device is bound to a driver* causes regression

Dear Greg, On 04/06/18 15:18, Greg Kroah-Hartman wrote: On Fri, Apr 06, 2018 at 02:20:40PM +0200, Paul Menzel wrote: Commit 1455cf8 (driver core: emit uevents when device is bound to a driver) [1], introduced in Linux 4.14-rc1, causes a regression in user space. After disconnecting USB

INFO: rcu detected stall in snd_pcm_stream_lock_irq

Hello, syzbot hit the following crash on upstream commit 38c23685b273cfb4ccf31a199feccce3bdcb5d83 (Fri Apr 6 04:29:35 2018 +) Merge tag 'armsoc-drivers' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc syzbot dashboard link:

Re: [PATCH v7 2/2] drm: bridge: Add thc63lvd1024 LVDS decoder driver

Hi Jacopo, Thank you for the patch. On Friday, 6 April 2018 15:41:57 EEST Jacopo Mondi wrote: > Add DRM bridge driver for Thine THC63LVD1024 LVDS to digital parallel > output converter. > > Signed-off-by: Jacopo Mondi > Reviewed-by: Andrzej Hajda

INFO: rcu detected stall in snd_pcm_stream_lock_irq

Hello, syzbot hit the following crash on upstream commit 38c23685b273cfb4ccf31a199feccce3bdcb5d83 (Fri Apr 6 04:29:35 2018 +) Merge tag 'armsoc-drivers' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc syzbot dashboard link:

Re: [PATCH v7 2/2] drm: bridge: Add thc63lvd1024 LVDS decoder driver

Hi Jacopo, Thank you for the patch. On Friday, 6 April 2018 15:41:57 EEST Jacopo Mondi wrote: > Add DRM bridge driver for Thine THC63LVD1024 LVDS to digital parallel > output converter. > > Signed-off-by: Jacopo Mondi > Reviewed-by: Andrzej Hajda > Reviewed-by: Niklas Söderlund > --- >

WARNING in kmem_cache_free

Hello, syzbot hit the following crash on upstream commit f2d285669aae656dfeafa0bf25e86bbbc5d22329 (Tue Apr 3 17:45:39 2018 +) Merge tag 'pm-4.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm syzbot dashboard link:

WARNING in kmem_cache_free

Hello, syzbot hit the following crash on upstream commit f2d285669aae656dfeafa0bf25e86bbbc5d22329 (Tue Apr 3 17:45:39 2018 +) Merge tag 'pm-4.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm syzbot dashboard link:

Re: [PATCH v4] dell_rbu: make firmware payload memory uncachable

On Fri, 06 Apr 2018 15:12:21 +0200, Stuart Hayes wrote: > > The dell_rbu driver takes firmware update payloads and puts them in memory so > the system BIOS can find them after a reboot. This sometimes fails (though > rarely), because the memory containing the payload is in the CPU cache but >

Re: [PATCH v4] dell_rbu: make firmware payload memory uncachable

On Fri, 06 Apr 2018 15:12:21 +0200, Stuart Hayes wrote: > > The dell_rbu driver takes firmware update payloads and puts them in memory so > the system BIOS can find them after a reboot. This sometimes fails (though > rarely), because the memory containing the payload is in the CPU cache but >

Re: [PATCH 00/10] kernel/locking: qspinlock improvements

On Thu, Apr 05, 2018 at 05:58:57PM +0100, Will Deacon wrote: > Hi all, > > I've been kicking the tyres further on qspinlock and with this set of patches > I'm happy with the performance and fairness properties. In particular, the > locking algorithm now guarantees forward progress whereas the

Re: [PATCH 00/10] kernel/locking: qspinlock improvements

On Thu, Apr 05, 2018 at 05:58:57PM +0100, Will Deacon wrote: > Hi all, > > I've been kicking the tyres further on qspinlock and with this set of patches > I'm happy with the performance and fairness properties. In particular, the > locking algorithm now guarantees forward progress whereas the

Re: INFO: rcu detected stall in __snd_pcm_lib_xfer (2)

On Fri, Apr 6, 2018 at 2:52 PM, Takashi Iwai wrote: > On Fri, 06 Apr 2018 09:08:01 +0200, > syzbot wrote: >> >> Hello, >> >> syzbot hit the following crash on upstream commit >> e02d37bf55a9a36f22427fd6dd733fe104d817b6 (Thu Apr 5 17:42:07 2018 +) >> Merge tag 'sound-4.17-rc1'

Re: INFO: rcu detected stall in __snd_pcm_lib_xfer (2)

On Fri, Apr 6, 2018 at 2:52 PM, Takashi Iwai wrote: > On Fri, 06 Apr 2018 09:08:01 +0200, > syzbot wrote: >> >> Hello, >> >> syzbot hit the following crash on upstream commit >> e02d37bf55a9a36f22427fd6dd733fe104d817b6 (Thu Apr 5 17:42:07 2018 +) >> Merge tag 'sound-4.17-rc1' of >>

Re: [PATCH v4 1/5] io: define several IO & PIO barrier types for the asm-generic version

On Fri, Apr 6, 2018 at 2:50 PM, wrote: > On 2018-04-06 06:19, Arnd Bergmann wrote: >> >> On Thu, Apr 5, 2018 at 3:09 PM, Sinan Kaya wrote: >>> >> >> I would guess that at least s390 doesn't need the barriers >> (maintainers on Cc now), but there may

Re: [PATCH v4 1/5] io: define several IO & PIO barrier types for the asm-generic version

On Fri, Apr 6, 2018 at 2:50 PM, wrote: > On 2018-04-06 06:19, Arnd Bergmann wrote: >> >> On Thu, Apr 5, 2018 at 3:09 PM, Sinan Kaya wrote: >>> >> >> I would guess that at least s390 doesn't need the barriers >> (maintainers on Cc now), but there may be others that want to >> override the new

[PATCH v3 2/2] iommu/amd: Add basic debugfs infrastructure for AMD IOMMU

Implement a skeleton framework for debugfs support in the AMD IOMMU. Signed-off-by: Gary R Hook --- drivers/iommu/Makefile|1 + drivers/iommu/amd_iommu_debugfs.c | 45 + drivers/iommu/amd_iommu_init.c|6 +++--

[PATCH v3 2/2] iommu/amd: Add basic debugfs infrastructure for AMD IOMMU

Implement a skeleton framework for debugfs support in the AMD IOMMU. Signed-off-by: Gary R Hook --- drivers/iommu/Makefile|1 + drivers/iommu/amd_iommu_debugfs.c | 45 + drivers/iommu/amd_iommu_init.c|6 +++--

Re: Commit *driver core: emit uevents when device is bound to a driver* causes regression

On Fri, Apr 06, 2018 at 02:20:40PM +0200, Paul Menzel wrote: > Dear Linux folks, > > > Commit 1455cf8 (driver core: emit uevents when device is bound to a > driver) [1], introduced in Linux 4.14-rc1, causes a regression in user > space. > > After disconnecting USB devices, they are still shown

Re: Commit *driver core: emit uevents when device is bound to a driver* causes regression

On Fri, Apr 06, 2018 at 02:20:40PM +0200, Paul Menzel wrote: > Dear Linux folks, > > > Commit 1455cf8 (driver core: emit uevents when device is bound to a > driver) [1], introduced in Linux 4.14-rc1, causes a regression in user > space. > > After disconnecting USB devices, they are still shown

[PATCH v3 1/2] iommu - Enable debugfs exposure of the IOMMU

Provide base enablement for using debugfs to expose internal data of an IOMMU driver. When called, create the /sys/kernel/debug/iommu directory. Emit a strong warning at boot time to indicate that this feature is enabled. This patch adds a top-level function that will create the (above)

Re: [PATCH v7 0/2] drm: Add Thine THC63LVD1024 LVDS decoder bridge

Sorry for the mess subject should have been Subject: [PATCH 0/7] V3M-Eagle display enablement I copied the wrong one from another cover letter... On Fri, Apr 06, 2018 at 03:08:05PM +0200, Jacopo Mondi wrote: > Hello, >this series enables HDMI display on V3M Eagle board. > > The series

[PATCH v3 0/2] Base enablement of IOMMU debugfs support

These patches create a top-level function to create a debugfs directory for the IOMMU, under which drivers may create and populate-specific directories for their device internals. Patch 1: general IOMMU enablement Patch 2: basic AMD enablement to demonstrate linkage with patch 1 Introduce a new

[PATCH v3 1/2] iommu - Enable debugfs exposure of the IOMMU

Provide base enablement for using debugfs to expose internal data of an IOMMU driver. When called, create the /sys/kernel/debug/iommu directory. Emit a strong warning at boot time to indicate that this feature is enabled. This patch adds a top-level function that will create the (above)

Re: [PATCH v7 0/2] drm: Add Thine THC63LVD1024 LVDS decoder bridge

Sorry for the mess subject should have been Subject: [PATCH 0/7] V3M-Eagle display enablement I copied the wrong one from another cover letter... On Fri, Apr 06, 2018 at 03:08:05PM +0200, Jacopo Mondi wrote: > Hello, >this series enables HDMI display on V3M Eagle board. > > The series

[PATCH v3 0/2] Base enablement of IOMMU debugfs support

These patches create a top-level function to create a debugfs directory for the IOMMU, under which drivers may create and populate-specific directories for their device internals. Patch 1: general IOMMU enablement Patch 2: basic AMD enablement to demonstrate linkage with patch 1 Introduce a new

Re: [PATCH v4 4/9] vsprintf: Consolidate handling of unknown pointer specifiers

On 2018-04-06 13:43, Petr Mladek wrote: > On Thu 2018-04-05 16:55:35, Joe Perches wrote: >> On Thu, 2018-04-05 at 16:45 -0700, Joe Perches wrote: >>> On Thu, 2018-04-05 at 16:25 +0200, Rasmus Villemoes wrote: Even just git grep -1 -E '%p"$' finds %pt and %po which should get fixed before

Re: [PATCH v4 4/9] vsprintf: Consolidate handling of unknown pointer specifiers

On 2018-04-06 13:43, Petr Mladek wrote: > On Thu 2018-04-05 16:55:35, Joe Perches wrote: >> On Thu, 2018-04-05 at 16:45 -0700, Joe Perches wrote: >>> On Thu, 2018-04-05 at 16:25 +0200, Rasmus Villemoes wrote: Even just git grep -1 -E '%p"$' finds %pt and %po which should get fixed before

Re: [PATCH v7 1/2] dt-bindings: display: bridge: Document THC63LVD1024 LVDS decoder

Hi Jacopo, Thank you for the patch. On Friday, 6 April 2018 15:41:56 EEST Jacopo Mondi wrote: > Document Thine THC63LVD1024 LVDS decoder device tree bindings. > > Signed-off-by: Jacopo Mondi > Reviewed-by: Andrzej Hajda > Reviewed-by: Niklas

Re: [PATCH v7 1/2] dt-bindings: display: bridge: Document THC63LVD1024 LVDS decoder

Hi Jacopo, Thank you for the patch. On Friday, 6 April 2018 15:41:56 EEST Jacopo Mondi wrote: > Document Thine THC63LVD1024 LVDS decoder device tree bindings. > > Signed-off-by: Jacopo Mondi > Reviewed-by: Andrzej Hajda > Reviewed-by: Niklas Söderlund > Reviewed-by: Laurent Pinchart > --- >

[PATCH] dts: remove cris & metag dts hard link file

arch cris & metag have been removed from supported archs. The dts hard link files should also be removed, or the ctags tool will give warning. execute"ctags -R", output: ctags: Warning: cannot open source file "scripts/dtc/include-prefixes/cris" : No such file or directory ctags: Warning: cannot

[PATCH] dts: remove cris & metag dts hard link file

arch cris & metag have been removed from supported archs. The dts hard link files should also be removed, or the ctags tool will give warning. execute"ctags -R", output: ctags: Warning: cannot open source file "scripts/dtc/include-prefixes/cris" : No such file or directory ctags: Warning: cannot

Re: [PATCH v4 6/9] vsprintf: Factor out %pV handler as va_format()

On Wed 2018-04-04 07:26:07, Joe Perches wrote: > On Wed, 2018-04-04 at 10:58 +0200, Petr Mladek wrote: > > Move the code from the long pointer() function. We are going to add a check > > for the access to the address that will make it even more complicated. > > > > This patch does not change the

Re: [PATCH v4 6/9] vsprintf: Factor out %pV handler as va_format()

On Wed 2018-04-04 07:26:07, Joe Perches wrote: > On Wed, 2018-04-04 at 10:58 +0200, Petr Mladek wrote: > > Move the code from the long pointer() function. We are going to add a check > > for the access to the address that will make it even more complicated. > > > > This patch does not change the

Re: [PATCH v4 8/9] vsprintf: Prevent crash when dereferencing invalid pointers

On 2018-04-06 14:26, Petr Mladek wrote: > On Thu 2018-04-05 16:46:23, Rasmus Villemoes wrote: >> On 2018-04-04 10:58, Petr Mladek wrote: >> >>> diff --git a/lib/vsprintf.c b/lib/vsprintf.c >>> index 3551b7957d9e..1a080a75a825 100644 >>> --- a/lib/vsprintf.c >>> +++ b/lib/vsprintf.c >>> @@ -599,12

Re: [PATCH v4 8/9] vsprintf: Prevent crash when dereferencing invalid pointers

On 2018-04-06 14:26, Petr Mladek wrote: > On Thu 2018-04-05 16:46:23, Rasmus Villemoes wrote: >> On 2018-04-04 10:58, Petr Mladek wrote: >> >>> diff --git a/lib/vsprintf.c b/lib/vsprintf.c >>> index 3551b7957d9e..1a080a75a825 100644 >>> --- a/lib/vsprintf.c >>> +++ b/lib/vsprintf.c >>> @@ -599,12

[PATCH v4] dell_rbu: make firmware payload memory uncachable

The dell_rbu driver takes firmware update payloads and puts them in memory so the system BIOS can find them after a reboot. This sometimes fails (though rarely), because the memory containing the payload is in the CPU cache but never gets written back to main memory before the system is rebooted

[PATCH v4] dell_rbu: make firmware payload memory uncachable

The dell_rbu driver takes firmware update payloads and puts them in memory so the system BIOS can find them after a reboot. This sometimes fails (though rarely), because the memory containing the payload is in the CPU cache but never gets written back to main memory before the system is rebooted

[PATCH 2/7] arm64: dts: renesas: r8a77970: add VSPD support

From: Sergei Shtylyov Describe VSPD0 in the R8A77970 device tree; it will be used by DU in the next patch... Based on the original (and large) patch by Daisuke Matsushita . Signed-off-by: Vladimir Barinov

[PATCH v7 0/2] drm: Add Thine THC63LVD1024 LVDS decoder bridge

Hello, this series enables HDMI display on V3M Eagle board. The series is based on Geert's "renesas-drivers-2018-04-03-v4.16" with THC63LVD1024 driver on top (cfr. my in review series: "[PATCH v7 0/2] drm: Add Thine THC63LVD1024 LVDS decoder bridge") This series includes some preliminary

[PATCH 2/7] arm64: dts: renesas: r8a77970: add VSPD support

From: Sergei Shtylyov Describe VSPD0 in the R8A77970 device tree; it will be used by DU in the next patch... Based on the original (and large) patch by Daisuke Matsushita . Signed-off-by: Vladimir Barinov Signed-off-by: Sergei Shtylyov Signed-off-by: Niklas Söderlund ---

[PATCH v7 0/2] drm: Add Thine THC63LVD1024 LVDS decoder bridge

Hello, this series enables HDMI display on V3M Eagle board. The series is based on Geert's "renesas-drivers-2018-04-03-v4.16" with THC63LVD1024 driver on top (cfr. my in review series: "[PATCH v7 0/2] drm: Add Thine THC63LVD1024 LVDS decoder bridge") This series includes some preliminary

[PATCH 4/7] arm64: dts: renesas: r8a77970: add the LVDS instance

From: Niklas Söderlund Add the LVDS device to r8a77970.dtsi in a disabled state. Also connect the it to the LVDS output of the DU. While at it align the endpoint name of the du to du_out_lvds0 which is used in other Renesas DTS files to describe this link.

[PATCH 4/7] arm64: dts: renesas: r8a77970: add the LVDS instance

From: Niklas Söderlund Add the LVDS device to r8a77970.dtsi in a disabled state. Also connect the it to the LVDS output of the DU. While at it align the endpoint name of the du to du_out_lvds0 which is used in other Renesas DTS files to describe this link. Signed-off-by: Niklas Söderlund ---

[PATCH 3/7] arm64: dts: renesas: r8a77970: add DU support

From: Sergei Shtylyov Define the generic R8A77970 part of the DU device node. Based on the original (and large) patch by Daisuke Matsushita . Signed-off-by: Vladimir Barinov

[PATCH 1/7] arm64: dts: renesas: r8a77970: add FCPVD support

From: Sergei Shtylyov Describe FCPVD0 in the R8A77970 device tree; it will be used by VSPD0 in the next patch... Based on the original (and large) patch by Daisuke Matsushita . Signed-off-by: Vladimir Barinov

[PATCH 3/7] arm64: dts: renesas: r8a77970: add DU support

From: Sergei Shtylyov Define the generic R8A77970 part of the DU device node. Based on the original (and large) patch by Daisuke Matsushita . Signed-off-by: Vladimir Barinov Signed-off-by: Sergei Shtylyov Signed-off-by: Niklas Söderlund --- arch/arm64/boot/dts/renesas/r8a77970.dtsi | 28

[PATCH 1/7] arm64: dts: renesas: r8a77970: add FCPVD support

From: Sergei Shtylyov Describe FCPVD0 in the R8A77970 device tree; it will be used by VSPD0 in the next patch... Based on the original (and large) patch by Daisuke Matsushita . Signed-off-by: Vladimir Barinov Signed-off-by: Sergei Shtylyov Signed-off-by: Niklas Söderlund ---

[PATCH 7/7] arm64: dts: renesas: eagle: Add ADV7511W and HDMI output

From: Niklas Söderlund Enable HDMI output adding the HDMI connector and the ADV7511W, connected to THC63LVD1024 LVDS decoder output. Signed-off-by: Niklas Söderlund Signed-off-by: Jacopo Mondi

[PATCH 7/7] arm64: dts: renesas: eagle: Add ADV7511W and HDMI output

From: Niklas Söderlund Enable HDMI output adding the HDMI connector and the ADV7511W, connected to THC63LVD1024 LVDS decoder output. Signed-off-by: Niklas Söderlund Signed-off-by: Jacopo Mondi --- arch/arm64/boot/dts/renesas/r8a77970-eagle.dts | 51 +- 1 file changed,

[PATCH 6/7] arm64: dts: renesas: eagle: Add LVDS decoder

The R-Car V3M Eagle board includes a transparent THC63LVD1024 LVDS decoder, connected to the on-chip LVDS encoder output on one side and to the not-yet-described HDMI encoder ADV7511W on the other one. As the decoder does not need any configuration it has been so-far omitted from DTS. Now that a

[PATCH 6/7] arm64: dts: renesas: eagle: Add LVDS decoder

The R-Car V3M Eagle board includes a transparent THC63LVD1024 LVDS decoder, connected to the on-chip LVDS encoder output on one side and to the not-yet-described HDMI encoder ADV7511W on the other one. As the decoder does not need any configuration it has been so-far omitted from DTS. Now that a

[PATCH 5/7] arm64: dts: renesas: eagle: Enable DU

Enable DU for Renesas R-Car V3M Eagle board. Signed-off-by: Jacopo Mondi --- arch/arm64/boot/dts/renesas/r8a77970-eagle.dts | 11 +++ 1 file changed, 11 insertions(+) diff --git a/arch/arm64/boot/dts/renesas/r8a77970-eagle.dts

[PATCH 5/7] arm64: dts: renesas: eagle: Enable DU

Enable DU for Renesas R-Car V3M Eagle board. Signed-off-by: Jacopo Mondi --- arch/arm64/boot/dts/renesas/r8a77970-eagle.dts | 11 +++ 1 file changed, 11 insertions(+) diff --git a/arch/arm64/boot/dts/renesas/r8a77970-eagle.dts b/arch/arm64/boot/dts/renesas/r8a77970-eagle.dts index

Re: [PATCH 0/8] use struct pt_regs based syscall calling for x86-64

On Fri, Apr 06, 2018 at 02:34:20PM +0200, Ingo Molnar wrote: > > * Dominik Brodowski wrote: > > > > > __sys_mprotect as prefix won't work by the way, as the > > > > double-underscore __sys_ > > > > variant is already used in net/* for internal syscall helpers. > >

Re: [PATCH 0/8] use struct pt_regs based syscall calling for x86-64

On Fri, Apr 06, 2018 at 02:34:20PM +0200, Ingo Molnar wrote: > > * Dominik Brodowski wrote: > > > > > __sys_mprotect as prefix won't work by the way, as the > > > > double-underscore __sys_ > > > > variant is already used in net/* for internal syscall helpers. > > > > > > Ok - then triple

Re: [PATCH net-next] netns: filter uevents correctly

On Thu, Apr 05, 2018 at 10:59:49PM -0500, Eric W. Biederman wrote: > Christian Brauner writes: > > > On Thu, Apr 05, 2018 at 05:26:59PM +0300, Kirill Tkhai wrote: > >> On 05.04.2018 17:07, Christian Brauner wrote: > >> > On Thu, Apr 05, 2018 at 04:01:03PM +0300,

Re: [PATCH net-next] netns: filter uevents correctly

On Thu, Apr 05, 2018 at 10:59:49PM -0500, Eric W. Biederman wrote: > Christian Brauner writes: > > > On Thu, Apr 05, 2018 at 05:26:59PM +0300, Kirill Tkhai wrote: > >> On 05.04.2018 17:07, Christian Brauner wrote: > >> > On Thu, Apr 05, 2018 at 04:01:03PM +0300, Kirill Tkhai wrote: > >> >> On

Re: [PATCH v3 04/13] ARM: dts: ipq4019: Update ipq4019-dk01.1 board data

On 2018-04-06 10:25, Richard Cochran wrote: On Mon, Apr 02, 2018 at 03:28:47PM +0530, sricha...@codeaurora.org wrote: Yes, i will post another series for ipq806[2/4] updates and the corresponding boards after this. I tried mainline on the ap148 using qcom_defconfig and the

Re: [PATCH v3 04/13] ARM: dts: ipq4019: Update ipq4019-dk01.1 board data

On 2018-04-06 10:25, Richard Cochran wrote: On Mon, Apr 02, 2018 at 03:28:47PM +0530, sricha...@codeaurora.org wrote: Yes, i will post another series for ipq806[2/4] updates and the corresponding boards after this. I tried mainline on the ap148 using qcom_defconfig and the

[for-next][PATCH 04/18] tracing: Mention trace_clock=global when warning about unstable clocks

From: Chris Wilson Mention the alternative of adding trace_clock=global to the kernel command line when we detect that we've used an unstable clock across a suspend/resume cycle. Link: http://lkml.kernel.org/r/20180330150132.16903-2-ch...@chris-wilson.co.uk

[for-next][PATCH 04/18] tracing: Mention trace_clock=global when warning about unstable clocks

From: Chris Wilson Mention the alternative of adding trace_clock=global to the kernel command line when we detect that we've used an unstable clock across a suspend/resume cycle. Link: http://lkml.kernel.org/r/20180330150132.16903-2-ch...@chris-wilson.co.uk Signed-off-by: Chris Wilson

[for-next][PATCH 09/18] tracing: Make sure variable string fields are NULL-terminated

From: Tom Zanussi The strncpy() currently being used for variable string fields can result in a lack of termination if the string length is equal to the field size. Use the safer strscpy() instead, which will guarantee termination. Link:

[for-next][PATCH 09/18] tracing: Make sure variable string fields are NULL-terminated

From: Tom Zanussi The strncpy() currently being used for variable string fields can result in a lack of termination if the string length is equal to the field size. Use the safer strscpy() instead, which will guarantee termination. Link:

[for-next][PATCH 03/18] tracing: Default to using trace_global_clock if sched_clock is unstable

From: Chris Wilson Across suspend, we may see a very large drift in timestamps if the sched clock is unstable, prompting the global trace's ringbuffer code to warn and suggest switching to the global clock. Preempt this request by detecting when the sched clock is

[for-next][PATCH 03/18] tracing: Default to using trace_global_clock if sched_clock is unstable

From: Chris Wilson Across suspend, we may see a very large drift in timestamps if the sched clock is unstable, prompting the global trace's ringbuffer code to warn and suggest switching to the global clock. Preempt this request by detecting when the sched clock is unstable (determined during

[for-next][PATCH 10/18] tracing: Uninitialized variable in create_tracing_map_fields()

From: Dan Carpenter Smatch complains that idx can be used uninitialized when we check if (idx < 0). It has to be the first iteration through the loop and the HIST_FIELD_FL_STACKTRACE bit has to be clear and the HIST_FIELD_FL_VAR bit has to be set to reach the bug.

[for-next][PATCH 10/18] tracing: Uninitialized variable in create_tracing_map_fields()

From: Dan Carpenter Smatch complains that idx can be used uninitialized when we check if (idx < 0). It has to be the first iteration through the loop and the HIST_FIELD_FL_STACKTRACE bit has to be clear and the HIST_FIELD_FL_VAR bit has to be set to reach the bug. Link:

[for-next][PATCH 02/18] init: Fix initcall0 name as it is "pure" not "early"

From: "Steven Rostedt (VMware)" The early_initcall() functions get assigned to __initcall_start[]. These are called by do_pre_smp_initcalls(). The initcall_levels[] array starts with __initcall0_start[], and initcall_levels[] are to match the initcall_level_names[] array.

[for-next][PATCH 02/18] init: Fix initcall0 name as it is "pure" not "early"

From: "Steven Rostedt (VMware)" The early_initcall() functions get assigned to __initcall_start[]. These are called by do_pre_smp_initcalls(). The initcall_levels[] array starts with __initcall0_start[], and initcall_levels[] are to match the initcall_level_names[] array. The first name in that

Re: [PATCH 10/10] locking/qspinlock: Elide back-to-back RELEASE operations with smp_wmb()

Hi Will, On Fri, Apr 06, 2018 at 12:34:36PM +0100, Will Deacon wrote: > On Thu, Apr 05, 2018 at 07:28:08PM +0200, Peter Zijlstra wrote: > > On Thu, Apr 05, 2018 at 05:59:07PM +0100, Will Deacon wrote: > > > @@ -340,12 +341,17 @@ void queued_spin_lock_slowpath(struct qspinlock > > > *lock, u32

Re: [PATCH 10/10] locking/qspinlock: Elide back-to-back RELEASE operations with smp_wmb()

Hi Will, On Fri, Apr 06, 2018 at 12:34:36PM +0100, Will Deacon wrote: > On Thu, Apr 05, 2018 at 07:28:08PM +0200, Peter Zijlstra wrote: > > On Thu, Apr 05, 2018 at 05:59:07PM +0100, Will Deacon wrote: > > > @@ -340,12 +341,17 @@ void queued_spin_lock_slowpath(struct qspinlock > > > *lock, u32

[for-next][PATCH 08/18] tracing: Add action comparisons when testing matching hist triggers

From: Tom Zanussi Actions also need to be considered when checking for matching triggers - triggers differing only by action should be allowed, but currently aren't because the matching check ignores the action and erroneously returns -EEXIST. Add and call an

[for-next][PATCH 08/18] tracing: Add action comparisons when testing matching hist triggers

From: Tom Zanussi Actions also need to be considered when checking for matching triggers - triggers differing only by action should be allowed, but currently aren't because the matching check ignores the action and erroneously returns -EEXIST. Add and call an actions_match() function to address

[for-next][PATCH 07/18] tracing: Dont add flag strings when displaying variable references

From: Tom Zanussi Variable references should never have flags appended when displayed - prevent that from happening. Before: # cat /sys/kernel/debug/tracing/events/sched/sched_switch/trigger

[for-next][PATCH 07/18] tracing: Dont add flag strings when displaying variable references

From: Tom Zanussi Variable references should never have flags appended when displayed - prevent that from happening. Before: # cat /sys/kernel/debug/tracing/events/sched/sched_switch/trigger hist:keys=next_pid:vals=hitcount:wakeup_lat=common_timestamp.usecs-$ts0.usecs:... After:

<    13   14   15   16   17   18   19   20   21   22   >