Re: [PATCH] mm/memory.c: Mark wp_huge_pmd() inline to prevent build failure

On Sun, Dec 3, 2017 at 10:11 PM, Geert Uytterhoeven wrote: > With gcc 4.1.2: > > mm/memory.o: In function `wp_huge_pmd': > memory.c:(.text+0x9b4): undefined reference to `do_huge_pmd_wp_page' > > Interestingly, wp_huge_pmd() is emitted in the assembler output, but >

Re: [PATCH] mm/memory.c: Mark wp_huge_pmd() inline to prevent build failure

On Sun, Dec 3, 2017 at 10:11 PM, Geert Uytterhoeven wrote: > With gcc 4.1.2: > > mm/memory.o: In function `wp_huge_pmd': > memory.c:(.text+0x9b4): undefined reference to `do_huge_pmd_wp_page' > > Interestingly, wp_huge_pmd() is emitted in the assembler output, but > never called. > >

Re: [PATCH 0/4] Move DP phy switch to PHY driver

Hi Chris, Am Montag, 4. Dezember 2017, 10:47:08 CET schrieb Chris Zhong: > On 2017年12月02日 05:58, Heiko Stuebner wrote: > > Am Freitag, 1. Dezember 2017, 13:42:46 CET schrieb Doug Anderson: > >> Hi, > >> > >> On Wed, Nov 29, 2017 at 6:27 PM, Chris Zhong wrote: > >>> Hi Doug

Re: [PATCH 0/4] Move DP phy switch to PHY driver

Hi Chris, Am Montag, 4. Dezember 2017, 10:47:08 CET schrieb Chris Zhong: > On 2017年12月02日 05:58, Heiko Stuebner wrote: > > Am Freitag, 1. Dezember 2017, 13:42:46 CET schrieb Doug Anderson: > >> Hi, > >> > >> On Wed, Nov 29, 2017 at 6:27 PM, Chris Zhong wrote: > >>> Hi Doug > >>> > >>> Thank

Re: [PATCH] sched/rt: Do not pull from current CPU if only one cpu to pull

Hi Steve, On 02/12/17 13:04, Steven Rostedt wrote: > Daniel Wagner reported a crash on the beaglebone black. This is a > single CPU architecture, and does not have a functional: > arch_send_call_function_single_ipi() and can crash if that is called. > > As it only has one CPU, it shouldn't be

Re: [PATCH] sched/rt: Do not pull from current CPU if only one cpu to pull

Hi Steve, On 02/12/17 13:04, Steven Rostedt wrote: > Daniel Wagner reported a crash on the beaglebone black. This is a > single CPU architecture, and does not have a functional: > arch_send_call_function_single_ipi() and can crash if that is called. > > As it only has one CPU, it shouldn't be

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

On Fri, Dec 01, 2017 at 03:03:30PM +0100, Linus Walleij wrote: > On Wed, Nov 8, 2017 at 4:52 AM, David Lechner wrote: > > > This adds a new driver for display panels based on the Ilitek ILI9225 > > controller. > > > > This was developed for a no-name panel with a red PCB

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

On Fri, Dec 01, 2017 at 03:03:30PM +0100, Linus Walleij wrote: > On Wed, Nov 8, 2017 at 4:52 AM, David Lechner wrote: > > > This adds a new driver for display panels based on the Ilitek ILI9225 > > controller. > > > > This was developed for a no-name panel with a red PCB that is commonly > >

Re: [PATCH] treewide: remove duplicate includes

On Mon, Dec 04, 2017 at 03:19:39AM +0530, Pravin Shedge wrote: > These duplicate includes have been found with scripts/checkincludes.pl but > they have been removed manually to avoid removing false positives. > > Unit Testing: > > - build successful > - LTP testsuite passes. > - checkpatch.pl

Re: [PATCH] treewide: remove duplicate includes

On Mon, Dec 04, 2017 at 03:19:39AM +0530, Pravin Shedge wrote: > These duplicate includes have been found with scripts/checkincludes.pl but > they have been removed manually to avoid removing false positives. > > Unit Testing: > > - build successful > - LTP testsuite passes. > - checkpatch.pl

Re: [GIT PULL] hash addresses printed with %p

On Mon, Dec 04, 2017 at 10:02:16AM +0800, Dave Young wrote: > +#define __ATTR_IRUSR(_name) { > \ > + .attr = { .name = __stringify(_name), .mode = S_IRUSR }, \ > + .show = _name##_show, \ > +}

Re: [GIT PULL] hash addresses printed with %p

On Mon, Dec 04, 2017 at 10:02:16AM +0800, Dave Young wrote: > +#define __ATTR_IRUSR(_name) { > \ > + .attr = { .name = __stringify(_name), .mode = S_IRUSR }, \ > + .show = _name##_show, \ > +}

Re: [PATCH 2/3] perf tools: Fix build for hardened environments

On Fri, Dec 01, 2017 at 11:11:37AM +0900, Namhyung Kim wrote: > Hi Jiri, > > On Wed, Nov 08, 2017 at 11:27:38AM +0100, Jiri Olsa wrote: > > From: Jiri Olsa > > > > On Fedora systems the perl and python CFLAGS/LDFLAGS include the > > hardened specs from redhat-rpm-config

Re: [PATCH 2/3] perf tools: Fix build for hardened environments

On Fri, Dec 01, 2017 at 11:11:37AM +0900, Namhyung Kim wrote: > Hi Jiri, > > On Wed, Nov 08, 2017 at 11:27:38AM +0100, Jiri Olsa wrote: > > From: Jiri Olsa > > > > On Fedora systems the perl and python CFLAGS/LDFLAGS include the > > hardened specs from redhat-rpm-config package. We apply them

Re: [PATCH] Make FSI a menuconfig to ease disabling it all

On Mon, Dec 04, 2017 at 02:56:32PM +0800, Jeremy Kerr wrote: > Hi Vincent, > > > No need to get into the submenu to disable all FSI-related config entries > > Sounds reasonable to me. > > Acked-by: Jeremy Kerr > > Greg: do you want Joel (or me) to manage FSI patches, or would

Re: [PATCH] Make FSI a menuconfig to ease disabling it all

On Mon, Dec 04, 2017 at 02:56:32PM +0800, Jeremy Kerr wrote: > Hi Vincent, > > > No need to get into the submenu to disable all FSI-related config entries > > Sounds reasonable to me. > > Acked-by: Jeremy Kerr > > Greg: do you want Joel (or me) to manage FSI patches, or would you > prefer to

Re: [PATCH 1/3] vhost: fix skb leak in handle_rx()

On 2017年12月01日 22:37, Michael S. Tsirkin wrote: On Fri, Dec 01, 2017 at 03:11:05PM +0800, Jason Wang wrote: On 2017年12月01日 13:54, w...@redhat.com wrote: From: Wei Xu Matthew found a roughly 40% tcp throughput regression with commit c67df11f(vhost_net: try batch dequing

Re: [PATCH 1/3] vhost: fix skb leak in handle_rx()

On 2017年12月01日 22:37, Michael S. Tsirkin wrote: On Fri, Dec 01, 2017 at 03:11:05PM +0800, Jason Wang wrote: On 2017年12月01日 13:54, 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

[RESEND PATCH v3 3/3] dt-bindings: Add INNOLUX P097PFG panel bindings

The Innolux P097PFG panel is 9.7" panel with 1536X2048 resolution, it reuse P079ZCA panel driver, so improve p079ZCA dt-binding to support P097PFG. Signed-off-by: Lin Huang --- .../devicetree/bindings/display/panel/innolux,p079zca.txt | 11 +-- 1 file changed, 9

[RESEND PATCH v3 3/3] dt-bindings: Add INNOLUX P097PFG panel bindings

The Innolux P097PFG panel is 9.7" panel with 1536X2048 resolution, it reuse P079ZCA panel driver, so improve p079ZCA dt-binding to support P097PFG. Signed-off-by: Lin Huang --- .../devicetree/bindings/display/panel/innolux,p079zca.txt | 11 +-- 1 file changed, 9 insertions(+), 2

[RESEND PATCH v3 1/3] drm/panel: refactor INNOLUX P079ZCA panel driver

Refactor Innolux P079ZCA panel driver, let it support multi panel. Signed-off-by: Lin Huang --- Changes in v2: - Change regulator property name to meet the panel datasheet Changes in v3: - this patch only refactor P079ZCA panel to support multi panel, support P097PFG panel

[RESEND PATCH v3 2/3] drm/panel: support Innolux P097PFG panel

Support Innolux P097PFG 9.7" 1536x2048 TFT LCD panel, it reuse the Innolux P079ZCA panel driver. Signed-off-by: Lin Huang --- drivers/gpu/drm/panel/Kconfig | 9 drivers/gpu/drm/panel/panel-innolux-p079zca.c | 31 +++ 2 files

[RESEND PATCH v3 1/3] drm/panel: refactor INNOLUX P079ZCA panel driver

Refactor Innolux P079ZCA panel driver, let it support multi panel. Signed-off-by: Lin Huang --- Changes in v2: - Change regulator property name to meet the panel datasheet Changes in v3: - this patch only refactor P079ZCA panel to support multi panel, support P097PFG panel in another patch

[RESEND PATCH v3 2/3] drm/panel: support Innolux P097PFG panel

Support Innolux P097PFG 9.7" 1536x2048 TFT LCD panel, it reuse the Innolux P079ZCA panel driver. Signed-off-by: Lin Huang --- drivers/gpu/drm/panel/Kconfig | 9 drivers/gpu/drm/panel/panel-innolux-p079zca.c | 31 +++ 2 files changed, 35

[PATCH v3 2/3] drm/panel: support Innolux P097PFG panel

Support Innolux P097PFG 9.7" 1536x2048 TFT LCD panel, it reuse the Innolux P079ZCA panel driver. Signed-off-by: Lin Huang --- drivers/gpu/drm/panel/Kconfig | 9 drivers/gpu/drm/panel/panel-innolux-p079zca.c | 31 +++ 2 files

[PATCH v3 3/3] dt-bindings: Add INNOLUX P097PFG panel bindings

The Innolux P097PFG panel is 9.7" panel with 1536X2048 resolution, it reuse P079ZCA panel driver, so improve p079ZCA dt-binding to support P097PFG. Change-Id: I8704914898fe53b734d31fbe646df8aa5fd8b30d Signed-off-by: Lin Huang ---

[PATCH v3 1/3] drm/panel: refactor INNOLUX P079ZCA panel driver

Refactor Innolux P079ZCA panel driver, let it support multi panel. Signed-off-by: Lin Huang --- Changes in v2: - Change regulator property name to meet the panel datasheet Changes in v3: - this patch only refactor P079ZCA panel to support multi panel, support P097PFG panel

[PATCH v3 2/3] drm/panel: support Innolux P097PFG panel

Support Innolux P097PFG 9.7" 1536x2048 TFT LCD panel, it reuse the Innolux P079ZCA panel driver. Signed-off-by: Lin Huang --- drivers/gpu/drm/panel/Kconfig | 9 drivers/gpu/drm/panel/panel-innolux-p079zca.c | 31 +++ 2 files changed, 35

[PATCH v3 3/3] dt-bindings: Add INNOLUX P097PFG panel bindings

The Innolux P097PFG panel is 9.7" panel with 1536X2048 resolution, it reuse P079ZCA panel driver, so improve p079ZCA dt-binding to support P097PFG. Change-Id: I8704914898fe53b734d31fbe646df8aa5fd8b30d Signed-off-by: Lin Huang --- .../devicetree/bindings/display/panel/innolux,p079zca.txt |

[PATCH v3 1/3] drm/panel: refactor INNOLUX P079ZCA panel driver

Refactor Innolux P079ZCA panel driver, let it support multi panel. Signed-off-by: Lin Huang --- Changes in v2: - Change regulator property name to meet the panel datasheet Changes in v3: - this patch only refactor P079ZCA panel to support multi panel, support P097PFG panel in another patch

Re: [PATCH net] virtio_net: fix return value check in receive_mergeable()

On 2017年12月04日 14:02, wangyunjian wrote: From: Yunjian Wang The function virtqueue_get_buf_ctx() could return NULL, the return value 'buf' need to be checked with NULL, not value 'ctx'. Signed-off-by: Yunjian Wang ---

Re: [PATCH net] virtio_net: fix return value check in receive_mergeable()

On 2017年12月04日 14:02, wangyunjian wrote: From: Yunjian Wang The function virtqueue_get_buf_ctx() could return NULL, the return value 'buf' need to be checked with NULL, not value 'ctx'. Signed-off-by: Yunjian Wang --- drivers/net/virtio_net.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH v6 2/2] media: i2c: Add the ov7740 image sensor driver

The ov7740 (color) image sensor is a high performance VGA CMOS image snesor, which supports for output formats: RAW RGB and YUV and image sizes: VGA, and QVGA, CIF and any size smaller. Signed-off-by: Songjun Wu Signed-off-by: Wenyou Yang ---

[PATCH v6 2/2] media: i2c: Add the ov7740 image sensor driver

The ov7740 (color) image sensor is a high performance VGA CMOS image snesor, which supports for output formats: RAW RGB and YUV and image sizes: VGA, and QVGA, CIF and any size smaller. Signed-off-by: Songjun Wu Signed-off-by: Wenyou Yang --- Changes in v6: - Remove unnecessary #include . -

[PATCH v6 1/2] media: ov7740: Document device tree bindings

Add the device tree binding documentation for the ov7740 sensor driver. Signed-off-by: Wenyou Yang --- Changes in v6: None Changes in v5: None Changes in v4: None Changes in v3: - Explicitly document the "remote-endpoint" property. Changes in v2: None

[PATCH v6 1/2] media: ov7740: Document device tree bindings

Add the device tree binding documentation for the ov7740 sensor driver. Signed-off-by: Wenyou Yang --- Changes in v6: None Changes in v5: None Changes in v4: None Changes in v3: - Explicitly document the "remote-endpoint" property. Changes in v2: None

[PATCH v6 0/2] media: ov7740: Add a V4L2 sensor-level driver

Add a Video4Linux2 sensor-level driver for the OmniVision OV7740 VGA camera image sensor. Changes in v6: - Remove unnecessary #include . - Remove unnecessary comments and extra newline. - Add const for some structures. - Add the check of the return value from regmap_write(). - Simplify the

[PATCH v6 0/2] media: ov7740: Add a V4L2 sensor-level driver

Add a Video4Linux2 sensor-level driver for the OmniVision OV7740 VGA camera image sensor. Changes in v6: - Remove unnecessary #include . - Remove unnecessary comments and extra newline. - Add const for some structures. - Add the check of the return value from regmap_write(). - Simplify the

Re: [PATCH v5 2/2] media: i2c: Add the ov7740 image sensor driver

Hi Sakari, Sorry for late answer. Thank you for your review. On 2017/11/28 20:06, Sakari Ailus wrote: Hi Wenyou, Thanks for the patch. Some comments below. On Tue, Nov 28, 2017 at 01:22:59PM +0800, Wenyou Yang wrote: The ov7740 (color) image sensor is a high performance VGA CMOS image

Re: [PATCH v5 2/2] media: i2c: Add the ov7740 image sensor driver

Hi Sakari, Sorry for late answer. Thank you for your review. On 2017/11/28 20:06, Sakari Ailus wrote: Hi Wenyou, Thanks for the patch. Some comments below. On Tue, Nov 28, 2017 at 01:22:59PM +0800, Wenyou Yang wrote: The ov7740 (color) image sensor is a high performance VGA CMOS image

Re: [PATCH] Make FSI a menuconfig to ease disabling it all

Hi Vincent, > No need to get into the submenu to disable all FSI-related config entries Sounds reasonable to me. Acked-by: Jeremy Kerr Greg: do you want Joel (or me) to manage FSI patches, or would you prefer to take this directly? Cheers, Jeremy

Re: [PATCH] Make FSI a menuconfig to ease disabling it all

Hi Vincent, > No need to get into the submenu to disable all FSI-related config entries Sounds reasonable to me. Acked-by: Jeremy Kerr Greg: do you want Joel (or me) to manage FSI patches, or would you prefer to take this directly? Cheers, Jeremy

Re: [PATCH 1/3] dt-bindings: Add optional nvmem MAC address bindings to ti,wlink-st

Hi David, > This adds optional nvmem consumer properties to the ti,wlink-st device tree > bindings to allow specifying the Bluetooth MAC address. > > Signed-off-by: David Lechner > --- > Documentation/devicetree/bindings/net/ti,wilink-st.txt | 4 > 1 file changed, 4

Re: [PATCH 1/3] dt-bindings: Add optional nvmem MAC address bindings to ti,wlink-st

Hi David, > This adds optional nvmem consumer properties to the ti,wlink-st device tree > bindings to allow specifying the Bluetooth MAC address. > > Signed-off-by: David Lechner > --- > Documentation/devicetree/bindings/net/ti,wilink-st.txt | 4 > 1 file changed, 4 insertions(+) > > diff

Re: [PATCH 3/3] bluetooth: hci_ll: Add optional nvmem MAC address source

Hi David, > This adds an optional nvmem consumer to get a MAC address from an external > source. The MAC address is then set in the Bluetooth chip after the > firmware has been loaded. > > This has been tested working with a TI CC2560A chip (in a LEGO MINDSTORMS > EV3). > > Signed-off-by: David

Re: [PATCH 3/3] bluetooth: hci_ll: Add optional nvmem MAC address source

Hi David, > This adds an optional nvmem consumer to get a MAC address from an external > source. The MAC address is then set in the Bluetooth chip after the > firmware has been loaded. > > This has been tested working with a TI CC2560A chip (in a LEGO MINDSTORMS > EV3). > > Signed-off-by: David

[RFC v2 0/2] Xilinx ZynqMP IPI Mailbox Controller Driver

Introduce mailbox controller driver for ZynqMP IPI(Inter-processor interrupt) IP core. There is previous discussion on the DT bindings: https://patchwork.kernel.org/patch/10012755/ v2: - change SPDX-License-Identifier license text style in .c file - replace xlnx-ipi-ids with xlnx,ipi-ids

[RFC v2 0/2] Xilinx ZynqMP IPI Mailbox Controller Driver

Introduce mailbox controller driver for ZynqMP IPI(Inter-processor interrupt) IP core. There is previous discussion on the DT bindings: https://patchwork.kernel.org/patch/10012755/ v2: - change SPDX-License-Identifier license text style in .c file - replace xlnx-ipi-ids with xlnx,ipi-ids

[RFC v2 2/2] dt-bindings: mailbox: Add Xilinx IPI Mailbox

Xilinx ZynqMP IPI(Inter Processor Interrupt) is a hardware block in ZynqMP SoC used for the communication between various processor systems. Signed-off-by: Wendy Liang --- .../bindings/mailbox/xlnx,zynqmp-ipi-mailbox.txt | 104 + 1 file changed, 104

[RFC v2 1/2] mailbox: ZynqMP IPI mailbox controller

This patch is to introduce ZynqMP IPI mailbox controller driver to use the ZynqMP IPI block as mailboxes. Signed-off-by: Wendy Liang --- drivers/mailbox/Kconfig| 8 + drivers/mailbox/Makefile | 2 +

[RFC v2 2/2] dt-bindings: mailbox: Add Xilinx IPI Mailbox

Xilinx ZynqMP IPI(Inter Processor Interrupt) is a hardware block in ZynqMP SoC used for the communication between various processor systems. Signed-off-by: Wendy Liang --- .../bindings/mailbox/xlnx,zynqmp-ipi-mailbox.txt | 104 + 1 file changed, 104 insertions(+) create

[RFC v2 1/2] mailbox: ZynqMP IPI mailbox controller

This patch is to introduce ZynqMP IPI mailbox controller driver to use the ZynqMP IPI block as mailboxes. Signed-off-by: Wendy Liang --- drivers/mailbox/Kconfig| 8 + drivers/mailbox/Makefile | 2 + drivers/mailbox/zynqmp-ipi-mailbox.c | 633

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

Am 04.12.2017 um 01:02 schrieb Stephen Rothwell: > Hi all, > > After merging the net-next tree, today's linux-next build (arm > multi_v7_defconfig) produced this warning: > > drivers/net/phy/broadcom.c:391:12: warning: 'bcm5482_read_status' defined but > not used [-Wunused-function] > static

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

Am 04.12.2017 um 01:02 schrieb Stephen Rothwell: > Hi all, > > After merging the net-next tree, today's linux-next build (arm > multi_v7_defconfig) produced this warning: > > drivers/net/phy/broadcom.c:391:12: warning: 'bcm5482_read_status' defined but > not used [-Wunused-function] > static

Re: [PATCH 2/3] bluetooth: hci_ll: add constant for vendor-specific command

Hi David, > This adds a #define for the vendor-specific HCI command to set the > baudrate instead of using the bare 0xff36 multiple times. > > Signed-off-by: David Lechner > --- > drivers/bluetooth/hci_ll.c | 10 -- > 1 file changed, 8 insertions(+), 2 deletions(-)

Re: [PATCH 2/3] bluetooth: hci_ll: add constant for vendor-specific command

Hi David, > This adds a #define for the vendor-specific HCI command to set the > baudrate instead of using the bare 0xff36 multiple times. > > Signed-off-by: David Lechner > --- > drivers/bluetooth/hci_ll.c | 10 -- > 1 file changed, 8 insertions(+), 2 deletions(-) patch has been

Re: [PATCH 0/4] Fix use after free in HPT resizing code and related minor improvements

On Wed, Nov 29, 2017 at 11:38:22AM -0500, Serhii Popovych wrote: > It is possible to trigger use after free during HPT resize > causing host kernel to crash. More details and analysis of > the problem can be found in change with corresponding subject > (KVM: PPC: Book3S HV: Fix use after free in

Re: [PATCH 0/4] Fix use after free in HPT resizing code and related minor improvements

On Wed, Nov 29, 2017 at 11:38:22AM -0500, Serhii Popovych wrote: > It is possible to trigger use after free during HPT resize > causing host kernel to crash. More details and analysis of > the problem can be found in change with corresponding subject > (KVM: PPC: Book3S HV: Fix use after free in

Re: [PATCH v2 00/15] NTB: Add full multi-port API support to the test drivers

On Sun, Dec 03, 2017 at 09:54:58PM -0700, Logan Gunthorpe wrote: > > > On 03/12/17 12:17 PM, Serge Semin wrote: > > The multi-port NTB API was introduced in kernel 4.13 as well as the > > first driver for the true multi-port devices of IDT PCIe-switches > > series. But the

Re: [PATCH v2 00/15] NTB: Add full multi-port API support to the test drivers

On Sun, Dec 03, 2017 at 09:54:58PM -0700, Logan Gunthorpe wrote: > > > On 03/12/17 12:17 PM, Serge Semin wrote: > > The multi-port NTB API was introduced in kernel 4.13 as well as the > > first driver for the true multi-port devices of IDT PCIe-switches > > series. But the test drivers still

[PATCH net] virtio_net: fix return value check in receive_mergeable()

From: Yunjian Wang The function virtqueue_get_buf_ctx() could return NULL, the return value 'buf' need to be checked with NULL, not value 'ctx'. Signed-off-by: Yunjian Wang --- drivers/net/virtio_net.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH net] virtio_net: fix return value check in receive_mergeable()

From: Yunjian Wang The function virtqueue_get_buf_ctx() could return NULL, the return value 'buf' need to be checked with NULL, not value 'ctx'. Signed-off-by: Yunjian Wang --- drivers/net/virtio_net.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 3/3] ARM64: dts: meson-axg: add PWM DT info for Meson-Axg SoC

From: Jian Hu Add PWM DT info for the Amlogic's Meson-Axg SoC. Signed-off-by: Jian Hu Signed-off-by: Yixun Lan --- arch/arm64/boot/dts/amlogic/meson-axg.dtsi | 120 + 1 file changed, 120

[PATCH 2/3] pwm: meson: add clock source configuratin for Meson-AXG

From: Jian Hu For PWM controller in the Meson-AXG SoC, the EE domain and AO domain have different clock source. This patch try to describe them in the DT compatible data. Signed-off-by: Jian Hu Signed-off-by: Yixun Lan ---

[PATCH 3/3] ARM64: dts: meson-axg: add PWM DT info for Meson-Axg SoC

From: Jian Hu Add PWM DT info for the Amlogic's Meson-Axg SoC. Signed-off-by: Jian Hu Signed-off-by: Yixun Lan --- arch/arm64/boot/dts/amlogic/meson-axg.dtsi | 120 + 1 file changed, 120 insertions(+) diff --git a/arch/arm64/boot/dts/amlogic/meson-axg.dtsi

[PATCH 2/3] pwm: meson: add clock source configuratin for Meson-AXG

From: Jian Hu For PWM controller in the Meson-AXG SoC, the EE domain and AO domain have different clock source. This patch try to describe them in the DT compatible data. Signed-off-by: Jian Hu Signed-off-by: Yixun Lan --- drivers/pwm/pwm-meson.c | 26 ++ 1 file

[PATCH 1/3] dt-bindings: pwm: update bindings for the Meson-AXG

From: Jian Hu Update the doc to explicitly support Meson-AXG Signed-off-by: Jian Hu Signed-off-by: Yixun Lan --- Documentation/devicetree/bindings/pwm/pwm-meson.txt | 2 ++ 1 file changed, 2 insertions(+) diff --git

[PATCH 1/3] dt-bindings: pwm: update bindings for the Meson-AXG

From: Jian Hu Update the doc to explicitly support Meson-AXG Signed-off-by: Jian Hu Signed-off-by: Yixun Lan --- Documentation/devicetree/bindings/pwm/pwm-meson.txt | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Documentation/devicetree/bindings/pwm/pwm-meson.txt

[PATCH 0/3] pwm: meson-axg: add pwm controller driver

This patch series try to add PWM controller driver for the Amlogic's Meson-AXG SoC. Update the Clock sources, pin DT. Jian Hu (3): dt-bindings: pwm: update bindings for the Meson-AXG pwm: meson: add clock source configuratin for Meson-AXG ARM64: dts: meson-axg: add PWM DT info for

[PATCH 0/3] pwm: meson-axg: add pwm controller driver

This patch series try to add PWM controller driver for the Amlogic's Meson-AXG SoC. Update the Clock sources, pin DT. Jian Hu (3): dt-bindings: pwm: update bindings for the Meson-AXG pwm: meson: add clock source configuratin for Meson-AXG ARM64: dts: meson-axg: add PWM DT info for

Re: [PATCH] riscv/ftrace: Add basic support

On Thu, Nov 30, 2017 at 03:24:21PM -0500, Steven Rostedt wrote: > On Thu, 30 Nov 2017 16:53:35 +0800 > Alan Kao wrote: > > > This patch contains basic ftrace support for RV64I platform. > > Specifically, function tracer (HAVE_FUNCTION_TRACER), function graph > > tracer

Re: [PATCH] riscv/ftrace: Add basic support

On Thu, Nov 30, 2017 at 03:24:21PM -0500, Steven Rostedt wrote: > On Thu, 30 Nov 2017 16:53:35 +0800 > Alan Kao wrote: > > > This patch contains basic ftrace support for RV64I platform. > > Specifically, function tracer (HAVE_FUNCTION_TRACER), function graph > > tracer

[PATCH] mtd: nand: squash struct nand_buffers into struct nand_chip

struct nand_buffers is malloc'ed in nand_scan_tail() just for containing three pointers. Move the pointers into nand_chip and delete struct nand_buffers. Signed-off-by: Masahiro Yamada --- Another possibility is to keep struct nand_buffers, but embed it in struct

[PATCH] mtd: nand: squash struct nand_buffers into struct nand_chip

struct nand_buffers is malloc'ed in nand_scan_tail() just for containing three pointers. Move the pointers into nand_chip and delete struct nand_buffers. Signed-off-by: Masahiro Yamada --- Another possibility is to keep struct nand_buffers, but embed it in struct nand_chip. struct

Re: [PATCH v2 0/8] perf tools: perf tools: Clarify overwrite and backward, bugfix

On Sun, Dec 03, 2017 at 02:00:36AM +, Wang Nan wrote: > THe final result of this patchset is removing the concept of > 'forward/backward', merge them into the concept of 'overwrite'. > > Patch 1 to 5 clear arguments lists of many functions, remove the > 'overwrite'. Because all callers of

Re: [PATCH v2 0/8] perf tools: perf tools: Clarify overwrite and backward, bugfix

On Sun, Dec 03, 2017 at 02:00:36AM +, Wang Nan wrote: > THe final result of this patchset is removing the concept of > 'forward/backward', merge them into the concept of 'overwrite'. > > Patch 1 to 5 clear arguments lists of many functions, remove the > 'overwrite'. Because all callers of

[PATCH v2] ARM64: dts: meson-axg: enable IR controller

Enable IR remote controller which find in Amlogic's Meson-AXG SoC. Signed-off-by: Yixun Lan --- Changes since v1 at [1]: - drop the compatbile 'amlogic,meson-gx-ir' [1] http://lists.infradead.org/pipermail/linux-amlogic/2017-November/005527.html ---

[PATCH v2] ARM64: dts: meson-axg: enable IR controller

Enable IR remote controller which find in Amlogic's Meson-AXG SoC. Signed-off-by: Yixun Lan --- Changes since v1 at [1]: - drop the compatbile 'amlogic,meson-gx-ir' [1] http://lists.infradead.org/pipermail/linux-amlogic/2017-November/005527.html ---

Re: [PATCH v2 6/8] perf mmap: Fix perf backward recording

Hi, On Sun, Dec 03, 2017 at 02:00:42AM +, Wang Nan wrote: > perf record backward recording doesn't work as we expected: it never > overwrite when ring buffer full. > > Test: > > (Run a busy printing task background like this: > > while True: > print 123 > > send SIGUSR2 to perf to

Re: [PATCH v2 6/8] perf mmap: Fix perf backward recording

Hi, On Sun, Dec 03, 2017 at 02:00:42AM +, Wang Nan wrote: > perf record backward recording doesn't work as we expected: it never > overwrite when ring buffer full. > > Test: > > (Run a busy printing task background like this: > > while True: > print 123 > > send SIGUSR2 to perf to

Re: [PATCH v18 10/10] virtio-balloon: don't report free pages when page poisoning is enabled

On 12/01/2017 11:49 PM, Michael S. Tsirkin wrote: On Wed, Nov 29, 2017 at 09:55:26PM +0800, Wei Wang wrote: The guest free pages should not be discarded by the live migration thread when page poisoning is enabled with PAGE_POISONING_NO_SANITY=n, because skipping the transfer of such poisoned

Re: [PATCH v18 10/10] virtio-balloon: don't report free pages when page poisoning is enabled

On 12/01/2017 11:49 PM, Michael S. Tsirkin wrote: On Wed, Nov 29, 2017 at 09:55:26PM +0800, Wei Wang wrote: The guest free pages should not be discarded by the live migration thread when page poisoning is enabled with PAGE_POISONING_NO_SANITY=n, because skipping the transfer of such poisoned

[PATCH] clk: meson: make the spinlock naming more specific

Make the spinlock more specific, so better for lockdep debugging and ctags/grep. Signed-off-by: Yixun Lan --- this patch try to address the issue which bring up by Stephen at [1] [1] http://lists.infradead.org/pipermail/linux-amlogic/2017-December/005534.html ---

[PATCH] Revert "powerpc: Do not call ppc_md.panic in fadump panic notifier"

This reverts commit a3b2cb30f252b21a6f962e0dd107c8b897ca65e4. The earlier patch tried to fix problems with panic on powerpc in certain circumstances, where some output from the generic panic code was being dropped. Unfortunately, it breaks things worse in other circumstances. In particular when

[PATCH] clk: meson: make the spinlock naming more specific

Make the spinlock more specific, so better for lockdep debugging and ctags/grep. Signed-off-by: Yixun Lan --- this patch try to address the issue which bring up by Stephen at [1] [1] http://lists.infradead.org/pipermail/linux-amlogic/2017-December/005534.html --- drivers/clk/meson/axg.c |

[PATCH] Revert "powerpc: Do not call ppc_md.panic in fadump panic notifier"

This reverts commit a3b2cb30f252b21a6f962e0dd107c8b897ca65e4. The earlier patch tried to fix problems with panic on powerpc in certain circumstances, where some output from the generic panic code was being dropped. Unfortunately, it breaks things worse in other circumstances. In particular when

[PATCH 1/2] clk: sunxi-ng: Support fixed post-dividers on MP style clocks

On the A64, the MMC module clocks are fixed in the new timing mode, i.e. they do not have a bit to select the mode. These clocks have a 2x divider somewhere between the clock and the MMC module. To be consistent with other SoCs supporting the new timing mode, we model the 2x divider as a fixed

[PATCH 0/2] clk: sunxi-ng: sun50i: a64: Add 2x fixed post-divider to MMC module clocks

Hi, This is a small fix to get MMC performance up to proper speeds on the A64. According to the BSP kernel, the MMC module clocks have a /2 fixed post-divider between the clock output and the MMC module, like what we've seen with the "new MMC timing mode" on the A83T, but the A64 does not have

[PATCH 1/2] clk: sunxi-ng: Support fixed post-dividers on MP style clocks

On the A64, the MMC module clocks are fixed in the new timing mode, i.e. they do not have a bit to select the mode. These clocks have a 2x divider somewhere between the clock and the MMC module. To be consistent with other SoCs supporting the new timing mode, we model the 2x divider as a fixed

[PATCH 0/2] clk: sunxi-ng: sun50i: a64: Add 2x fixed post-divider to MMC module clocks

Hi, This is a small fix to get MMC performance up to proper speeds on the A64. According to the BSP kernel, the MMC module clocks have a /2 fixed post-divider between the clock output and the MMC module, like what we've seen with the "new MMC timing mode" on the A83T, but the A64 does not have

[PATCH 2/2] clk: sunxi-ng: sun50i: a64: Add 2x fixed post-divider to MMC module clocks

On the A64, the MMC module clocks are fixed in the new timing mode, i.e. they do not have a bit to select the mode. These clocks have a 2x divider somewhere between the clock and the MMC module. To be consistent with other SoCs supporting the new timing mode, we model the 2x divider as a fixed

[PATCH 2/2] clk: sunxi-ng: sun50i: a64: Add 2x fixed post-divider to MMC module clocks

On the A64, the MMC module clocks are fixed in the new timing mode, i.e. they do not have a bit to select the mode. These clocks have a 2x divider somewhere between the clock and the MMC module. To be consistent with other SoCs supporting the new timing mode, we model the 2x divider as a fixed

Re: [PATCH] leaking_addresses: add support for 32-bit kernel addresses

> On Mon, Dec 4, 2017 at 10:25 AM, Tobin C. Harding wrote: >> >> > With the 'eval', no warning, it's fine. >> >> Why not use hex()? > >> > >> > foreach my $config_file (@config_files) { >> > + $config_file =~ s/\R*//g; >> >> Is there some reason you don't use

Re: [PATCH] leaking_addresses: add support for 32-bit kernel addresses

> On Mon, Dec 4, 2017 at 10:25 AM, Tobin C. Harding wrote: >> >> > With the 'eval', no warning, it's fine. >> >> Why not use hex()? > >> > >> > foreach my $config_file (@config_files) { >> > + $config_file =~ s/\R*//g; >> >> Is there some reason you don't use chomp()? > Wrt

Re: [Bridge] [PATCH net-next] bridge: ebtables: Avoid resetting limit rule state

On Mon, Dec 04, 2017 at 05:53:35AM +0100, Linus Lüssing wrote: > And so, no I do not have this patch. I looked at it now, but it > does not seem to have any relation with .matchinfo, does it? Relation between .usersize and .checkentry I ment, not .usersize and .matchinfo.

Re: [Bridge] [PATCH net-next] bridge: ebtables: Avoid resetting limit rule state

On Mon, Dec 04, 2017 at 05:53:35AM +0100, Linus Lüssing wrote: > And so, no I do not have this patch. I looked at it now, but it > does not seem to have any relation with .matchinfo, does it? Relation between .usersize and .checkentry I ment, not .usersize and .matchinfo.

[PATCH v2 1/4] lockdep: Apply crossrelease to PG_locked locks

Although lock_page() and its family can cause deadlock, lockdep have not worked with them, becasue unlock_page() might be called in a different context from the acquire context, which violated lockdep's assumption. Now CONFIG_LOCKDEP_CROSSRELEASE has been introduced, lockdep can work with page

[PATCH v2 1/4] lockdep: Apply crossrelease to PG_locked locks

Although lock_page() and its family can cause deadlock, lockdep have not worked with them, becasue unlock_page() might be called in a different context from the acquire context, which violated lockdep's assumption. Now CONFIG_LOCKDEP_CROSSRELEASE has been introduced, lockdep can work with page

[PATCH v2 4/4] lockdep: Add a boot parameter enabling to track page locks using lockdep and disable it by default

To track page locks using lockdep, we need a huge memory space for lockdep_map per page. So, it would be better to make it disabled by default and provide a boot parameter to turn it on. Do it. Suggested-by: Michal Hocko Signed-off-by: Byungchul Park

[PATCH v2 4/4] lockdep: Add a boot parameter enabling to track page locks using lockdep and disable it by default

To track page locks using lockdep, we need a huge memory space for lockdep_map per page. So, it would be better to make it disabled by default and provide a boot parameter to turn it on. Do it. Suggested-by: Michal Hocko Signed-off-by: Byungchul Park ---

  1   2   3   4   5   6   7   >