Re: [PATCH v2] gpio: add Intel WhiskeyCove GPIO driver

> > Looks good. I have couple of minor comments, see below. Thanks for review again. > > > + * Copyright (C) 2015 Intel Corporation. All rights reserved. > > It is 2016 now isn't it? :-) Will fix this in v3. > > +#define DRV_NAME "bxt_wcove_gpio" > > Drop this. We have _TWO_ places using

[PATCH v3 3/4] reset: hisilicon: Change to syscon register access

From: Chen Feng There are two reset controllers in hi6220 SoC: The peripheral reset controller bits are part of sysctrl registers. The media reset controller bits are part of mediactrl registers. So change register access to syscon way. And rename current reset controller to peripheral one.

[PATCH v3 0/4] Add hi6220 media subsystem reset controller driver

This patch set adds support for HiSilicon hi6220 SoC media subsystem reset controller. Change history: v3: - Split regmap register access change and mediactrl support. v2: - Update binding document for media reset controller. - Separate peripheral and media reset controller ops. Chen Feng (1):

[PATCH v3 4/4] reset: hisilicon: Add hi6220 media subsystem reset support

Add hi6220 media subsystem reset controller. Signed-off-by: Chen Feng Signed-off-by: Xia Qing Signed-off-by: Xinliang Liu --- drivers/reset/hisilicon/hi6220_reset.c | 49 -- 1 file changed, 47 insertions(+), 2 deletions(-) diff --git

RE: [PATCH v2] mmc: dw_mmc: remove UBSAN warning in dw_mci_setup_bus()

Hi, > -Original Message- > From: Seung-Woo Kim [mailto:sw0312@samsung.com] > Sent: Monday, June 20, 2016 12:30 PM > To: 'Jaehoon Chung'; ulf.hans...@linaro.org; linux-...@vger.kernel.org; > linux-kernel@vger.kernel.org > Cc: sw0312@samsung.com > Subject: RE: [PATCH v2] mmc:

RE: [PATCH v2] mmc: dw_mmc: remove UBSAN warning in dw_mci_setup_bus()

Hi, > -Original Message- > From: Seung-Woo Kim [mailto:sw0312@samsung.com] > Sent: Monday, June 20, 2016 12:30 PM > To: 'Jaehoon Chung'; ulf.hans...@linaro.org; linux-...@vger.kernel.org; > linux-kernel@vger.kernel.org > Cc: sw0312@samsung.com > Subject: RE: [PATCH v2] mmc:

Re: [PATCH v6 2/2] phy: rockchip-inno-usb2: add a new driver for Rockchip usb2phy

Hi Heiko & Guenter, On 2016/6/20 11:00, Guenter Roeck wrote: On Sun, Jun 19, 2016 at 6:27 PM, Frank Wang wrote: Hi Guenter, On 2016/6/17 21:20, Guenter Roeck wrote: Hi Frank, On 06/16/2016 11:43 PM, Frank Wang wrote: Hi Guenter, On 2016/6/17 12:59, Guenter

Re: [PATCH v6 2/2] phy: rockchip-inno-usb2: add a new driver for Rockchip usb2phy

Hi Heiko & Guenter, On 2016/6/20 11:00, Guenter Roeck wrote: On Sun, Jun 19, 2016 at 6:27 PM, Frank Wang wrote: Hi Guenter, On 2016/6/17 21:20, Guenter Roeck wrote: Hi Frank, On 06/16/2016 11:43 PM, Frank Wang wrote: Hi Guenter, On 2016/6/17 12:59, Guenter Roeck wrote: On 06/16/2016

RE: [PATCH v2] mmc: dw_mmc: remove UBSAN warning in dw_mci_setup_bus()

Hello Jaehoon, > -Original Message- > From: Jaehoon Chung [mailto:jh80.ch...@samsung.com] > Sent: Monday, June 20, 2016 11:34 AM > To: Seung-Woo Kim; ulf.hans...@linaro.org; linux-...@vger.kernel.org; > linux-kernel@vger.kernel.org > Subject: Re: [PATCH v2] mmc: dw_mmc: remove UBSAN

Re: [PATCH 2/2] perf record: Add --dry-run option to check cmdline options

On 2016/6/17 0:48, Arnaldo Carvalho de Melo wrote: Em Thu, Jun 16, 2016 at 08:02:41AM +, Wang Nan escreveu: With '--dry-run', 'perf record' doesn't do reall recording. Combine with llvm.dump-obj option, --dry-run can be used to help compile BPF objects for embedded platform. So these are

RE: [PATCH v2] mmc: dw_mmc: remove UBSAN warning in dw_mci_setup_bus()

Hello Jaehoon, > -Original Message- > From: Jaehoon Chung [mailto:jh80.ch...@samsung.com] > Sent: Monday, June 20, 2016 11:34 AM > To: Seung-Woo Kim; ulf.hans...@linaro.org; linux-...@vger.kernel.org; > linux-kernel@vger.kernel.org > Subject: Re: [PATCH v2] mmc: dw_mmc: remove UBSAN

Re: [PATCH 2/2] perf record: Add --dry-run option to check cmdline options

On 2016/6/17 0:48, Arnaldo Carvalho de Melo wrote: Em Thu, Jun 16, 2016 at 08:02:41AM +, Wang Nan escreveu: With '--dry-run', 'perf record' doesn't do reall recording. Combine with llvm.dump-obj option, --dry-run can be used to help compile BPF objects for embedded platform. So these are

linux-next: manual merge of the iommu tree with the arm tree

Hi Joerg, Today's linux-next merge of the iommu tree got a conflict in: drivers/iommu/mtk_iommu.c between commit: d267804c8457 ("iommu: convert DT component matching to component_match_add_release()") from the arm tree and commit: da4d6e6d3b3e ("iommu/mediatek: Convert DT component

linux-next: manual merge of the iommu tree with the arm tree

Hi Joerg, Today's linux-next merge of the iommu tree got a conflict in: drivers/iommu/mtk_iommu.c between commit: d267804c8457 ("iommu: convert DT component matching to component_match_add_release()") from the arm tree and commit: da4d6e6d3b3e ("iommu/mediatek: Convert DT component

[PATCH v3 3/8] mfd: ac100: Add driver for X-Powers AC100 audio codec / RTC combo IC

The AC100 is a multifunction device with an audio codec subsystem and an RTC subsystem. These two subsystems share a common register space and host interface. Signed-off-by: Chen-Yu Tsai Acked-by: Lee Jones --- Changes since v2: - Dropped file name -

[PATCH v3 0/8] mfd: ac100: Add support for X-Powers AC100 audio codec / RTC combo IC

Hi everyone, This series adds support for X-Powers' AC100 audio codec / RTC combo IC. This chip is found on Allwinner A80 SoC based boards, and is also part of the AXP813/AXP818 PMIC found with Allwinner A83T SoCs. The series focuses on the RTC side of the chip. The audio codec will be done

[PATCH v3 4/8] rtc: ac100: Add RTC driver for X-Powers AC100

X-Powers AC100 is a codec / RTC combo chip. This driver supports the RTC sub-device. The RTC block also has clock outputs and non-volatile storage. Non-volatile storage wthin the RTC hardware is not supported. Clock output support is added in the next patch. Signed-off-by: Chen-Yu Tsai

[PATCH v3 3/8] mfd: ac100: Add driver for X-Powers AC100 audio codec / RTC combo IC

The AC100 is a multifunction device with an audio codec subsystem and an RTC subsystem. These two subsystems share a common register space and host interface. Signed-off-by: Chen-Yu Tsai Acked-by: Lee Jones --- Changes since v2: - Dropped file name - Added copyright line. - Changed

[PATCH v3 0/8] mfd: ac100: Add support for X-Powers AC100 audio codec / RTC combo IC

Hi everyone, This series adds support for X-Powers' AC100 audio codec / RTC combo IC. This chip is found on Allwinner A80 SoC based boards, and is also part of the AXP813/AXP818 PMIC found with Allwinner A83T SoCs. The series focuses on the RTC side of the chip. The audio codec will be done

[PATCH v3 4/8] rtc: ac100: Add RTC driver for X-Powers AC100

X-Powers AC100 is a codec / RTC combo chip. This driver supports the RTC sub-device. The RTC block also has clock outputs and non-volatile storage. Non-volatile storage wthin the RTC hardware is not supported. Clock output support is added in the next patch. Signed-off-by: Chen-Yu Tsai ---

[PATCH v3 1/8] regmap: Support bulk writes for devices without raw formatting

When doing a bulk writes from a device which lacks raw I/O support we fall back to doing register at a time reads but we still use the raw formatters in order to render the data into the word size used by the device (since bulk reads still operate on the device word size rather than unsigned

[PATCH v3 2/8] mfd: ac100: Add device tree bindings for X-Powers AC100 codec/RTC combo IC

Signed-off-by: Chen-Yu Tsai --- Changes since v2: - Fix interrupt line for ac100_codec in provided example. --- Documentation/devicetree/bindings/mfd/ac100.txt | 42 + 1 file changed, 42 insertions(+) create mode 100644

[PATCH v3 1/8] regmap: Support bulk writes for devices without raw formatting

When doing a bulk writes from a device which lacks raw I/O support we fall back to doing register at a time reads but we still use the raw formatters in order to render the data into the word size used by the device (since bulk reads still operate on the device word size rather than unsigned

[PATCH v3 2/8] mfd: ac100: Add device tree bindings for X-Powers AC100 codec/RTC combo IC

Signed-off-by: Chen-Yu Tsai --- Changes since v2: - Fix interrupt line for ac100_codec in provided example. --- Documentation/devicetree/bindings/mfd/ac100.txt | 42 + 1 file changed, 42 insertions(+) create mode 100644 Documentation/devicetree/bindings/mfd/ac100.txt

RE: [PATCH v3 1/2] usb: ohci-at91: Forcibly suspend ports while USB suspend

Hi Aleandre, > -Original Message- > From: Alexandre Belloni [mailto:alexandre.bell...@free-electrons.com] > Sent: 2016年6月17日 21:55 > To: Yang, Wenyou > Cc: Rob Herring ; Alan Stern ; > Greg Kroah-Hartman

RE: [PATCH v3 1/2] usb: ohci-at91: Forcibly suspend ports while USB suspend

Hi Aleandre, > -Original Message- > From: Alexandre Belloni [mailto:alexandre.bell...@free-electrons.com] > Sent: 2016年6月17日 21:55 > To: Yang, Wenyou > Cc: Rob Herring ; Alan Stern ; > Greg Kroah-Hartman ; Ferre, Nicolas > ; Pawel Moll ; Mark Brown > ; Ian Campbell ; Kumar > Gala ;

linux-next: manual merge of the tpmdd tree with Linus' tree

Hi Jarkko, Today's linux-next merge of the tpmdd tree got a conflict in: Documentation/devicetree/bindings/vendor-prefixes.txt between commit: 7aa5d38cfb77 ("of: Add Inforce Computing to vendor prefix list") 3eefa7e8cc85 ("dt-bindings: Add vendor prefix for TechNexion") from Linus' tree

linux-next: manual merge of the tpmdd tree with Linus' tree

Hi Jarkko, Today's linux-next merge of the tpmdd tree got a conflict in: Documentation/devicetree/bindings/vendor-prefixes.txt between commit: 7aa5d38cfb77 ("of: Add Inforce Computing to vendor prefix list") 3eefa7e8cc85 ("dt-bindings: Add vendor prefix for TechNexion") from Linus' tree

Re: [PATCHv9-rebased2 01/37] mm, thp: make swapin readahead under down_read of mmap_sem

> > > > @@ -2401,11 +2430,18 @@ static void __collapse_huge_page_swapin(struct > > > > mm_struct *mm, > > > > continue; > > > > swapped_in++; > > > > ret = do_swap_page(mm, vma, _address, pte, pmd, > > > > -

Re: [PATCHv9-rebased2 01/37] mm, thp: make swapin readahead under down_read of mmap_sem

> > > > @@ -2401,11 +2430,18 @@ static void __collapse_huge_page_swapin(struct > > > > mm_struct *mm, > > > > continue; > > > > swapped_in++; > > > > ret = do_swap_page(mm, vma, _address, pte, pmd, > > > > -

Re: [PATCH v2] mmc: dw_mmc: remove UBSAN warning in dw_mci_setup_bus()

Hi SeungWoo, On 06/17/2016 02:16 PM, Seung-Woo Kim wrote: > This patch removes following UBSAN warnings in dw_mci_setup_bus(). > > UBSAN: Undefined behaviour in drivers/mmc/host/dw_mmc.c:1102:14 > shift exponent 250 is too large for 32-bit type 'unsigned int' > Call trace: > []

Re: [PATCH v6 2/2] phy: rockchip-inno-usb2: add a new driver for Rockchip usb2phy

On Sun, Jun 19, 2016 at 6:27 PM, Frank Wang wrote: > Hi Guenter, > > > On 2016/6/17 21:20, Guenter Roeck wrote: >> >> Hi Frank, >> >> On 06/16/2016 11:43 PM, Frank Wang wrote: >>> >>> Hi Guenter, >>> >>> On 2016/6/17 12:59, Guenter Roeck wrote: On 06/16/2016

Re: [PATCH v2] mmc: dw_mmc: remove UBSAN warning in dw_mci_setup_bus()

Hi SeungWoo, On 06/17/2016 02:16 PM, Seung-Woo Kim wrote: > This patch removes following UBSAN warnings in dw_mci_setup_bus(). > > UBSAN: Undefined behaviour in drivers/mmc/host/dw_mmc.c:1102:14 > shift exponent 250 is too large for 32-bit type 'unsigned int' > Call trace: > []

Re: [PATCH v6 2/2] phy: rockchip-inno-usb2: add a new driver for Rockchip usb2phy

On Sun, Jun 19, 2016 at 6:27 PM, Frank Wang wrote: > Hi Guenter, > > > On 2016/6/17 21:20, Guenter Roeck wrote: >> >> Hi Frank, >> >> On 06/16/2016 11:43 PM, Frank Wang wrote: >>> >>> Hi Guenter, >>> >>> On 2016/6/17 12:59, Guenter Roeck wrote: On 06/16/2016 07:09 PM, Frank Wang wrote:

[PATCH 04/28] staging/lustre/llite: lock i_lock before __d_drop()

From: Bruno Faccini There has been several Lustre Client crashes reported by sites running with Lustre versions 2.1/2.5, all showing the same dentry->d_hash->next corrupted pointer cause. This patch fixes a regression that has been introduced since a long time by commit

[PATCH 04/28] staging/lustre/llite: lock i_lock before __d_drop()

From: Bruno Faccini There has been several Lustre Client crashes reported by sites running with Lustre versions 2.1/2.5, all showing the same dentry->d_hash->next corrupted pointer cause. This patch fixes a regression that has been introduced since a long time by commit : (LU-506 kernel: FC15 -

[PATCH 02/28] staging/lustre/llite: correct request handling after ll_lookup_it()

From: "John L. Hammond" In the FIFO cases of ll_atomic_open() and ll_lookup_nd() remove spurious calls to ptlrpc_req_finished(). Explain that these cases are unreachable in practice anyway. Signed-off-by: John L. Hammond Reviewed-on:

[PATCH 00/28] Lustre fixes

These patches represent another round of Lustre fixes and also a few cleanups that some of the fixes were building up upon. Please consider. Alex Zhuravlev (1): staging/lustre: LDLM_DEBUG() shouldn't be passed \n Andriy Skulysh (1): staging/lustre/osc: glimpse lock should match only with

[PATCH 01/28] staging/lustre/llite: allocate and free client cache asynchronously

From: Emoly Liu Since the inflight request holds import refcount as well as export, sometimes obd_disconnect() in client_common_put_super() can't put the last refcount of OSC import (e.g. due to network disconnection), this will cause cl_cache being accessed after free. To

[PATCH 03/28] staging/lustre/llite: Get rid of ll_lock_dcache/ll_unlock_dcache

These are just doing spin_lock/unlock on inode's i_lock, so just do the spinlock directly to make the code more clear Signed-off-by: Oleg Drokin --- drivers/staging/lustre/lustre/llite/dcache.c | 4 ++-- drivers/staging/lustre/lustre/llite/llite_internal.h | 10

[PATCH 02/28] staging/lustre/llite: correct request handling after ll_lookup_it()

From: "John L. Hammond" In the FIFO cases of ll_atomic_open() and ll_lookup_nd() remove spurious calls to ptlrpc_req_finished(). Explain that these cases are unreachable in practice anyway. Signed-off-by: John L. Hammond Reviewed-on: http://review.whamcloud.com/17068 Intel-bug-id:

[PATCH 00/28] Lustre fixes

These patches represent another round of Lustre fixes and also a few cleanups that some of the fixes were building up upon. Please consider. Alex Zhuravlev (1): staging/lustre: LDLM_DEBUG() shouldn't be passed \n Andriy Skulysh (1): staging/lustre/osc: glimpse lock should match only with

[PATCH 01/28] staging/lustre/llite: allocate and free client cache asynchronously

From: Emoly Liu Since the inflight request holds import refcount as well as export, sometimes obd_disconnect() in client_common_put_super() can't put the last refcount of OSC import (e.g. due to network disconnection), this will cause cl_cache being accessed after free. To fix this issue,

[PATCH 03/28] staging/lustre/llite: Get rid of ll_lock_dcache/ll_unlock_dcache

These are just doing spin_lock/unlock on inode's i_lock, so just do the spinlock directly to make the code more clear Signed-off-by: Oleg Drokin --- drivers/staging/lustre/lustre/llite/dcache.c | 4 ++-- drivers/staging/lustre/lustre/llite/llite_internal.h | 10 --

[PATCH v3 7/8] ARM: dts: sun9i: cubieboard4: Add device node for AC100

Signed-off-by: Chen-Yu Tsai --- Changes since v2: none Changes since v1: none --- arch/arm/boot/dts/sun9i-a80-cubieboard4.dts | 21 + 1 file changed, 21 insertions(+) diff --git a/arch/arm/boot/dts/sun9i-a80-cubieboard4.dts

[PATCH v3 8/8] ARM: dts: sun9i: Switch to the AC100 RTC clock outputs for osc32k

The 32.768 kHz clock inside the A80 SoC is fed from an external source, typically the AC100 RTC module. Make the osc32k placeholder a fixed-factor clock so board dts files can specify its source. Signed-off-by: Chen-Yu Tsai --- Changes since v2: none Changes since v1: none ---

[PATCH v3 7/8] ARM: dts: sun9i: cubieboard4: Add device node for AC100

Signed-off-by: Chen-Yu Tsai --- Changes since v2: none Changes since v1: none --- arch/arm/boot/dts/sun9i-a80-cubieboard4.dts | 21 + 1 file changed, 21 insertions(+) diff --git a/arch/arm/boot/dts/sun9i-a80-cubieboard4.dts b/arch/arm/boot/dts/sun9i-a80-cubieboard4.dts

[PATCH v3 8/8] ARM: dts: sun9i: Switch to the AC100 RTC clock outputs for osc32k

The 32.768 kHz clock inside the A80 SoC is fed from an external source, typically the AC100 RTC module. Make the osc32k placeholder a fixed-factor clock so board dts files can specify its source. Signed-off-by: Chen-Yu Tsai --- Changes since v2: none Changes since v1: none ---

[PATCH v3 6/8] ARM: dts: sun9i: a80-optimus: Add device node for AC100

Signed-off-by: Chen-Yu Tsai --- Changes since v2: none Changes since v1: none --- arch/arm/boot/dts/sun9i-a80-optimus.dts | 21 + 1 file changed, 21 insertions(+) diff --git a/arch/arm/boot/dts/sun9i-a80-optimus.dts b/arch/arm/boot/dts/sun9i-a80-optimus.dts

Re: [PATCH v13 01/10] arm64: Add HAVE_REGS_AND_STACK_ACCESS_API feature

on 2016/6/3 11:26, David Long wrote: > From: "David A. Long" > > Add HAVE_REGS_AND_STACK_ACCESS_API feature for arm64, including supporting > functions and defines. > > Signed-off-by: David A. Long > --- > arch/arm64/Kconfig | 1 + >

[PATCH v3 5/8] rtc: ac100: Add clk output support

The AC100's RTC side has 3 clock outputs on external pins, which can provide a clock signal to the SoC or other modules, such as WiFi or GSM modules. Support this with a custom clk driver integrated with the rtc driver. Signed-off-by: Chen-Yu Tsai --- Changes since v2: none

[PATCH] staging: lustre: remove remote client support

From: Fan Yong There are several obsolete sub commands for lfs to work with remote client. We do not support that anymore, and should be deleted along with any kernel code related to remote client. Signed-off-by: Fan Yong Intel-bug-id:

[PATCH v3 6/8] ARM: dts: sun9i: a80-optimus: Add device node for AC100

Signed-off-by: Chen-Yu Tsai --- Changes since v2: none Changes since v1: none --- arch/arm/boot/dts/sun9i-a80-optimus.dts | 21 + 1 file changed, 21 insertions(+) diff --git a/arch/arm/boot/dts/sun9i-a80-optimus.dts b/arch/arm/boot/dts/sun9i-a80-optimus.dts index

Re: [PATCH v13 01/10] arm64: Add HAVE_REGS_AND_STACK_ACCESS_API feature

on 2016/6/3 11:26, David Long wrote: > From: "David A. Long" > > Add HAVE_REGS_AND_STACK_ACCESS_API feature for arm64, including supporting > functions and defines. > > Signed-off-by: David A. Long > --- > arch/arm64/Kconfig | 1 + > arch/arm64/include/asm/ptrace.h | 54

[PATCH v3 5/8] rtc: ac100: Add clk output support

The AC100's RTC side has 3 clock outputs on external pins, which can provide a clock signal to the SoC or other modules, such as WiFi or GSM modules. Support this with a custom clk driver integrated with the rtc driver. Signed-off-by: Chen-Yu Tsai --- Changes since v2: none Changes since v1:

[PATCH] staging: lustre: remove remote client support

From: Fan Yong There are several obsolete sub commands for lfs to work with remote client. We do not support that anymore, and should be deleted along with any kernel code related to remote client. Signed-off-by: Fan Yong Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-6971 Reviewed-on:

[PATCH] fix error: a bin file can truncate itself while running at overlayfs.

From: Aihua Zhang I wrote a testcase to truncate a bin file while it is running at overlayfs. the result as below: Bus error (core dumped) I think it's not appropriate for filesystem, and fixed it by this patch. after the patch, result as below: status:-1 errno:26

[PATCH] fix error: a bin file can truncate itself while running at overlayfs.

From: Aihua Zhang I wrote a testcase to truncate a bin file while it is running at overlayfs. the result as below: Bus error (core dumped) I think it's not appropriate for filesystem, and fixed it by this patch. after the patch, result as below: status:-1 errno:26 ETXTBSY:26 PASS This is

linux-next: manual merge of the block tree with the f2fs tree

Hi Jens, Today's linux-next merge of the block tree got a conflict in: fs/f2fs/data.c between commit: 6d63ed97a1f2 ("f2fs: detect host-managed SMR by feature flag") from the f2fs tree and commit: 04d328defd06 ("f2fs: use bio op accessors") from the block tree. I fixed it up (see

linux-next: manual merge of the block tree with the f2fs tree

Hi Jens, Today's linux-next merge of the block tree got a conflict in: fs/f2fs/data.c between commit: 6d63ed97a1f2 ("f2fs: detect host-managed SMR by feature flag") from the f2fs tree and commit: 04d328defd06 ("f2fs: use bio op accessors") from the block tree. I fixed it up (see

[PATCH v2 20/24] block: Replace CURRENT_TIME with ktime_get_real_ts

CURRENT_TIME is not y2038 safe. The macro will be deleted and all the references to it will be replaced by ktime_get_* apis. struct timespec is also not y2038 safe. Retain timespec for timestamp representation here as ceph uses it internally everywhere. These references will be changed to use

[PATCH v2 20/24] block: Replace CURRENT_TIME with ktime_get_real_ts

CURRENT_TIME is not y2038 safe. The macro will be deleted and all the references to it will be replaced by ktime_get_* apis. struct timespec is also not y2038 safe. Retain timespec for timestamp representation here as ceph uses it internally everywhere. These references will be changed to use

Re: [PATCH v2 2/9] kexec_file: Generalize kexec_add_buffer.

On 06/17/16 at 05:51pm, Thiago Jung Bauermann wrote: > Am Freitag, 17 Juni 2016, 15:35:23 schrieb Dave Young: > > On 06/16/16 at 05:39pm, Thiago Jung Bauermann wrote: > > > Am Donnerstag, 16 Juni 2016, 09:58:53 schrieb Dave Young: > > > > On 06/15/16 at 01:21pm, Thiago Jung Bauermann wrote: > > >

Re: [PATCH v2 2/9] kexec_file: Generalize kexec_add_buffer.

On 06/17/16 at 05:51pm, Thiago Jung Bauermann wrote: > Am Freitag, 17 Juni 2016, 15:35:23 schrieb Dave Young: > > On 06/16/16 at 05:39pm, Thiago Jung Bauermann wrote: > > > Am Donnerstag, 16 Juni 2016, 09:58:53 schrieb Dave Young: > > > > On 06/15/16 at 01:21pm, Thiago Jung Bauermann wrote: > > >

Re: [PATCH v10 0/8] add i2c driver supported for rk3399

Hi Wolfram， 在 2016/6/17 19:56, Wolfram Sang 写道: Applied whole series to for-next, thanks! This was nicely refactored and easy to review, thanks. Also thanks to all reviewers who helped this series. I fixed one checkpatch issue for you, though: WARNING: Statements should start on a tabstop

Re: [PATCH v10 0/8] add i2c driver supported for rk3399

Hi Wolfram， 在 2016/6/17 19:56, Wolfram Sang 写道: Applied whole series to for-next, thanks! This was nicely refactored and easy to review, thanks. Also thanks to all reviewers who helped this series. I fixed one checkpatch issue for you, though: WARNING: Statements should start on a tabstop

Re: [PATCH v10 0/8] add i2c driver supported for rk3399

Hi Wolfram， 在 2016/6/17 19:56, Wolfram Sang 写道: Applied whole series to for-next, thanks! This was nicely refactored and easy to review, thanks. Also thanks to all reviewers who helped this series. I fixed one checkpatch issue for you, though: WARNING: Statements should start on a tabstop

Re: [PATCH v10 0/8] add i2c driver supported for rk3399

Hi Wolfram， 在 2016/6/17 19:56, Wolfram Sang 写道: Applied whole series to for-next, thanks! This was nicely refactored and easy to review, thanks. Also thanks to all reviewers who helped this series. I fixed one checkpatch issue for you, though: WARNING: Statements should start on a tabstop

Re: [PATCH] checkpatch: remove obsolete CONFIG_EXPERIMENTAL checks

On Mon, Jun 20, 2016 at 4:30 AM, Joe Perches wrote: > On Sun, 2016-06-19 at 23:29 +0300, Ruslan Bilovol wrote: >> Config EXPERIMENTAL has been removed from kernel in 2013 >> (see 3d374d0: "final removal of CONFIG_EXPERIMENTAL"), >> there is no any reason to do these checks now.

Re: [PATCH] checkpatch: remove obsolete CONFIG_EXPERIMENTAL checks

On Mon, Jun 20, 2016 at 4:30 AM, Joe Perches wrote: > On Sun, 2016-06-19 at 23:29 +0300, Ruslan Bilovol wrote: >> Config EXPERIMENTAL has been removed from kernel in 2013 >> (see 3d374d0: "final removal of CONFIG_EXPERIMENTAL"), >> there is no any reason to do these checks now. > > Not quite

[PATCH 28/28] staging/lustre/osc: glimpse lock should match only with granted locks

From: Andriy Skulysh A deadlock is possible during ccc_prep_size()->ldlm_lock_match() vs cl_io_lock() which is waiting for a matched lock and conflicts with already taken lock before ccc_prep_size(). It is better to send an additional lock request to avoid deadlock.

[PATCH 28/28] staging/lustre/osc: glimpse lock should match only with granted locks

From: Andriy Skulysh A deadlock is possible during ccc_prep_size()->ldlm_lock_match() vs cl_io_lock() which is waiting for a matched lock and conflicts with already taken lock before ccc_prep_size(). It is better to send an additional lock request to avoid deadlock. Seagate-bug-id: MRP-3312

[PATCH 23/28] staging/lustre/llite: Restore proper opencache operations

From: Oleg Drokin Mark dentries that came to us via NFS in a special way so that we can tell them apart during open and activate open cache (we really don't want to do open/close RPC for every NFS IO). This became needed since dentry revlidate no longer reimplements any

[PATCH 22/28] staging/lustre/llite: don't panic when fid is insane

From: Sergey Cheremencev LASSERT should never be done on data that is received to over the network. Return EINVAL when server returns invalid fid despite of it_status == 0. Signed-off-by: Sergey Cheremencev Seagate-bug-id:

[PATCH 20/28] staging/lustre/mdc: Zero atime in close RPC

From: Niu Yawei While atime on close is supposed to only increase, there's a bug in some older server versions where atime from a client is taken no matter the value that allows a stale client atime to overwrite a correct value. Update atime in close rpc to 0 to help such

[PATCH 15/28] staging/lustre/llite: flatten struct lookup_intent

From: "John L. Hammond" Replace the union in struct lookup_intent with the members of struct lustre_indent_data. Remove the then unused struct lustre_intent_data. Signed-off-by: John L. Hammond Reviewed-on: http://review.whamcloud.com/17069

[PATCH 23/28] staging/lustre/llite: Restore proper opencache operations

From: Oleg Drokin Mark dentries that came to us via NFS in a special way so that we can tell them apart during open and activate open cache (we really don't want to do open/close RPC for every NFS IO). This became needed since dentry revlidate no longer reimplements any RPCs for lookup, and as

[PATCH 22/28] staging/lustre/llite: don't panic when fid is insane

From: Sergey Cheremencev LASSERT should never be done on data that is received to over the network. Return EINVAL when server returns invalid fid despite of it_status == 0. Signed-off-by: Sergey Cheremencev Seagate-bug-id: MRP-3073 Reviewed-on: http://review.whamcloud.com/17985 Intel-bug-id:

[PATCH 20/28] staging/lustre/mdc: Zero atime in close RPC

From: Niu Yawei While atime on close is supposed to only increase, there's a bug in some older server versions where atime from a client is taken no matter the value that allows a stale client atime to overwrite a correct value. Update atime in close rpc to 0 to help such servers out.

[PATCH 15/28] staging/lustre/llite: flatten struct lookup_intent

From: "John L. Hammond" Replace the union in struct lookup_intent with the members of struct lustre_indent_data. Remove the then unused struct lustre_intent_data. Signed-off-by: John L. Hammond Reviewed-on: http://review.whamcloud.com/17069 Intel-bug-id:

[PATCH 27/28] staging/lustre: Add documentation for unstable_stats in sysfs

commit ac5b14810952 ("staging: lustre: osc: Track and limit "unstable" pages") added a new sysfs variable, but corresponding bit of documentation was not forgotten. Signed-off-by: Oleg Drokin --- drivers/staging/lustre/sysfs-fs-lustre | 8 1 file changed, 8

[PATCH 27/28] staging/lustre: Add documentation for unstable_stats in sysfs

commit ac5b14810952 ("staging: lustre: osc: Track and limit "unstable" pages") added a new sysfs variable, but corresponding bit of documentation was not forgotten. Signed-off-by: Oleg Drokin --- drivers/staging/lustre/sysfs-fs-lustre | 8 1 file changed, 8 insertions(+) diff --git

[PATCH 26/28] staging/lustre/osc: fix signed one bit field

From: Dmitry Eremin Bit field 'oi_lockless' and 'oi_is_active' has one bit and is signed which is confusing. Signed-off-by: Dmitry Eremin Reviewed-on: http://review.whamcloud.com/19196 Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7258

[PATCH 26/28] staging/lustre/osc: fix signed one bit field

From: Dmitry Eremin Bit field 'oi_lockless' and 'oi_is_active' has one bit and is signed which is confusing. Signed-off-by: Dmitry Eremin Reviewed-on: http://review.whamcloud.com/19196 Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7258 Reviewed-by: Andreas Dilger Reviewed-by: James

[PATCH 17/28] staging/lustre/llite: change it_data to it_request

From: "John L. Hammond" Change the void *it_data member of struct lookup_intent to struct ptlrpc_request *it_request. Signed-off-by: John L. Hammond Reviewed-on: http://review.whamcloud.com/17070 Intel-bug-id:

[PATCH 19/28] staging/lustre/llite: ensure obd is effective in onu_upcall

From: Yang Sheng The watched obd device may still not setup while onu_upcall invoked. So we need verify it in cl_ocd_update. Signed-off-by: Yang Sheng Reviewed-on: http://review.whamcloud.com/19597 Intel-bug-id:

[PATCH 17/28] staging/lustre/llite: change it_data to it_request

From: "John L. Hammond" Change the void *it_data member of struct lookup_intent to struct ptlrpc_request *it_request. Signed-off-by: John L. Hammond Reviewed-on: http://review.whamcloud.com/17070 Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7403 Reviewed-by: Andreas Dilger Reviewed-by:

[PATCH 19/28] staging/lustre/llite: ensure obd is effective in onu_upcall

From: Yang Sheng The watched obd device may still not setup while onu_upcall invoked. So we need verify it in cl_ocd_update. Signed-off-by: Yang Sheng Reviewed-on: http://review.whamcloud.com/19597 Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8027 Reviewed-by: Niu Yawei Reviewed-by:

[PATCH 18/28] staging/lustre/ldlm: const qualify struct lustre_handle * params

From: "John L. Hammond" Add a const qualifier to several struct lustre_handle * parameters in the LDLM interface. Signed-off-by: John L. Hammond Reviewed-on: http://review.whamcloud.com/17071 Intel-bug-id:

[PATCH 18/28] staging/lustre/ldlm: const qualify struct lustre_handle * params

From: "John L. Hammond" Add a const qualifier to several struct lustre_handle * parameters in the LDLM interface. Signed-off-by: John L. Hammond Reviewed-on: http://review.whamcloud.com/17071 Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7403 Reviewed-by: Andreas Dilger Reviewed-by:

[PATCH 21/28] staging/lustre/o2ib: Don't access NULL NI on failure path

From: Doug Oucharek In kiblnd_passive_connect(), if we are failing the connection attempt because we cannot find a valid NI (we have a NULL NI), we were coring after the "goto fail" because the failure path was assuming non-NULL NI. This patch ensures we don't

[PATCH 24/28] staging/lustre/llite: ll_revalidate_dentry update

From: Oleg Drokin There are a couple of cases in ll_revalidate_dentry() where we are pretty sure the dentry is valid, so check for them early and save more expensive checks for later. Signed-off-by: Oleg Drokin ---

[PATCH 25/28] staging/lustre/llite: IOC_MDC_GETFILEINFO returns the wrong ino

From: akam kumar bharathi req_capsule_server_get() through __req_capsule_get in ll_dir_ioctl() returns a pointer to a PTLRPC request or reply buffer, which is assigned to struct mdt_body. If the command is IOC_MDS_GETFILEINFO then the inode "st.st_ino" should be assigned

[PATCH 14/28] staging/lustre: Add newline to LU_OBJECT_DEBUG() message

From: Bob Glossman LU_OBJECT_DEBUG expects non \n terminated message from the caller, so it should add it's own to keep debug logger happy. Signed-off-by: Bob Glossman Reviewed-on: http://review.whamcloud.com/19960 Intel-bug-id:

[PATCH 21/28] staging/lustre/o2ib: Don't access NULL NI on failure path

From: Doug Oucharek In kiblnd_passive_connect(), if we are failing the connection attempt because we cannot find a valid NI (we have a NULL NI), we were coring after the "goto fail" because the failure path was assuming non-NULL NI. This patch ensures we don't dereference a NULL NI on that

[PATCH 24/28] staging/lustre/llite: ll_revalidate_dentry update

From: Oleg Drokin There are a couple of cases in ll_revalidate_dentry() where we are pretty sure the dentry is valid, so check for them early and save more expensive checks for later. Signed-off-by: Oleg Drokin --- drivers/staging/lustre/lustre/llite/dcache.c | 11 +++ 1 file changed,

[PATCH 25/28] staging/lustre/llite: IOC_MDC_GETFILEINFO returns the wrong ino

From: akam kumar bharathi req_capsule_server_get() through __req_capsule_get in ll_dir_ioctl() returns a pointer to a PTLRPC request or reply buffer, which is assigned to struct mdt_body. If the command is IOC_MDS_GETFILEINFO then the inode "st.st_ino" should be assigned from one extracted

[PATCH 14/28] staging/lustre: Add newline to LU_OBJECT_DEBUG() message

From: Bob Glossman LU_OBJECT_DEBUG expects non \n terminated message from the caller, so it should add it's own to keep debug logger happy. Signed-off-by: Bob Glossman Reviewed-on: http://review.whamcloud.com/19960 Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8094 Reviewed-by: Andreas

[PATCH 09/28] staging/lustre/ptlrpc: Early Reply vs Reply MDunlink

From: Vitaly Fertman A race between unregister_reply & early reply. When buffers are busy for the early transfer, they cannon be unlinked by unregister_reply, so the RPC gets into UNREGISTERING state. The coming reply_in_callback for the early RPC already has unlinked

[PATCH 09/28] staging/lustre/ptlrpc: Early Reply vs Reply MDunlink

From: Vitaly Fertman A race between unregister_reply & early reply. When buffers are busy for the early transfer, they cannon be unlinked by unregister_reply, so the RPC gets into UNREGISTERING state. The coming reply_in_callback for the early RPC already has unlinked flag set due to previous

<    1   2   3   4   5   6   >