Re: [PATCHv14 2/3] usb: USB Type-C connector class

On Tue, Jan 10, 2017 at 11:08:51AM +0100, Oliver Neukum wrote: > > And since we are talking about the ABI, can we also change the listing > > of the accessory mode back to just "audio" and "debug" like I > > originally had it? I don't remember who and why wanted it to be > > changed to "Audio

Re: [PATCHv14 2/3] usb: USB Type-C connector class

On Tue, Jan 10, 2017 at 11:08:51AM +0100, Oliver Neukum wrote: > > And since we are talking about the ABI, can we also change the listing > > of the accessory mode back to just "audio" and "debug" like I > > originally had it? I don't remember who and why wanted it to be > > changed to "Audio

[PATCH v8 0/2] securityfs support for TPM 2.0 firmware event log

The TPM device driver defines ascii and binary methods for displaying the TPM 1.2 event log via securityfs files, which are needed for validating a TPM quote. The device driver for TPM 2.0 does not have similar support for displaying the TPM 2.0 event log. This patch set adds the support for

[PATCH v8 2/2] tpm: add securityfs support for TPM 2.0 firmware event log

Unlike the device driver support for TPM 1.2, the TPM 2.0 does not support the securityfs pseudo files for displaying the firmware event log. This patch enables support for providing the TPM 2.0 event log in binary form. TPM 2.0 event log supports a crypto agile format that records multiple

[PATCH v8 0/2] securityfs support for TPM 2.0 firmware event log

The TPM device driver defines ascii and binary methods for displaying the TPM 1.2 event log via securityfs files, which are needed for validating a TPM quote. The device driver for TPM 2.0 does not have similar support for displaying the TPM 2.0 event log. This patch set adds the support for

[PATCH v8 2/2] tpm: add securityfs support for TPM 2.0 firmware event log

Unlike the device driver support for TPM 1.2, the TPM 2.0 does not support the securityfs pseudo files for displaying the firmware event log. This patch enables support for providing the TPM 2.0 event log in binary form. TPM 2.0 event log supports a crypto agile format that records multiple

[PATCH v8 1/2] tpm: enhance read_log_of() to support Physical TPM event log

Physical TPMs use Open Firmware Device Tree bindings that are similar to the IBM Power virtual TPM to support event log. However, these properties store the values in different endianness for Physical and Virtual TPM. This patch fixes the endianness issue by doing appropriate conversion based on

[PATCH v8 1/2] tpm: enhance read_log_of() to support Physical TPM event log

Physical TPMs use Open Firmware Device Tree bindings that are similar to the IBM Power virtual TPM to support event log. However, these properties store the values in different endianness for Physical and Virtual TPM. This patch fixes the endianness issue by doing appropriate conversion based on

Re: [PATCH v3 5/7] mtd: nand: raw: create struct rawnand_device

On Tue, 10 Jan 2017 20:09:15 +0100 Marek Vasut wrote: > On 11/21/2016 01:45 PM, Boris Brezillon wrote: > > Create the rawnand_device struct inheriting from nand_device and make > > nand_chip inherit from this struct. > > > > The rawnand_device object should be used for

Re: [PATCH v3 5/7] mtd: nand: raw: create struct rawnand_device

On Tue, 10 Jan 2017 20:09:15 +0100 Marek Vasut wrote: > On 11/21/2016 01:45 PM, Boris Brezillon wrote: > > Create the rawnand_device struct inheriting from nand_device and make > > nand_chip inherit from this struct. > > > > The rawnand_device object should be used for the new > >

Re: [PATCH v8 3/3] arm64: dts: exynos: Add support for S6E3HA2 panel device on TM2 board

On 11.01.2017 07:33, Hoegeun Kwon wrote: > From: Hyungwon Hwang > > This patch add the panel device tree node for S6E3HA2 display > controller to TM2 dts. > > Signed-off-by: Hyungwon Hwang > Signed-off-by: Andrzej Hajda >

Re: [PATCH v8 3/3] arm64: dts: exynos: Add support for S6E3HA2 panel device on TM2 board

On 11.01.2017 07:33, Hoegeun Kwon wrote: > From: Hyungwon Hwang > > This patch add the panel device tree node for S6E3HA2 display > controller to TM2 dts. > > Signed-off-by: Hyungwon Hwang > Signed-off-by: Andrzej Hajda > Signed-off-by: Chanwoo Choi > Signed-off-by: Hoegeun Kwon > Tested-by:

Re: [PATCH v3 4/7] mtd: nand: raw: prefix conflicting names with nandc instead of nand

On Tue, 10 Jan 2017 20:08:23 +0100 Marek Vasut wrote: > On 11/21/2016 01:45 PM, Boris Brezillon wrote: > > Some raw NAND function names conflict with names defined in nand.h. > > Prefix all those functions with nandc (for nand chip) instead of nand so > > we can include

Re: [PATCH v3 4/7] mtd: nand: raw: prefix conflicting names with nandc instead of nand

On Tue, 10 Jan 2017 20:08:23 +0100 Marek Vasut wrote: > On 11/21/2016 01:45 PM, Boris Brezillon wrote: > > Some raw NAND function names conflict with names defined in nand.h. > > Prefix all those functions with nandc (for nand chip) instead of nand so > > we can include nand.h from rawnand.h > >

Re: [Intel-gfx] 4.10-rc2 oops in DRM connector code

On Tue, Jan 10, 2017 at 08:52:47AM -0800, Dave Hansen wrote: > On 01/10/2017 02:31 AM, Daniel Vetter wrote: > > commit e73ab00e9a0f1731f34d0620a9c55f5c30c4ad4e > > Author: Daniel Vetter > > Date: Sun Dec 18 14:35:45 2016 +0100 > > > > drm: prevent

Re: [PATCH v8 1/3] dt-bindings: Add support for samsung s6e3ha2 panel binding

On 11.01.2017 07:33, Hoegeun Kwon wrote: > The Samsung s6e3ha2 is a 5.7" 1440x2560 AMOLED panel connected > using MIPI-DSI interfaces. > > Signed-off-by: Donghwa Lee > Signed-off-by: Hyungwon Hwang > Signed-off-by: Hoegeun Kwon

Re: [Intel-gfx] 4.10-rc2 oops in DRM connector code

On Tue, Jan 10, 2017 at 08:52:47AM -0800, Dave Hansen wrote: > On 01/10/2017 02:31 AM, Daniel Vetter wrote: > > commit e73ab00e9a0f1731f34d0620a9c55f5c30c4ad4e > > Author: Daniel Vetter > > Date: Sun Dec 18 14:35:45 2016 +0100 > > > > drm: prevent double-(un)registration for connectors > >

Re: [PATCH v8 1/3] dt-bindings: Add support for samsung s6e3ha2 panel binding

On 11.01.2017 07:33, Hoegeun Kwon wrote: > The Samsung s6e3ha2 is a 5.7" 1440x2560 AMOLED panel connected > using MIPI-DSI interfaces. > > Signed-off-by: Donghwa Lee > Signed-off-by: Hyungwon Hwang > Signed-off-by: Hoegeun Kwon > Tested-by: Chanwoo Choi > Reviewed-by: Andrzej Hajda > --- >

Re: [patch v2] mm, thp: add new defer+madvise defrag option

[+CC linux-api] On 01/11/2017 01:15 AM, David Rientjes wrote: > There is no thp defrag option that currently allows MADV_HUGEPAGE regions > to do direct compaction and reclaim while all other thp allocations simply > trigger kswapd and kcompactd in the background and fail immediately. > > The

Re: [patch v2] mm, thp: add new defer+madvise defrag option

[+CC linux-api] On 01/11/2017 01:15 AM, David Rientjes wrote: > There is no thp defrag option that currently allows MADV_HUGEPAGE regions > to do direct compaction and reclaim while all other thp allocations simply > trigger kswapd and kcompactd in the background and fail immediately. > > The

Re: [PATCH net-next v2] net: dsa: make "label" property optional for dsa2

Tue, Jan 10, 2017 at 06:58:18PM CET, f.faine...@gmail.com wrote: >On 01/10/2017 01:55 AM, Jiri Pirko wrote: >> Mon, Jan 09, 2017 at 07:06:39PM CET, f.faine...@gmail.com wrote: >>> On 01/09/2017 09:58 AM, Jiri Pirko wrote: Mon, Jan 09, 2017 at 06:42:07PM CET, f.faine...@gmail.com wrote: >

Re: [PATCH net-next v2] net: dsa: make "label" property optional for dsa2

Tue, Jan 10, 2017 at 06:58:18PM CET, f.faine...@gmail.com wrote: >On 01/10/2017 01:55 AM, Jiri Pirko wrote: >> Mon, Jan 09, 2017 at 07:06:39PM CET, f.faine...@gmail.com wrote: >>> On 01/09/2017 09:58 AM, Jiri Pirko wrote: Mon, Jan 09, 2017 at 06:42:07PM CET, f.faine...@gmail.com wrote: >

Re: [PATCH] serial: fsl_lpuart: Remove the alias node dependence

On Wed, Dec 14, 2016 at 04:33:32PM +0800, Yuan Yao wrote: > From: Yuan Yao > > Numbering the ttyLPn space should not depend on the generic name > "serial". > > If don't add the alias node like:"serial0 = ", then lpuart > will probe failed: > [0.773410] fsl-lpuart

Re: [PATCH] serial: fsl_lpuart: Remove the alias node dependence

On Wed, Dec 14, 2016 at 04:33:32PM +0800, Yuan Yao wrote: > From: Yuan Yao > > Numbering the ttyLPn space should not depend on the generic name > "serial". > > If don't add the alias node like:"serial0 = ", then lpuart > will probe failed: > [0.773410] fsl-lpuart 295.serial: failed to

Re: [PATCH] tty/serial: atmel: RS485 half duplex w/DMA: enable RX after TX is done

On Mon, Jan 02, 2017 at 03:14:37PM +0100, Richard Genoud wrote: > 2017-01-02 12:53 GMT+01:00 Alexandre Belloni > : > > On 06/12/2016 at 13:05:33 +0100, Richard Genoud wrote : > >> When using RS485 in half duplex, RX should be enabled when TX is > >> finished,

Re: [PATCH] tty/serial: atmel: RS485 half duplex w/DMA: enable RX after TX is done

On Mon, Jan 02, 2017 at 03:14:37PM +0100, Richard Genoud wrote: > 2017-01-02 12:53 GMT+01:00 Alexandre Belloni > : > > On 06/12/2016 at 13:05:33 +0100, Richard Genoud wrote : > >> When using RS485 in half duplex, RX should be enabled when TX is > >> finished, and stopped when TX starts. > >> > >>

Re: [PATCH] tty/serial: atmel_serial: BUG: stop DMA from transmitting in stop_tx

On Mon, Jan 02, 2017 at 03:16:46PM +0100, Richard Genoud wrote: > 2017-01-02 12:13 GMT+01:00 Nicolas Ferre : > > Le 13/12/2016 à 17:27, Richard Genoud a écrit : > >> If we don't disable the transmitter in atmel_stop_tx, the DMA buffer > >> continues to send data until it

Re: [PATCH] tty/serial: atmel_serial: BUG: stop DMA from transmitting in stop_tx

On Mon, Jan 02, 2017 at 03:16:46PM +0100, Richard Genoud wrote: > 2017-01-02 12:13 GMT+01:00 Nicolas Ferre : > > Le 13/12/2016 à 17:27, Richard Genoud a écrit : > >> If we don't disable the transmitter in atmel_stop_tx, the DMA buffer > >> continues to send data until it is emptied. > >> This

Re: [PATCH] mm: Respect FOLL_FORCE/FOLL_COW for thp

On Tue, 10 Jan 2017, Hugh Dickins wrote: > On Thu, 5 Jan 2017, Kirill A. Shutemov wrote: > > On Thu, Jan 05, 2017 at 12:36:58AM -0500, Keno Fischer wrote: > > > struct page *follow_devmap_pmd(struct vm_area_struct *vma, unsigned long > > > addr, > > > pmd_t *pmd, int flags) > > > { >

Re: [PATCH] mm: Respect FOLL_FORCE/FOLL_COW for thp

On Tue, 10 Jan 2017, Hugh Dickins wrote: > On Thu, 5 Jan 2017, Kirill A. Shutemov wrote: > > On Thu, Jan 05, 2017 at 12:36:58AM -0500, Keno Fischer wrote: > > > struct page *follow_devmap_pmd(struct vm_area_struct *vma, unsigned long > > > addr, > > > pmd_t *pmd, int flags) > > > { >

Re: [PATCH v3 04/15] livepatch/x86: add TIF_PATCH_PENDING thread flag

On Thursday 08 December 2016 11:38 PM, Josh Poimboeuf wrote: Add the TIF_PATCH_PENDING thread flag to enable the new livepatch per-task consistency model for x86_64. The bit getting set indicates the thread has a pending patch which needs to be applied when the thread exits the kernel. The bit

Re: [PATCH v3 04/15] livepatch/x86: add TIF_PATCH_PENDING thread flag

On Thursday 08 December 2016 11:38 PM, Josh Poimboeuf wrote: Add the TIF_PATCH_PENDING thread flag to enable the new livepatch per-task consistency model for x86_64. The bit getting set indicates the thread has a pending patch which needs to be applied when the thread exits the kernel. The bit

[PATCH v11 11/12] drm/mediatek: update DSI sub driver flow for sending commands to panel

This patch update enable/disable flow of DSI module. Original flow works on there is a bridge chip: DSI -> bridge -> panel. In this case: DSI -> panel, the DSI sub driver flow should be updated. We need to initialize DSI first so that we can send commands to panel. Signed-off-by: shaoming chen

[PATCH v11 09/12] drm/mediatek: add dsi transfer function

From: shaoming chen add dsi read/write commands for transfer function Signed-off-by: shaoming chen --- drivers/gpu/drm/mediatek/mtk_dsi.c | 168 - 1 file changed, 166 insertions(+), 2 deletions(-)

[PATCH v11 11/12] drm/mediatek: update DSI sub driver flow for sending commands to panel

This patch update enable/disable flow of DSI module. Original flow works on there is a bridge chip: DSI -> bridge -> panel. In this case: DSI -> panel, the DSI sub driver flow should be updated. We need to initialize DSI first so that we can send commands to panel. Signed-off-by: shaoming chen

[PATCH v11 09/12] drm/mediatek: add dsi transfer function

From: shaoming chen add dsi read/write commands for transfer function Signed-off-by: shaoming chen --- drivers/gpu/drm/mediatek/mtk_dsi.c | 168 - 1 file changed, 166 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/mediatek/mtk_dsi.c

[PATCH v11 08/12] drm/mediatek: add dsi interrupt control

From: shaoming chen add dsi interrupt control Signed-off-by: shaoming chen --- drivers/gpu/drm/mediatek/mtk_dsi.c | 92 ++ 1 file changed, 92 insertions(+) diff --git

[PATCH v11 10/12] drm/mediatek: add non-continuous clock mode and EOT packet control

This patch will update dsi clock control method. 1. dsi non-continue clock mode will enhance antistatic effect for panel 2. EOT packet control will judge whether dsi send end of packet or not by customize Signed-off-by: shaoming chen Signed-off-by: YT Shen

[PATCH v11 12/12] drm/mediatek: add support for Mediatek SoC MT2701

This patch add support for the Mediatek MT2701 DISP subsystem. There is only one OVL engine in MT2701. Signed-off-by: YT Shen --- drivers/gpu/drm/mediatek/mtk_disp_ovl.c | 8 drivers/gpu/drm/mediatek/mtk_disp_rdma.c| 6 ++

[PATCH v11 08/12] drm/mediatek: add dsi interrupt control

From: shaoming chen add dsi interrupt control Signed-off-by: shaoming chen --- drivers/gpu/drm/mediatek/mtk_dsi.c | 92 ++ 1 file changed, 92 insertions(+) diff --git a/drivers/gpu/drm/mediatek/mtk_dsi.c b/drivers/gpu/drm/mediatek/mtk_dsi.c index

[PATCH v11 10/12] drm/mediatek: add non-continuous clock mode and EOT packet control

This patch will update dsi clock control method. 1. dsi non-continue clock mode will enhance antistatic effect for panel 2. EOT packet control will judge whether dsi send end of packet or not by customize Signed-off-by: shaoming chen Signed-off-by: YT Shen ---

[PATCH v11 12/12] drm/mediatek: add support for Mediatek SoC MT2701

This patch add support for the Mediatek MT2701 DISP subsystem. There is only one OVL engine in MT2701. Signed-off-by: YT Shen --- drivers/gpu/drm/mediatek/mtk_disp_ovl.c | 8 drivers/gpu/drm/mediatek/mtk_disp_rdma.c| 6 ++ drivers/gpu/drm/mediatek/mtk_drm_ddp.c | 17

[PATCH v11 07/12] drm/mediatek: cleaning up and refine

cleaning up unused define and refine function name and variable Signed-off-by: shaoming chen Signed-off-by: YT Shen --- drivers/gpu/drm/mediatek/mtk_dsi.c | 73 -- drivers/gpu/drm/mediatek/mtk_mipi_tx.c | 8

[PATCH v11 07/12] drm/mediatek: cleaning up and refine

cleaning up unused define and refine function name and variable Signed-off-by: shaoming chen Signed-off-by: YT Shen --- drivers/gpu/drm/mediatek/mtk_dsi.c | 73 -- drivers/gpu/drm/mediatek/mtk_mipi_tx.c | 8 ++-- 2 files changed, 39 insertions(+), 42

[PATCH v11 04/12] drm/mediatek: add shadow register support

We need to acquire mutex before using the resources, and need to release it after finished. So we don't need to write registers in the blanking period. Signed-off-by: YT Shen --- drivers/gpu/drm/mediatek/mtk_drm_crtc.c | 75 -

[PATCH v11 03/12] drm/mediatek: add *driver_data for different hardware settings

There are some hardware settings changed, between MT8173 & MT2701: DISP_OVL address offset changed, color format definition changed. DISP_RDMA fifo size changed. DISP_COLOR offset changed. MIPI_TX pll setting changed. And add prefix for mtk_ddp_main & mtk_ddp_ext & mutex_mod. Signed-off-by: YT

[PATCH v11 06/12] drm/mediatek: update display module connections

update connections for OVL, RDMA, BLS, DSI Signed-off-by: YT Shen --- drivers/gpu/drm/mediatek/mtk_drm_ddp.c | 25 + 1 file changed, 25 insertions(+) diff --git a/drivers/gpu/drm/mediatek/mtk_drm_ddp.c b/drivers/gpu/drm/mediatek/mtk_drm_ddp.c

[PATCH v11 01/12] dt-bindings: display: mediatek: update supported chips

Add decriptions about supported chips, including MT2701 & MT8173 Signed-off-by: YT Shen --- Documentation/devicetree/bindings/display/mediatek/mediatek,disp.txt | 2 ++ Documentation/devicetree/bindings/display/mediatek/mediatek,dsi.txt | 2 ++ 2 files changed, 4

[PATCH v11 04/12] drm/mediatek: add shadow register support

We need to acquire mutex before using the resources, and need to release it after finished. So we don't need to write registers in the blanking period. Signed-off-by: YT Shen --- drivers/gpu/drm/mediatek/mtk_drm_crtc.c | 75 -

[PATCH v11 03/12] drm/mediatek: add *driver_data for different hardware settings

There are some hardware settings changed, between MT8173 & MT2701: DISP_OVL address offset changed, color format definition changed. DISP_RDMA fifo size changed. DISP_COLOR offset changed. MIPI_TX pll setting changed. And add prefix for mtk_ddp_main & mtk_ddp_ext & mutex_mod. Signed-off-by: YT

[PATCH v11 06/12] drm/mediatek: update display module connections

update connections for OVL, RDMA, BLS, DSI Signed-off-by: YT Shen --- drivers/gpu/drm/mediatek/mtk_drm_ddp.c | 25 + 1 file changed, 25 insertions(+) diff --git a/drivers/gpu/drm/mediatek/mtk_drm_ddp.c b/drivers/gpu/drm/mediatek/mtk_drm_ddp.c index b77d456..a9b209c

[PATCH v11 01/12] dt-bindings: display: mediatek: update supported chips

Add decriptions about supported chips, including MT2701 & MT8173 Signed-off-by: YT Shen --- Documentation/devicetree/bindings/display/mediatek/mediatek,disp.txt | 2 ++ Documentation/devicetree/bindings/display/mediatek/mediatek,dsi.txt | 2 ++ 2 files changed, 4 insertions(+) diff --git

[PATCH v11 02/12] drm/mediatek: add helpers for coverting from the generic components

define helpers for converting from 'mtk_ddp_comp' to 'mtk_disp_ovl' define helpers for converting from 'mtk_ddp_comp' to 'mtk_disp_rdma' Signed-off-by: YT Shen --- drivers/gpu/drm/mediatek/mtk_disp_ovl.c | 15 +-- drivers/gpu/drm/mediatek/mtk_disp_rdma.c | 15

[PATCH v11 05/12] drm/mediatek: add BLS component

Add BLS component for PWM + GAMMA function Signed-off-by: YT Shen --- drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.c | 5 - drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.h | 2 ++ 2 files changed, 6 insertions(+), 1 deletion(-) diff --git

[PATCH v11 05/12] drm/mediatek: add BLS component

Add BLS component for PWM + GAMMA function Signed-off-by: YT Shen --- drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.c | 5 - drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.h | 2 ++ 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.c

[PATCH v11 02/12] drm/mediatek: add helpers for coverting from the generic components

define helpers for converting from 'mtk_ddp_comp' to 'mtk_disp_ovl' define helpers for converting from 'mtk_ddp_comp' to 'mtk_disp_rdma' Signed-off-by: YT Shen --- drivers/gpu/drm/mediatek/mtk_disp_ovl.c | 15 +-- drivers/gpu/drm/mediatek/mtk_disp_rdma.c | 15 +-- 2

[PATCH v11 00/12] MT2701 DRM support

This is MT2701 DRM support PATCH v10, based on 4.10-rc1. We add DSI interrupt control, transfer function for MIPI DSI panel support. Most codes are the same, except some register changed. For example: - DISP_OVL address offset changed, color format definition changed. - DISP_RDMA fifo size

[PATCH v11 00/12] MT2701 DRM support

This is MT2701 DRM support PATCH v10, based on 4.10-rc1. We add DSI interrupt control, transfer function for MIPI DSI panel support. Most codes are the same, except some register changed. For example: - DISP_OVL address offset changed, color format definition changed. - DISP_RDMA fifo size

Re: [PATCH 4.9 000/206] 4.9.3-stable review

On Tue, Jan 10, 2017 at 02:28:07PM -0800, Guenter Roeck wrote: > On Tue, Jan 10, 2017 at 02:34:43PM +0100, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.9.3 release. > > There are 206 patches in this series, all will be posted as a response > > to this one.

Re: [PATCH 4.9 000/206] 4.9.3-stable review

On Tue, Jan 10, 2017 at 02:28:07PM -0800, Guenter Roeck wrote: > On Tue, Jan 10, 2017 at 02:34:43PM +0100, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.9.3 release. > > There are 206 patches in this series, all will be posted as a response > > to this one.

Re: WARNING at fs/sysfs/group.c:237 .sysfs_remove_group+0xc4/0xd0 on Linus mainline

Hi , Let me know if the below community fix is been merged into upstream code. https://www.mail-archive.com/linux-scsi@vger.kernel.org/msg39187.html Thanks Seeteena On 01/11/2017 12:14 PM, abdul wrote: Hi Today's mainline shows warning while load/unload lpfc module on PowerPC Machine :

Re: WARNING at fs/sysfs/group.c:237 .sysfs_remove_group+0xc4/0xd0 on Linus mainline

Hi , Let me know if the below community fix is been merged into upstream code. https://www.mail-archive.com/linux-scsi@vger.kernel.org/msg39187.html Thanks Seeteena On 01/11/2017 12:14 PM, abdul wrote: Hi Today's mainline shows warning while load/unload lpfc module on PowerPC Machine :

Re: [PATCH 0/2] Style fixes: open code obfuscating macros

On Tue, Jan 10, 2017 at 04:34:41PM -0700, Logan Gunthorpe wrote: > > > On 10/01/17 04:06 PM, Joe Perches wrote: > > It might also be better to add and use YA > > logging macro like ndev_dbg > > > > #define ndev_dvg(ndev, fmt, ...)\ > > dev_dbg(&(ndev)->ntb.pdev->dev, fmt, ##__VA_ARGS__)

Re: [PATCH 0/2] Style fixes: open code obfuscating macros

On Tue, Jan 10, 2017 at 04:34:41PM -0700, Logan Gunthorpe wrote: > > > On 10/01/17 04:06 PM, Joe Perches wrote: > > It might also be better to add and use YA > > logging macro like ndev_dbg > > > > #define ndev_dvg(ndev, fmt, ...)\ > > dev_dbg(&(ndev)->ntb.pdev->dev, fmt, ##__VA_ARGS__)

Re: [PATCH v2 6/6] arm64: allwinner: a64: Increase the MMC max frequency

On Wed, Jan 11, 2017 at 3:15 AM, Maxime Ripard wrote: > Hi, > > On Tue, Jan 10, 2017 at 01:01:20AM +0800, Chen-Yu Tsai wrote: >> On Tue, Jan 10, 2017 at 12:46 AM, Maxime Ripard >> wrote: >> > All the controllers can have a

Re: [PATCH v2 6/6] arm64: allwinner: a64: Increase the MMC max frequency

On Wed, Jan 11, 2017 at 3:15 AM, Maxime Ripard wrote: > Hi, > > On Tue, Jan 10, 2017 at 01:01:20AM +0800, Chen-Yu Tsai wrote: >> On Tue, Jan 10, 2017 at 12:46 AM, Maxime Ripard >> wrote: >> > All the controllers can have a maximum frequency of 200MHz. >> > >> > Since older SoCs cannot go that

[PATCH v8 2/3] drm/panel: Add support for S6E3HA2 panel driver on TM2 board

This patch add support for MIPI-DSI based S6E3HA2 AMOLED panel driver. This panel has 1440x2560 resolution in 5.7-inch physical panel in the TM2 device. Signed-off-by: Donghwa Lee Signed-off-by: Hyungwon Hwang Signed-off-by: Hoegeun Kwon

[PATCH v8 2/3] drm/panel: Add support for S6E3HA2 panel driver on TM2 board

This patch add support for MIPI-DSI based S6E3HA2 AMOLED panel driver. This panel has 1440x2560 resolution in 5.7-inch physical panel in the TM2 device. Signed-off-by: Donghwa Lee Signed-off-by: Hyungwon Hwang Signed-off-by: Hoegeun Kwon Tested-by: Chanwoo Choi Reviewed-by: Andrzej Hajda ---

[PATCH v8 3/3] arm64: dts: exynos: Add support for S6E3HA2 panel device on TM2 board

From: Hyungwon Hwang This patch add the panel device tree node for S6E3HA2 display controller to TM2 dts. Signed-off-by: Hyungwon Hwang Signed-off-by: Andrzej Hajda Signed-off-by: Chanwoo Choi

[PATCH v8 3/3] arm64: dts: exynos: Add support for S6E3HA2 panel device on TM2 board

From: Hyungwon Hwang This patch add the panel device tree node for S6E3HA2 display controller to TM2 dts. Signed-off-by: Hyungwon Hwang Signed-off-by: Andrzej Hajda Signed-off-by: Chanwoo Choi Signed-off-by: Hoegeun Kwon Tested-by: Chanwoo Choi ---

[PATCH v8 1/3] dt-bindings: Add support for samsung s6e3ha2 panel binding

The Samsung s6e3ha2 is a 5.7" 1440x2560 AMOLED panel connected using MIPI-DSI interfaces. Signed-off-by: Donghwa Lee Signed-off-by: Hyungwon Hwang Signed-off-by: Hoegeun Kwon Tested-by: Chanwoo Choi

[PATCH v8 1/3] dt-bindings: Add support for samsung s6e3ha2 panel binding

The Samsung s6e3ha2 is a 5.7" 1440x2560 AMOLED panel connected using MIPI-DSI interfaces. Signed-off-by: Donghwa Lee Signed-off-by: Hyungwon Hwang Signed-off-by: Hoegeun Kwon Tested-by: Chanwoo Choi Reviewed-by: Andrzej Hajda --- .../bindings/display/panel/samsung,s6e3ha2.txt | 26

[PATCH v8 0/3] Add support for the S6E3HA2 panel on TM2 board

Purpose of this patch is add support for S6E3HA2 AMOLED panel on the TM2 board. The first patch adds support for S6E3HA2 panel device tree document and driver, the second patch add support for S6E3HA2 panel device tree. Thank you for your review. Changes for V8: - Applied below two patches:

[PATCH v8 0/3] Add support for the S6E3HA2 panel on TM2 board

Purpose of this patch is add support for S6E3HA2 AMOLED panel on the TM2 board. The first patch adds support for S6E3HA2 panel device tree document and driver, the second patch add support for S6E3HA2 panel device tree. Thank you for your review. Changes for V8: - Applied below two patches:

Re: [Cocci] [PATCH] coccicheck: add a test for repeat copy_from_user

I looked at the get_user part of the original script. It looks like most of the complexity is to deal with the possibility of the src location being expressed in two different ways between the two calls. Even if this happens in practice only for get_user, it would seem that it could happen for

Re: [Cocci] [PATCH] coccicheck: add a test for repeat copy_from_user

I looked at the get_user part of the original script. It looks like most of the complexity is to deal with the possibility of the src location being expressed in two different ways between the two calls. Even if this happens in practice only for get_user, it would seem that it could happen for

[PATCH perf/core v2 4/4] perf-probe: Find probe events without target module

Find probe events without -m "module" option. If perf-probe failed to find given function in kernel image, it tries to find same symbol and module in kallsyms, and retry search in the found module. E.g. # perf probe -D i915_capabilities p:probe/i915_capabilities i915:i915_capabilities+0

[PATCH perf/core v2 4/4] perf-probe: Find probe events without target module

Find probe events without -m "module" option. If perf-probe failed to find given function in kernel image, it tries to find same symbol and module in kallsyms, and retry search in the found module. E.g. # perf probe -D i915_capabilities p:probe/i915_capabilities i915:i915_capabilities+0

[PATCH perf/core v2 3/4] perf-probe: Fix to probe on gcc generated functions in modules

Fix to probe on gcc generated functions on modules. Since probing on a module is based on its symbol name, it should be adjusted on actual symbols. E.g. without this fix, perf probe shows probe definition on non-exist symbol as below. $ perf probe -m build-x86_64/net/netfilter/nf_nat.ko -F

[PATCH perf/core v2 3/4] perf-probe: Fix to probe on gcc generated functions in modules

Fix to probe on gcc generated functions on modules. Since probing on a module is based on its symbol name, it should be adjusted on actual symbols. E.g. without this fix, perf probe shows probe definition on non-exist symbol as below. $ perf probe -m build-x86_64/net/netfilter/nf_nat.ko -F

[PATCH perf/core v2 2/4] perf-probe: Add error checks to offline probe post-processing

Add error check codes to post process and improve it for offline probe events as; - post process fails if no matched symbol found in map(-ENOENT) or strdup() failed(-ENOMEM). - Even if the symbol name is same, it updates symbol address and offset. Signed-off-by: Masami Hiramatsu

[PATCH perf/core v2 2/4] perf-probe: Add error checks to offline probe post-processing

Add error check codes to post process and improve it for offline probe events as; - post process fails if no matched symbol found in map(-ENOENT) or strdup() failed(-ENOMEM). - Even if the symbol name is same, it updates symbol address and offset. Signed-off-by: Masami Hiramatsu ---

Re: x86-64: Maintain 16-byte stack alignment

On Tue, Jan 10, 2017 at 8:35 PM, Herbert Xu wrote: > On Tue, Jan 10, 2017 at 08:17:17PM -0800, Linus Torvalds wrote: >> >> That said, I do think that the "don't assume stack alignment, do it by >> hand" may be the safer thing. Because who knows what the random rules

Re: x86-64: Maintain 16-byte stack alignment

On Tue, Jan 10, 2017 at 8:35 PM, Herbert Xu wrote: > On Tue, Jan 10, 2017 at 08:17:17PM -0800, Linus Torvalds wrote: >> >> That said, I do think that the "don't assume stack alignment, do it by >> hand" may be the safer thing. Because who knows what the random rules >> will be on other

[PATCH perf/core v2 1/4] perf-probe: Fix to show correct locations for events on modules

Fix to show correct locations for events on modules by relocating given address instead of retrying after failure. This happens when the module text size is enough big, bigger than sh_addr, because original code retries withgiven address + sh_addr if it failed to find CU DIE at the given address.

[PATCH perf/core v2 1/4] perf-probe: Fix to show correct locations for events on modules

Fix to show correct locations for events on modules by relocating given address instead of retrying after failure. This happens when the module text size is enough big, bigger than sh_addr, because original code retries withgiven address + sh_addr if it failed to find CU DIE at the given address.

[PATCH perf/core v2 0/4] perf-probe: Fix and improve module probe events

Hello, This is the 2nd version of the series for fixing offline/online module probe support and improving perf-probe to probe module without -m option (Thanks Arnaldo!). This includes below patches. - [1/4] Fix perf-probe --list to show correct probe location in module. - [2/4]

[PATCH perf/core v2 0/4] perf-probe: Fix and improve module probe events

Hello, This is the 2nd version of the series for fixing offline/online module probe support and improving perf-probe to probe module without -m option (Thanks Arnaldo!). This includes below patches. - [1/4] Fix perf-probe --list to show correct probe location in module. - [2/4]

Re: [RFC] coccicheck: add a test for repeat memory fetches

On Tue, 10 Jan 2017, Kees Cook wrote: > On Tue, Jan 10, 2017 at 1:14 PM, Julia Lawall wrote: > > OK, I have the impression that what you are looking for is the following, > > that currently does not seem to work well. Still maybe it gives an idea. > > > > The basic

Re: [RFC] coccicheck: add a test for repeat memory fetches

On Tue, 10 Jan 2017, Kees Cook wrote: > On Tue, Jan 10, 2017 at 1:14 PM, Julia Lawall wrote: > > OK, I have the impression that what you are looking for is the following, > > that currently does not seem to work well. Still maybe it gives an idea. > > > > The basic pattern is the following

Re: [PATCH] mm: Respect FOLL_FORCE/FOLL_COW for thp

On Thu, 5 Jan 2017, Kirill A. Shutemov wrote: > On Thu, Jan 05, 2017 at 12:36:58AM -0500, Keno Fischer wrote: > > struct page *follow_devmap_pmd(struct vm_area_struct *vma, unsigned long > > addr, > > pmd_t *pmd, int flags) > > { > > @@ -783,7 +793,7 @@ struct page

Re: [PATCH] mm: Respect FOLL_FORCE/FOLL_COW for thp

On Thu, 5 Jan 2017, Kirill A. Shutemov wrote: > On Thu, Jan 05, 2017 at 12:36:58AM -0500, Keno Fischer wrote: > > struct page *follow_devmap_pmd(struct vm_area_struct *vma, unsigned long > > addr, > > pmd_t *pmd, int flags) > > { > > @@ -783,7 +793,7 @@ struct page

Re: [PATCH v7 1/4] drm/exynos: mic: Add mode_set callback function

Applied. Thanks. 2017년 01월 05일 19:20에 Hoegeun Kwon 이(가) 쓴 글: > Before applying the patch, used the of_get_videomode function to > parse the display-timings in the panel which is the child driver > of dsi in the devicetree. this is wrong. So removed the > of_get_videomode and fixed to get

Re: [PATCH v7 2/4] drm/exynos: mic: Fix parse_dt function

Applied. Thanks. 2017년 01월 05일 19:20에 Hoegeun Kwon 이(가) 쓴 글: > The OF graph is not necessary because the panel is a child of > dsi. therefore, the parse_dt function of dsi does not need to > check the remote_node connected to the panel. and the whole > parse_dt function should be refactored

Re: [PATCH v7 1/4] drm/exynos: mic: Add mode_set callback function

Applied. Thanks. 2017년 01월 05일 19:20에 Hoegeun Kwon 이(가) 쓴 글: > Before applying the patch, used the of_get_videomode function to > parse the display-timings in the panel which is the child driver > of dsi in the devicetree. this is wrong. So removed the > of_get_videomode and fixed to get

Re: [PATCH v7 2/4] drm/exynos: mic: Fix parse_dt function

Applied. Thanks. 2017년 01월 05일 19:20에 Hoegeun Kwon 이(가) 쓴 글: > The OF graph is not necessary because the panel is a child of > dsi. therefore, the parse_dt function of dsi does not need to > check the remote_node connected to the panel. and the whole > parse_dt function should be refactored

Re: [PATCH 3/3] xen: optimize xenbus driver for multiple concurrent xenstore accesses

On 10/01/17 23:56, Boris Ostrovsky wrote: > > > >> diff --git a/drivers/xen/xenbus/xenbus_xs.c b/drivers/xen/xenbus/xenbus_xs.c >> index ebc768f..ebdfbee 100644 >> --- a/drivers/xen/xenbus/xenbus_xs.c >> +++ b/drivers/xen/xenbus/xenbus_xs.c > > >> - >> -static struct xs_handle xs_state; >>

Re: [PATCH 3/3] xen: optimize xenbus driver for multiple concurrent xenstore accesses

On 10/01/17 23:56, Boris Ostrovsky wrote: > > > >> diff --git a/drivers/xen/xenbus/xenbus_xs.c b/drivers/xen/xenbus/xenbus_xs.c >> index ebc768f..ebdfbee 100644 >> --- a/drivers/xen/xenbus/xenbus_xs.c >> +++ b/drivers/xen/xenbus/xenbus_xs.c > > >> - >> -static struct xs_handle xs_state; >>

Re: [Cocci] [RFC] coccicheck: add a test for repeat memory fetches

On Wednesday 11 January 2017 05:34 AM, Kees Cook wrote: On Tue, Jan 10, 2017 at 1:14 PM, Julia Lawall wrote: OK, I have the impression that what you are looking for is the following, that currently does not seem to work well. Still maybe it gives an idea. The basic

Re: [Cocci] [RFC] coccicheck: add a test for repeat memory fetches

On Wednesday 11 January 2017 05:34 AM, Kees Cook wrote: On Tue, Jan 10, 2017 at 1:14 PM, Julia Lawall wrote: OK, I have the impression that what you are looking for is the following, that currently does not seem to work well. Still maybe it gives an idea. The basic pattern is the following

  1   2   3   4   5   6   7   8   9   10   >