Re: [PATCH v6 01/14] ACPI: ARM64: IORT: minor cleanup for iort_match_node_callback()

Hi Lorenzo, On 2017/1/3 22:08, Lorenzo Pieralisi wrote: On Mon, Jan 02, 2017 at 09:31:32PM +0800, Hanjun Guo wrote: Cleanup iort_match_node_callback() a little bit to reduce some lines of code, aslo fix the indentation in iort_scan_node(). s/aslo/also "Also" in a commit log is a sign a

Re: [PATCH v6 01/14] ACPI: ARM64: IORT: minor cleanup for iort_match_node_callback()

Hi Lorenzo, On 2017/1/3 22:08, Lorenzo Pieralisi wrote: On Mon, Jan 02, 2017 at 09:31:32PM +0800, Hanjun Guo wrote: Cleanup iort_match_node_callback() a little bit to reduce some lines of code, aslo fix the indentation in iort_scan_node(). s/aslo/also "Also" in a commit log is a sign a

[v1] misc: genwqe: card_base:-Release memory regions obtained by pci_request_mem_regions

Free memory regions, if genwqe_bus_reset is not successful. Signed-off-by: Arvind Yadav --- drivers/misc/genwqe/card_base.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/misc/genwqe/card_base.c b/drivers/misc/genwqe/card_base.c index 6c1f49a..a998d40

[v1] misc: genwqe: card_base:-Release memory regions obtained by pci_request_mem_regions

Free memory regions, if genwqe_bus_reset is not successful. Signed-off-by: Arvind Yadav --- drivers/misc/genwqe/card_base.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/misc/genwqe/card_base.c b/drivers/misc/genwqe/card_base.c index 6c1f49a..a998d40 100644 ---

Re: [RFC PATCH] input: Add disable sysfs entry for every input device

On 3.01.2017 13:21, Bastien Nocera wrote: On Mon, 2017-01-02 at 18:09 +0100, Pali Rohár wrote: On Monday 02 January 2017 16:27:05 Bastien Nocera wrote: On Sun, 2016-12-25 at 11:04 +0100, Pali Rohár wrote: This patch allows user to disable events from any input device so events would not be

Re: [RFC PATCH] input: Add disable sysfs entry for every input device

On 3.01.2017 13:21, Bastien Nocera wrote: On Mon, 2017-01-02 at 18:09 +0100, Pali Rohár wrote: On Monday 02 January 2017 16:27:05 Bastien Nocera wrote: On Sun, 2016-12-25 at 11:04 +0100, Pali Rohár wrote: This patch allows user to disable events from any input device so events would not be

Re: [PATCH 2/7] mm, vmscan: add active list aging tracepoint

On Wed 04-01-17 14:07:22, Minchan Kim wrote: > On Tue, Jan 03, 2017 at 09:21:22AM +0100, Michal Hocko wrote: [...] > > with other tracepoints but that can be helpful because you do not have > > all the tracepoints enabled all the time. So unless you see this > > particular thing as a road block I

Re: [PATCH 2/7] mm, vmscan: add active list aging tracepoint

On Wed 04-01-17 14:07:22, Minchan Kim wrote: > On Tue, Jan 03, 2017 at 09:21:22AM +0100, Michal Hocko wrote: [...] > > with other tracepoints but that can be helpful because you do not have > > all the tracepoints enabled all the time. So unless you see this > > particular thing as a road block I

Re: [PATCH] virtio_blk: avoid DMA to stack for the sense buffer

On 2017年01月04日 13:25, Christoph Hellwig wrote: Most users of BLOCK_PC requests allocate the sense buffer on the stack, so to avoid DMA to the stack copy them to a field in the heap allocated virtblk_req structure. Without that any attempt at SCSI passthrough I/O, including the SG_IO ioctl

Re: [PATCH] virtio_blk: avoid DMA to stack for the sense buffer

On 2017年01月04日 13:25, Christoph Hellwig wrote: Most users of BLOCK_PC requests allocate the sense buffer on the stack, so to avoid DMA to the stack copy them to a field in the heap allocated virtblk_req structure. Without that any attempt at SCSI passthrough I/O, including the SG_IO ioctl

RE: [PATCH v2 2/3] dmaeninge: xilinx_dma: Fix bug in multiple frame stores scenario in vdma

Hi Jose Miguel Abreu, Thanks for the review... > >> If so then there is no race condition, but the HW image that I have > >> does not have this register enabled so I was getting this result > >> (memory corruption because not all framebuffers had addresses set). > > Thanks for the

RE: [PATCH v2 2/3] dmaeninge: xilinx_dma: Fix bug in multiple frame stores scenario in vdma

Hi Jose Miguel Abreu, Thanks for the review... > >> If so then there is no race condition, but the HW image that I have > >> does not have this register enabled so I was getting this result > >> (memory corruption because not all framebuffers had addresses set). > > Thanks for the

Re: [PATCH v4 1/3] drm/exynos: mic: Add mode_set callback function

2017년 01월 04일 15:58에 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 videomode struct through

Re: [PATCH v4 1/3] drm/exynos: mic: Add mode_set callback function

2017년 01월 04일 15:58에 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 videomode struct through

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

Hi Hoegeun, I tested this patch on Exynos5433-TM2 board. It is well working Tested-by: Chanwoo Choi Regards, Chanwoo Choi On 2017년 01월 04일 15:58, Hoegeun Kwon wrote: > This patch add support for MIPI-DSI based S6E3HA2 AMOLED panel > driver. This panel has 1440x2560

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

Hi Hoegeun, I tested this patch on Exynos5433-TM2 board. It is well working Tested-by: Chanwoo Choi Regards, Chanwoo Choi On 2017년 01월 04일 15:58, Hoegeun Kwon wrote: > This patch add support for MIPI-DSI based S6E3HA2 AMOLED panel > driver. This panel has 1440x2560 resolution in 5.7-inch

Re: [PATCH 2/7] mm, vmscan: add active list aging tracepoint

On 01/04/2017 06:07 AM, Minchan Kim wrote: > With this, > ./scripts/bloat-o-meter vmlinux.old vmlinux.new.new > add/remove: 1/1 grow/shrink: 0/9 up/down: 1394/-1636 (-242) > function old new delta > isolate_lru_pages -1394

Re: [PATCH v6 06/14] irqchip: gicv3-its: platform-msi: refactor its_pmsi_init() to prepare for ACPI

On 04.01.2017 08:02, Hanjun Guo wrote: Hi Tomasz, On 2017/1/3 15:41, Tomasz Nowicki wrote: Hi, Can we merge patch 4 & 6 into one patch so that we keep refactoring part as one piece ? I do not see a reason to keep them separate or have patch 5 in between. You can refactor what needs to be

Re: [PATCH 2/7] mm, vmscan: add active list aging tracepoint

On 01/04/2017 06:07 AM, Minchan Kim wrote: > With this, > ./scripts/bloat-o-meter vmlinux.old vmlinux.new.new > add/remove: 1/1 grow/shrink: 0/9 up/down: 1394/-1636 (-242) > function old new delta > isolate_lru_pages -1394

Re: [PATCH v6 06/14] irqchip: gicv3-its: platform-msi: refactor its_pmsi_init() to prepare for ACPI

On 04.01.2017 08:02, Hanjun Guo wrote: Hi Tomasz, On 2017/1/3 15:41, Tomasz Nowicki wrote: Hi, Can we merge patch 4 & 6 into one patch so that we keep refactoring part as one piece ? I do not see a reason to keep them separate or have patch 5 in between. You can refactor what needs to be

[PATCH v3 1/3] dmaengine: xilinx_dma: Check for channel idle state before submitting dma descriptor

Add channel idle state to ensure that dma descriptor is not submitted when VDMA engine is in progress. Reviewed-by: Jose Abreu Signed-off-by: Kedareswara rao Appana --- Changes for v3: ---> None. Changes for v2: ---> Add idle check in the reset as

[PATCH v3 1/3] dmaengine: xilinx_dma: Check for channel idle state before submitting dma descriptor

Add channel idle state to ensure that dma descriptor is not submitted when VDMA engine is in progress. Reviewed-by: Jose Abreu Signed-off-by: Kedareswara rao Appana --- Changes for v3: ---> None. Changes for v2: ---> Add idle check in the reset as suggested by Jose Abreu ---> Removed

[RESEND,PATCH v7 2/2] Documentation/ABI: Add ABI information for QCOM socinfo driver

The socinfo ABI document describes the information provided by socinfo driver and the corresponding attributes to access that information. Signed-off-by: Imran Khan --- Documentation/ABI/stable/sysfs-driver-qcom_socinfo | 147 + 1 file changed, 147

[RESEND,PATCH v7 0/2] soc: qcom: Add SoC info driver

This is patchset v7 which takes care of review comments received for patchset v6. Resending the patch set as the last one had a compilation error. Major changes with respect to patch v6 are as below: - Rather than showing string for h/w types, just show the number obtained from SMEM. The

[RESEND,PATCH v7 2/2] Documentation/ABI: Add ABI information for QCOM socinfo driver

The socinfo ABI document describes the information provided by socinfo driver and the corresponding attributes to access that information. Signed-off-by: Imran Khan --- Documentation/ABI/stable/sysfs-driver-qcom_socinfo | 147 + 1 file changed, 147 insertions(+) create mode

[RESEND,PATCH v7 0/2] soc: qcom: Add SoC info driver

This is patchset v7 which takes care of review comments received for patchset v6. Resending the patch set as the last one had a compilation error. Major changes with respect to patch v6 are as below: - Rather than showing string for h/w types, just show the number obtained from SMEM. The

[PATCH v2 1/1] extcon: usb-gpio: add pinctrl operation during system PM

At some systems, the pinctrl setting will be lost or needs to set as "sleep" state to save power consumption. So, we need to configure pinctrl as "sleep" state when system enters suspend, and as "default" state after system resumes. In this way, the pinctrl value can be recovered as "default"

[PATCH v2 1/1] extcon: usb-gpio: add pinctrl operation during system PM

At some systems, the pinctrl setting will be lost or needs to set as "sleep" state to save power consumption. So, we need to configure pinctrl as "sleep" state when system enters suspend, and as "default" state after system resumes. In this way, the pinctrl value can be recovered as "default"

Re: [PATCH] dax: fix deadlock with DAX 4k holes

On Tue 03-01-17 14:36:05, Ross Zwisler wrote: > Currently in DAX if we have three read faults on the same hole address we > can end up with the following: > > Thread 0 Thread 1Thread 2 > > dax_iomap_fault >

Re: [PATCH] dax: fix deadlock with DAX 4k holes

On Tue 03-01-17 14:36:05, Ross Zwisler wrote: > Currently in DAX if we have three read faults on the same hole address we > can end up with the following: > > Thread 0 Thread 1Thread 2 > > dax_iomap_fault >

[RESEND,PATCH v7 1/2] soc: qcom: Add SoC info driver

The SoC info driver provides information such as Chip ID, Chip family, serial number and other such details about Qualcomm SoCs to user space, so that if needed some user space utility(like antutu) can query such information using sysfs interface. Signed-off-by: Imran Khan

[RESEND,PATCH v7 1/2] soc: qcom: Add SoC info driver

The SoC info driver provides information such as Chip ID, Chip family, serial number and other such details about Qualcomm SoCs to user space, so that if needed some user space utility(like antutu) can query such information using sysfs interface. Signed-off-by: Imran Khan --- v6 --> v7: - Some

[PATCH] memory: tegra: Add a missing 'of_node_put()' call

If 'of_find_device_by_node()' fails, an 'of_node_put()' call is missing in the error handling path. Fix it by reordering the code. While at it, remove some empty lines in a more or less similar construction a few lines below. Signed-off-by: Christophe JAILLET ---

[PATCH] memory: tegra: Add a missing 'of_node_put()' call

If 'of_find_device_by_node()' fails, an 'of_node_put()' call is missing in the error handling path. Fix it by reordering the code. While at it, remove some empty lines in a more or less similar construction a few lines below. Signed-off-by: Christophe JAILLET ---

Re: [PATCH v4 2/3] ARM: dts: imx6: Support Savageboard dual

On 01/04/2017 01:55 PM, Milo Kim wrote: Common savageboard DT file is used for board support. Add the vendor name and specify the dtb file for i.MX6Q build. Reviewed-by: Fabio Estevam Signed-off-by: Milo Kim ---

Re: [PATCH v4 2/3] ARM: dts: imx6: Support Savageboard dual

On 01/04/2017 01:55 PM, Milo Kim wrote: Common savageboard DT file is used for board support. Add the vendor name and specify the dtb file for i.MX6Q build. Reviewed-by: Fabio Estevam Signed-off-by: Milo Kim --- .../devicetree/bindings/vendor-prefixes.txt| 1 +

[PATCH v3 3/3] dmaengine: xilinx_dma: Fix race condition in the driver for multiple descriptor scenario

When driver is handling AXI DMA SoftIP When user submits multiple descriptors back to back on the S2MM(recv) side with the current driver flow the last buffer descriptor next bd points to a invalid location resulting the invalid data or errors in the DMA engine. This patch fixes this issue by

[PATCH v3 3/3] dmaengine: xilinx_dma: Fix race condition in the driver for multiple descriptor scenario

When driver is handling AXI DMA SoftIP When user submits multiple descriptors back to back on the S2MM(recv) side with the current driver flow the last buffer descriptor next bd points to a invalid location resulting the invalid data or errors in the DMA engine. This patch fixes this issue by

[PATCH v3 0/3] dmaengine: xilinx_dma: Bug fixes

This patch series fixes below bugs in DMA and VDMA IP's ---> Do not start VDMA until frame buffer is processed by the h/w Fix ---> bug in Multi frame sotres handling in VDMA Fix issues w.r.to multi ---> frame descriptors submit with AXI DMA S2MM(recv) Side. Kedareswara rao Appana (3):

[PATCH v3 0/3] dmaengine: xilinx_dma: Bug fixes

This patch series fixes below bugs in DMA and VDMA IP's ---> Do not start VDMA until frame buffer is processed by the h/w Fix ---> bug in Multi frame sotres handling in VDMA Fix issues w.r.to multi ---> frame descriptors submit with AXI DMA S2MM(recv) Side. Kedareswara rao Appana (3):

[PATCH v3 2/3] dmaeninge: xilinx_dma: Fix bug in multiple frame stores scenario in vdma

When VDMA is configured for more than one frame in the h/w for example h/w is configured for n number of frames and user Submits n number of frames and triggered the DMA using issue_pending API. In the current driver flow we are submitting one frame at a time but we should submit all the n number

[PATCH v3 2/3] dmaeninge: xilinx_dma: Fix bug in multiple frame stores scenario in vdma

When VDMA is configured for more than one frame in the h/w for example h/w is configured for n number of frames and user Submits n number of frames and triggered the DMA using issue_pending API. In the current driver flow we are submitting one frame at a time but we should submit all the n number

Re: [PATCH v3] IB/umem: Release pid in error and ODP flow

On Wed, Jan 04, 2017 at 03:07:04PM +0800, Kenneth Lee wrote: > On Tue, Jan 03, 2017 at 12:12:24PM +0200, Leon Romanovsky wrote: > > Date: Tue, 3 Jan 2017 12:12:24 +0200 > > From: Leon Romanovsky > > To: Kenneth Lee > > CC: dledf...@redhat.com,

Re: [PATCH v3] IB/umem: Release pid in error and ODP flow

On Wed, Jan 04, 2017 at 03:07:04PM +0800, Kenneth Lee wrote: > On Tue, Jan 03, 2017 at 12:12:24PM +0200, Leon Romanovsky wrote: > > Date: Tue, 3 Jan 2017 12:12:24 +0200 > > From: Leon Romanovsky > > To: Kenneth Lee > > CC: dledf...@redhat.com, sean.he...@intel.com, hal.rosenst...@gmail.com, > >

Re: [PATCH 1/2] pwm: sunxi: allow the pwm to finish its pulse before disable

On Tue, Jan 03, 2017 at 05:55:54PM +0100, Alexandre Belloni wrote: > On 03/01/2017 at 16:59:57 +0100, Olliver Schinagl wrote : > > On 12-12-16 13:24, Maxime Ripard wrote: > > > On Thu, Dec 08, 2016 at 02:23:39PM +0100, Olliver Schinagl wrote: > > > > Hey Maxime, > > > > > > > > first off, also

Re: [PATCH 1/2] pwm: sunxi: allow the pwm to finish its pulse before disable

On Tue, Jan 03, 2017 at 05:55:54PM +0100, Alexandre Belloni wrote: > On 03/01/2017 at 16:59:57 +0100, Olliver Schinagl wrote : > > On 12-12-16 13:24, Maxime Ripard wrote: > > > On Thu, Dec 08, 2016 at 02:23:39PM +0100, Olliver Schinagl wrote: > > > > Hey Maxime, > > > > > > > > first off, also

RE: [PATCH 1/1] regulator: fixed: add suspend pm routines for pinctrl

>>On Tue, Jan 03, 2017 at 05:02:47PM +0800, Peter Chen wrote: >>> At some systems, the pinctrl setting will be lost or needs to set as >>> "sleep" state to save power consumption. So, we need to configure >>> pinctrl as "sleep" state when system enters suspend, and as "default" >>> state after

RE: [PATCH 1/1] regulator: fixed: add suspend pm routines for pinctrl

>>On Tue, Jan 03, 2017 at 05:02:47PM +0800, Peter Chen wrote: >>> At some systems, the pinctrl setting will be lost or needs to set as >>> "sleep" state to save power consumption. So, we need to configure >>> pinctrl as "sleep" state when system enters suspend, and as "default" >>> state after

[PATCH resend v4 2/3] ARM: dts: imx6: Support Savageboard dual

Common savageboard DT file is used for board support. Add the vendor name and specify the dtb file for i.MX6Q build. Reviewed-by: Fabio Estevam Signed-off-by: Milo Kim --- .../devicetree/bindings/vendor-prefixes.txt| 1 +

[PATCH resend v4 2/3] ARM: dts: imx6: Support Savageboard dual

Common savageboard DT file is used for board support. Add the vendor name and specify the dtb file for i.MX6Q build. Reviewed-by: Fabio Estevam Signed-off-by: Milo Kim --- .../devicetree/bindings/vendor-prefixes.txt| 1 + arch/arm/boot/dts/Makefile | 1 +

Re: [PATCH] rcu: fix the OOM problem of huge IP abnormal packet traffic

On 2017/1/4 8:57, Paul E. McKenney wrote: > On Wed, Dec 28, 2016 at 04:13:15PM -0800, Paul E. McKenney wrote: >> On Wed, Dec 28, 2016 at 01:58:06PM +0800, Ding Tianhong wrote: >>> Hi, Paul: >>> >>> I try to debug this problem and found this solution could work well for >>> both problem scene.

Re: [PATCH] rcu: fix the OOM problem of huge IP abnormal packet traffic

On 2017/1/4 8:57, Paul E. McKenney wrote: > On Wed, Dec 28, 2016 at 04:13:15PM -0800, Paul E. McKenney wrote: >> On Wed, Dec 28, 2016 at 01:58:06PM +0800, Ding Tianhong wrote: >>> Hi, Paul: >>> >>> I try to debug this problem and found this solution could work well for >>> both problem scene.

Re: [PATCH v6 06/14] irqchip: gicv3-its: platform-msi: refactor its_pmsi_init() to prepare for ACPI

Hi Tomasz, On 2017/1/3 15:41, Tomasz Nowicki wrote: Hi, Can we merge patch 4 & 6 into one patch so that we keep refactoring part as one piece ? I do not see a reason to keep them separate or have patch 5 in between. You can refactor what needs to be refactored, add necessary functions to

Re: [PATCH v6 06/14] irqchip: gicv3-its: platform-msi: refactor its_pmsi_init() to prepare for ACPI

Hi Tomasz, On 2017/1/3 15:41, Tomasz Nowicki wrote: Hi, Can we merge patch 4 & 6 into one patch so that we keep refactoring part as one piece ? I do not see a reason to keep them separate or have patch 5 in between. You can refactor what needs to be refactored, add necessary functions to

[PATCH v4 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 v4 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 --- arch/arm64/boot/dts/exynos/exynos5433-tm2.dts | 17

[PATCH v4 1/3] drm/exynos: mic: Add mode_set callback function

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 videomode struct through mode_set callback function. Signed-off-by: Hoegeun

[PATCH v4 1/3] drm/exynos: mic: Add mode_set callback function

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 videomode struct through mode_set callback function. Signed-off-by: Hoegeun

[PATCH v4 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. Changes for V4: - Removed display-timings in devicetree, the display-timings

[PATCH v4 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 v4 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. Changes for V4: - Removed display-timings in devicetree, the display-timings

[PATCH v4 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 --- .../bindings/display/panel/samsung,s6e3ha2.txt

[Acked] [PATCH] checkpatch: Warn on embedded function names

On Tue, Jan 03, 2017 at 07:21:54PM -0800, Joe Perches wrote: > Embedded function names are less appropriate to use when > refactoring can cause function renaming. Prefer the use > of "%s", __func__ to embedded function names. > > Signed-off-by: Joe Perches > --- >

[Acked] [PATCH] checkpatch: Warn on embedded function names

On Tue, Jan 03, 2017 at 07:21:54PM -0800, Joe Perches wrote: > Embedded function names are less appropriate to use when > refactoring can cause function renaming. Prefer the use > of "%s", __func__ to embedded function names. > > Signed-off-by: Joe Perches > --- > scripts/checkpatch.pl | 22

Re: [PATCH 7/7] misc: intel-ish-client: add intel ishtp clients driver

On 二, 2017-01-03 at 10:54 +0100, Jiri Kosina wrote: > On Fri, 23 Dec 2016, Even Xu wrote: > > [ ... snip ... ] > > > > +static ssize_t ishtp_cl_write(struct file *file, const char __user > > *ubuf, > > + size_t length, loff_t *offset) > > +{ > > + struct ishtp_cl_miscdev *ishtp_cl_misc =

Re: [PATCH 7/7] misc: intel-ish-client: add intel ishtp clients driver

On 二, 2017-01-03 at 10:54 +0100, Jiri Kosina wrote: > On Fri, 23 Dec 2016, Even Xu wrote: > > [ ... snip ... ] > > > > +static ssize_t ishtp_cl_write(struct file *file, const char __user > > *ubuf, > > + size_t length, loff_t *offset) > > +{ > > + struct ishtp_cl_miscdev *ishtp_cl_misc =

RE: [PATCH 1/1] regulator: fixed: add suspend pm routines for pinctrl

>On Tue, Jan 03, 2017 at 05:02:47PM +0800, Peter Chen wrote: >> At some systems, the pinctrl setting will be lost or needs to set as >> "sleep" state to save power consumption. So, we need to configure >> pinctrl as "sleep" state when system enters suspend, and as "default" >> state after system

RE: [PATCH 1/1] regulator: fixed: add suspend pm routines for pinctrl

>On Tue, Jan 03, 2017 at 05:02:47PM +0800, Peter Chen wrote: >> At some systems, the pinctrl setting will be lost or needs to set as >> "sleep" state to save power consumption. So, we need to configure >> pinctrl as "sleep" state when system enters suspend, and as "default" >> state after system

RE: [PATCH 1/1] extcon: usb-gpio: add pinctrl operation during system PM

> >On 03/01/17 10:17, Peter Chen wrote: >> At some systems, the pinctrl setting will be lost or needs to set as >> "sleep" state to save power consumption. So, we need to configure >> pinctrl as "sleep" state when system enters suspend, and as "default" >> state after system resumes. In this

RE: [PATCH 1/1] extcon: usb-gpio: add pinctrl operation during system PM

> >On 03/01/17 10:17, Peter Chen wrote: >> At some systems, the pinctrl setting will be lost or needs to set as >> "sleep" state to save power consumption. So, we need to configure >> pinctrl as "sleep" state when system enters suspend, and as "default" >> state after system resumes. In this

Re: [PATCH] i2c: i801: Register optional lis3lv02d i2c device on Dell machines

On Tue, Jan 03, 2017 at 10:29:34PM +0100, Benjamin Tissoires wrote: > On Jan 03 2017 or thereabouts, Dmitry Torokhov wrote: > > > Yet another option: can we add a new flag to i2c_board_info controlling > > whether we want to enable/disable wiring up host notify interrupt? > > That should be

Re: [PATCH 2/2] Fix warning during compilation

I have done this patch for mainline because since v4.3 the ipu driver doesn't work properly. The reason is mistake in v4.3 considering both functions ipu_irq_err and ipu_irq_fn for equal and they was merged to ipu_irq_handler. But there is only one difference between these functions which was

Re: [PATCH] i2c: i801: Register optional lis3lv02d i2c device on Dell machines

On Tue, Jan 03, 2017 at 10:29:34PM +0100, Benjamin Tissoires wrote: > On Jan 03 2017 or thereabouts, Dmitry Torokhov wrote: > > > Yet another option: can we add a new flag to i2c_board_info controlling > > whether we want to enable/disable wiring up host notify interrupt? > > That should be

Re: [PATCH 2/2] Fix warning during compilation

I have done this patch for mainline because since v4.3 the ipu driver doesn't work properly. The reason is mistake in v4.3 considering both functions ipu_irq_err and ipu_irq_fn for equal and they was merged to ipu_irq_handler. But there is only one difference between these functions which was

Re: [PATCH v5 0/2] change the proc handler for nsm_use_hostnames

Ping, any comments are welcome. Thanks B.R. Jia On 15/12/2016 3:24 PM, Jia He wrote: nsm_use_hostnames is a module parameter and it will be exported to sysctl procfs. This is to let user sometimes change it from userspace. But the minimal unit for sysctl procfs read/write it sizeof(int). In

Re: [PATCH v5 0/2] change the proc handler for nsm_use_hostnames

Ping, any comments are welcome. Thanks B.R. Jia On 15/12/2016 3:24 PM, Jia He wrote: nsm_use_hostnames is a module parameter and it will be exported to sysctl procfs. This is to let user sometimes change it from userspace. But the minimal unit for sysctl procfs read/write it sizeof(int). In

Re: [PATCH v3] IB/umem: Release pid in error and ODP flow

On Tue, Jan 03, 2017 at 12:12:24PM +0200, Leon Romanovsky wrote: > Date: Tue, 3 Jan 2017 12:12:24 +0200 > From: Leon Romanovsky > To: Kenneth Lee > CC: dledf...@redhat.com, sean.he...@intel.com, hal.rosenst...@gmail.com, > robin.mur...@arm.com,

Re: Designated initializers, struct randomization and addressing?

On Tue, Jan 3, 2017 at 10:27 PM, Julia Lawall wrote: > > > On Tue, 3 Jan 2017, Kees Cook wrote: > >> On Tue, Dec 20, 2016 at 9:29 AM, Joe Perches wrote: >> > On Fri, 2016-12-16 at 17:00 -0800, Kees Cook wrote: >> >> Prepare to mark sensitive kernel

Re: [PATCH v3] IB/umem: Release pid in error and ODP flow

On Tue, Jan 03, 2017 at 12:12:24PM +0200, Leon Romanovsky wrote: > Date: Tue, 3 Jan 2017 12:12:24 +0200 > From: Leon Romanovsky > To: Kenneth Lee > CC: dledf...@redhat.com, sean.he...@intel.com, hal.rosenst...@gmail.com, > robin.mur...@arm.com, jroe...@suse.de, egtv...@samfundet.no, >

Re: Designated initializers, struct randomization and addressing?

On Tue, Jan 3, 2017 at 10:27 PM, Julia Lawall wrote: > > > On Tue, 3 Jan 2017, Kees Cook wrote: > >> On Tue, Dec 20, 2016 at 9:29 AM, Joe Perches wrote: >> > On Fri, 2016-12-16 at 17:00 -0800, Kees Cook wrote: >> >> Prepare to mark sensitive kernel structures for randomization by making >> >

Re: [PATCH 0/2] Begin auditing SECCOMP_RET_ERRNO return actions

On Tue, Jan 3, 2017 at 8:43 PM, Richard Guy Briggs wrote: > On 2017-01-04 08:58, Tyler Hicks wrote: >> On 01/04/2017 04:44 AM, Kees Cook wrote: >> > On Tue, Jan 3, 2017 at 1:31 PM, Paul Moore wrote: >> >> On Tue, Jan 3, 2017 at 4:21 PM, Kees Cook

Re: [PATCH 0/2] Begin auditing SECCOMP_RET_ERRNO return actions

On Tue, Jan 3, 2017 at 8:43 PM, Richard Guy Briggs wrote: > On 2017-01-04 08:58, Tyler Hicks wrote: >> On 01/04/2017 04:44 AM, Kees Cook wrote: >> > On Tue, Jan 3, 2017 at 1:31 PM, Paul Moore wrote: >> >> On Tue, Jan 3, 2017 at 4:21 PM, Kees Cook wrote: >> >>> On Tue, Jan 3, 2017 at 1:13 PM,

Re: [PATCH 1/2] arm64: dma_mapping: allow PCI host driver to limit DMA mask

> commit 9a57d58d116800a535510053136c6dd7a9c26e25 > Author: Arnd Bergmann > Date: Tue Nov 17 14:06:55 2015 +0100 > > [EXPERIMENTAL] ARM64: check implement dma_set_mask > > Needs work for coherent mask > > Signed-off-by: Arnd Bergmann

Re: [PATCH 1/2] arm64: dma_mapping: allow PCI host driver to limit DMA mask

> commit 9a57d58d116800a535510053136c6dd7a9c26e25 > Author: Arnd Bergmann > Date: Tue Nov 17 14:06:55 2015 +0100 > > [EXPERIMENTAL] ARM64: check implement dma_set_mask > > Needs work for coherent mask > > Signed-off-by: Arnd Bergmann Unfortunately this is far incomplete

[PATCH] ACPI/PCI: Fix bus range comparation in pci_mcfg_lookup

The configuration data provided by an MCFG region (ie PCI segment and bus range) may span multiple host bridges. Current code in pci_mcfg_lookup() carries out an exact match of host bridge bus range start value against the MCFG region(s) bus range start value which would cause configurations like

[PATCH] ACPI/PCI: Fix bus range comparation in pci_mcfg_lookup

The configuration data provided by an MCFG region (ie PCI segment and bus range) may span multiple host bridges. Current code in pci_mcfg_lookup() carries out an exact match of host bridge bus range start value against the MCFG region(s) bus range start value which would cause configurations like

Re: [PATCH v2 1/2] ALSA: usb-audio: Fix irq/process data synchronization

On Mon, 02 Jan 2017 16:50:30 +0100, Ioan-Adrian Ratiu wrote: > > --- a/sound/usb/pcm.c > +++ b/sound/usb/pcm.c (snip) > @@ -850,7 +850,7 @@ static int snd_usb_pcm_prepare(struct snd_pcm_substream > *substream) > /* for playback, submit the URBs now; otherwise, the first hwptr_done >

Re: [PATCH v2 1/2] ALSA: usb-audio: Fix irq/process data synchronization

On Mon, 02 Jan 2017 16:50:30 +0100, Ioan-Adrian Ratiu wrote: > > --- a/sound/usb/pcm.c > +++ b/sound/usb/pcm.c (snip) > @@ -850,7 +850,7 @@ static int snd_usb_pcm_prepare(struct snd_pcm_substream > *substream) > /* for playback, submit the URBs now; otherwise, the first hwptr_done >

Re: Designated initializers, struct randomization and addressing?

On Tue, 3 Jan 2017, Kees Cook wrote: > On Tue, Dec 20, 2016 at 9:29 AM, Joe Perches wrote: > > On Fri, 2016-12-16 at 17:00 -0800, Kees Cook wrote: > >> Prepare to mark sensitive kernel structures for randomization by making > > sure they're using designated initializers. > >

Re: Designated initializers, struct randomization and addressing?

On Tue, 3 Jan 2017, Kees Cook wrote: > On Tue, Dec 20, 2016 at 9:29 AM, Joe Perches wrote: > > On Fri, 2016-12-16 at 17:00 -0800, Kees Cook wrote: > >> Prepare to mark sensitive kernel structures for randomization by making > > sure they're using designated initializers. > > > > About the

[PATCH zram] extend zero pages to same element pages

From: z00281421 Signed-off-by: z00281421 --- drivers/block/zram/zram_drv.c | 67 ++--- drivers/block/zram/zram_drv.h | 11 --- 2 files changed, 49 insertions(+), 29 deletions(-) diff

[PATCH zram] extend zero pages to same element pages

From: z00281421 Signed-off-by: z00281421 --- drivers/block/zram/zram_drv.c | 67 ++--- drivers/block/zram/zram_drv.h | 11 --- 2 files changed, 49 insertions(+), 29 deletions(-) diff --git a/drivers/block/zram/zram_drv.c

Re: [PATCH v3 0/8] pstore: ramoops: support multiple pmsg instances

On Mon, Dec 26, 2016 at 4:48 PM, 岩松信洋 / IWAMATSU，NOBUHIRO wrote: > Ping?_ > >> -Original Message- >> From: linux-kernel-ow...@vger.kernel.org >> [mailto:linux-kernel-ow...@vger.kernel.org] On Behalf Of 岩松信洋 / >> IWAMATSU，NOBUHIRO >> Sent: Monday, December

Re: [PATCH v3 0/8] pstore: ramoops: support multiple pmsg instances

On Mon, Dec 26, 2016 at 4:48 PM, 岩松信洋 / IWAMATSU，NOBUHIRO wrote: > Ping?_ > >> -Original Message- >> From: linux-kernel-ow...@vger.kernel.org >> [mailto:linux-kernel-ow...@vger.kernel.org] On Behalf Of 岩松信洋 / >> IWAMATSU，NOBUHIRO >> Sent: Monday, December 05, 2016 10:47 AM >> To: Kees

[PATCH] checkpatch: Warn on embedded function names

Embedded function names are less appropriate to use when refactoring can cause function renaming. Prefer the use of "%s", __func__ to embedded function names. Signed-off-by: Joe Perches --- scripts/checkpatch.pl | 22 -- 1 file changed, 20 insertions(+), 2

[PATCH] checkpatch: Warn on embedded function names

Embedded function names are less appropriate to use when refactoring can cause function renaming. Prefer the use of "%s", __func__ to embedded function names. Signed-off-by: Joe Perches --- scripts/checkpatch.pl | 22 -- 1 file changed, 20 insertions(+), 2 deletions(-)

Re: [PATCH RFC V2] purgatory: fix up declarations

Vivek, thanks for ccing me.. On 01/03/17 at 04:34pm, Nicholas Mc Guire wrote: > On Tue, Jan 03, 2017 at 10:38:14AM -0500, Vivek Goyal wrote: > > On Fri, Dec 23, 2016 at 12:43:07PM +0100, Nicholas Mc Guire wrote: > > > Add the missing declarations of basic purgatory functions and variables > > >

[PATCH] checkpatch: Warn on embedded function names

Embedded function names are less appropriate to use when refactoring can cause function renaming. Prefer the use of "%s", __func__ to embedded function names. Signed-off-by: Joe Perches --- scripts/checkpatch.pl | 22 -- 1 file changed, 20 insertions(+), 2

Re: [PATCH RFC V2] purgatory: fix up declarations

Vivek, thanks for ccing me.. On 01/03/17 at 04:34pm, Nicholas Mc Guire wrote: > On Tue, Jan 03, 2017 at 10:38:14AM -0500, Vivek Goyal wrote: > > On Fri, Dec 23, 2016 at 12:43:07PM +0100, Nicholas Mc Guire wrote: > > > Add the missing declarations of basic purgatory functions and variables > > >

[PATCH] checkpatch: Warn on embedded function names

Embedded function names are less appropriate to use when refactoring can cause function renaming. Prefer the use of "%s", __func__ to embedded function names. Signed-off-by: Joe Perches --- scripts/checkpatch.pl | 22 -- 1 file changed, 20 insertions(+), 2 deletions(-)

  1   2   3   4   5   6   7   8   9   10   >