[PATCH v2 2/2] MAINTAINERS: add entry for mediatek usb3 DRD IP driver

Add myself as maintainer of MediaTek USB3 DRD IP driver Signed-off-by: Chunfeng Yun --- MAINTAINERS |8 1 file changed, 8 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 205d397..0cf5e31 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -8472,6 +8472,14 @@ M: Sean Wang

[PATCH v2 1/2] usb: mtu3: add a vbus debugfs interface

Provides a new vbus debugfs interface used to turn on/off vbus regulator, it also can be used to get/put reference count of vbus, due to sometimes we need keep it alive when manually switch mtu3 to device mode. Signed-off-by: Chunfeng Yun --- drivers/usb/mtu3/mtu3_dr.c | 58

Re: [PATCH 2/2] arm64: Define PAGE_OFFSET using GENMASK_ULL

Hi Matthias, [auto build test ERROR on arm64/for-next/core] [also build test ERROR on v4.13-rc3 next-20170803] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Matthias-Kaehlcke/bitops-Avoid

Re: [PATCH 2/2] arm64: Define PAGE_OFFSET using GENMASK_ULL

Hi Matthias, [auto build test ERROR on arm64/for-next/core] [also build test ERROR on v4.13-rc3 next-20170803] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Matthias-Kaehlcke/bitops-Avoid

Re: [linux-sunxi] [PATCH] pinctrl: sunxi: fix V3s pinctrl driver IRQ bank base

On Tue, Aug 1, 2017 at 10:54 PM, Icenowy Zheng wrote: > The V3s pin controller doesn't have the bank 0 (starts at address > 0x200), which is like A33. However, this is not workarounded when was not worked around "Work around" is a verb

Re: [linux-sunxi] [PATCH] pinctrl: sunxi: fix V3s pinctrl driver IRQ bank base

On Tue, Aug 1, 2017 at 10:54 PM, Icenowy Zheng wrote: > The V3s pin controller doesn't have the bank 0 (starts at address > 0x200), which is like A33. However, this is not workarounded when was not worked around "Work around" is a verb phrase.

[PATCH] pinctrl: move const qualifier before struct

Update subsystem wide for consistency. Signed-off-by: Masahiro Yamada --- drivers/pinctrl/berlin/berlin.c | 4 ++-- drivers/pinctrl/core.c | 14 +++--- drivers/pinctrl/core.h | 6 +++--- drivers/pinctrl/pinconf.c | 12

[PATCH] pinctrl: move const qualifier before struct

Update subsystem wide for consistency. Signed-off-by: Masahiro Yamada --- drivers/pinctrl/berlin/berlin.c | 4 ++-- drivers/pinctrl/core.c | 14 +++--- drivers/pinctrl/core.h | 6 +++--- drivers/pinctrl/pinconf.c | 12 ++-- drivers/pinctrl/pinconf.h

Re: [PATCH v3 00/10] ARM: sun8i: a83t: Add support for MMC controllers

On Thu, Aug 3, 2017 at 8:02 PM, Ulf Hansson wrote: > On 3 August 2017 at 13:25, Chen-Yu Tsai wrote: >> On Thu, Aug 3, 2017 at 7:19 PM, Ulf Hansson wrote: >>> On 26 July 2017 at 21:45, Maxime Ripard >>>

Re: [PATCH v3 00/10] ARM: sun8i: a83t: Add support for MMC controllers

On Thu, Aug 3, 2017 at 8:02 PM, Ulf Hansson wrote: > On 3 August 2017 at 13:25, Chen-Yu Tsai wrote: >> On Thu, Aug 3, 2017 at 7:19 PM, Ulf Hansson wrote: >>> On 26 July 2017 at 21:45, Maxime Ripard >>> wrote: On Wed, Jul 26, 2017 at 10:09:41PM +0800, Chen-Yu Tsai wrote: > On Mon, Jul

Re: [PATCH v4 3/3] power: wm831x_power: Support USB charger current limit management

On 4 August 2017 at 03:16, Rob Herring wrote: > On Thu, Jul 27, 2017 at 01:14:38PM +0800, Baolin Wang wrote: >> Integrate with the newly added USB charger interface to limit the current >> we draw from the USB input based on the input device configuration >> identified by the USB

Re: [PATCH v4 3/3] power: wm831x_power: Support USB charger current limit management

On 4 August 2017 at 03:16, Rob Herring wrote: > On Thu, Jul 27, 2017 at 01:14:38PM +0800, Baolin Wang wrote: >> Integrate with the newly added USB charger interface to limit the current >> we draw from the USB input based on the input device configuration >> identified by the USB stack, allowing

Re: [PATCH 1/2] usb: mtu3: add a vbus debugfs interface

On Thu, 2017-08-03 at 09:01 -0700, Greg Kroah-Hartman wrote: > On Thu, Aug 03, 2017 at 09:00:57AM -0700, Greg Kroah-Hartman wrote: > > On Thu, Aug 03, 2017 at 04:37:18PM +0800, Chunfeng Yun wrote: > > > +static ssize_t ssusb_vbus_write(struct file *file, > > > + const char __user *ubuf, size_t

Re: [PATCH 1/2] usb: mtu3: add a vbus debugfs interface

On Thu, 2017-08-03 at 09:01 -0700, Greg Kroah-Hartman wrote: > On Thu, Aug 03, 2017 at 09:00:57AM -0700, Greg Kroah-Hartman wrote: > > On Thu, Aug 03, 2017 at 04:37:18PM +0800, Chunfeng Yun wrote: > > > +static ssize_t ssusb_vbus_write(struct file *file, > > > + const char __user *ubuf, size_t

Re: [PATCH 3/3] IPI: Avoid to use 2 cache lines for one call_single_data

"Huang, Ying" writes: > Peter Zijlstra writes: > [snip] >> diff --git a/include/linux/smp.h b/include/linux/smp.h >> index 68123c1fe549..8d817cb80a38 100644 >> --- a/include/linux/smp.h >> +++ b/include/linux/smp.h >> @@ -14,13 +14,16 @@ >> #include

Re: [PATCH 3/3] IPI: Avoid to use 2 cache lines for one call_single_data

"Huang, Ying" writes: > Peter Zijlstra writes: > [snip] >> diff --git a/include/linux/smp.h b/include/linux/smp.h >> index 68123c1fe549..8d817cb80a38 100644 >> --- a/include/linux/smp.h >> +++ b/include/linux/smp.h >> @@ -14,13 +14,16 @@ >> #include >> >> typedef void

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

Hi all, Today's linux-next merge of the wireless-drivers-next tree got a conflict in: drivers/net/wireless/intel/iwlwifi/mvm/ops.c between commit: bf8b286f86fc ("iwlwifi: mvm: defer setting IWL_MVM_STATUS_IN_HW_RESTART") from Linus' tree and commit: 7174beb60c53 ("iwlwifi: refactor

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

Hi all, Today's linux-next merge of the wireless-drivers-next tree got a conflict in: drivers/net/wireless/intel/iwlwifi/mvm/ops.c between commit: bf8b286f86fc ("iwlwifi: mvm: defer setting IWL_MVM_STATUS_IN_HW_RESTART") from Linus' tree and commit: 7174beb60c53 ("iwlwifi: refactor

Re: [PATCH] x86/boot/KASLR: Extend movable_node option for KASLR

On Fri, Aug 04, 2017 at 09:37:14AM +0800, Dou Liyang wrote: >Hi Chao,Baoquan > >At 08/04/2017 07:49 AM, Baoquan He wrote: >> On 08/03/17 at 08:24pm, Chao Fan wrote: >> > It's almost another "mem=". >> > >No, it is different. > >See Documentation/kernel-parameters: > >"mem=" will force usage of a

Re: [PATCH] x86/boot/KASLR: Extend movable_node option for KASLR

On Fri, Aug 04, 2017 at 09:37:14AM +0800, Dou Liyang wrote: >Hi Chao,Baoquan > >At 08/04/2017 07:49 AM, Baoquan He wrote: >> On 08/03/17 at 08:24pm, Chao Fan wrote: >> > It's almost another "mem=". >> > >No, it is different. > >See Documentation/kernel-parameters: > >"mem=" will force usage of a

Re: [PATCH] x86/boot/KASLR: Extend movable_node option for KASLR

On 08/04/17 at 09:37am, Dou Liyang wrote: > Hi Chao,Baoquan > > At 08/04/2017 07:49 AM, Baoquan He wrote: > > On 08/03/17 at 08:24pm, Chao Fan wrote: > > > It's almost another "mem=". > > > > No, it is different. > > See Documentation/kernel-parameters: > > "mem=" will force usage of a

Re: [PATCH] x86/boot/KASLR: Extend movable_node option for KASLR

On 08/04/17 at 09:37am, Dou Liyang wrote: > Hi Chao,Baoquan > > At 08/04/2017 07:49 AM, Baoquan He wrote: > > On 08/03/17 at 08:24pm, Chao Fan wrote: > > > It's almost another "mem=". > > > > No, it is different. > > See Documentation/kernel-parameters: > > "mem=" will force usage of a

[PATCH] f2fs: use printk_ratelimited for f2fs_msg

This patch reduces contention of printks. Signed-off-by: Jaegeuk Kim --- fs/f2fs/super.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c index 4ab6dc31a61b..ca340d84f8c2 100644 --- a/fs/f2fs/super.c +++ b/fs/f2fs/super.c

[PATCH] f2fs: use printk_ratelimited for f2fs_msg

This patch reduces contention of printks. Signed-off-by: Jaegeuk Kim --- fs/f2fs/super.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c index 4ab6dc31a61b..ca340d84f8c2 100644 --- a/fs/f2fs/super.c +++ b/fs/f2fs/super.c @@ -159,7 +159,7 @@

Re: [PATCH] f2fs: provide f2fs_balance_fs to __write_data_page for dentry pages

On 08/02, Yunlong Song wrote: > Hi Jay, > The case is like this: > write_checkpoint: normal dentry > page writeback of inodeB： > -block_operations -f2fs_write_data_pages > -SBI_BLOCK_OPS is set -f2fs_write_cache_pages >

Re: [PATCH] f2fs: provide f2fs_balance_fs to __write_data_page for dentry pages

On 08/02, Yunlong Song wrote: > Hi Jay, > The case is like this: > write_checkpoint: normal dentry > page writeback of inodeB： > -block_operations -f2fs_write_data_pages > -SBI_BLOCK_OPS is set -f2fs_write_cache_pages >

[PATCH] cpufreq: dt: Add rk3328 compatible to use generic cpufreq driver

This patch adds the rk3328 compatible string for supporting the generic cpufreq driver on RK3328. Signed-off-by: Finley Xiao --- drivers/cpufreq/cpufreq-dt-platdev.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c

[PATCH] cpufreq: dt: Add rk3328 compatible to use generic cpufreq driver

This patch adds the rk3328 compatible string for supporting the generic cpufreq driver on RK3328. Signed-off-by: Finley Xiao --- drivers/cpufreq/cpufreq-dt-platdev.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-dt-platdev.c

Re: [PATCH] ARC: clk: introduce HSDKv1 pll driver

On 07/14, Eugeniy Paltsev wrote: > HSDKv1 boards manages it's clocks using various PLLs. These PLL has same s/it's/its/ s/has/have/ > dividers and corresponding control registers mapped to different addresses. > So we add one common driver for such PLLs. > > Each PLL on HSDK board consist of

Re: [PATCH] ARC: clk: introduce HSDKv1 pll driver

On 07/14, Eugeniy Paltsev wrote: > HSDKv1 boards manages it's clocks using various PLLs. These PLL has same s/it's/its/ s/has/have/ > dividers and corresponding control registers mapped to different addresses. > So we add one common driver for such PLLs. > > Each PLL on HSDK board consist of

Re: [PATCH] x86/boot/KASLR: Extend movable_node option for KASLR

Hi Kees, At 08/04/2017 06:40 AM, Kees Cook wrote: On Thu, Aug 3, 2017 at 5:17 AM, Dou Liyang wrote: movable_node is a boot-time switch to make hot-pluggable memory NUMA nodes to be movable. This option is based on an assumption that any node which the kernel resides

Re: [PATCH] x86/boot/KASLR: Extend movable_node option for KASLR

Hi Kees, At 08/04/2017 06:40 AM, Kees Cook wrote: On Thu, Aug 3, 2017 at 5:17 AM, Dou Liyang wrote: movable_node is a boot-time switch to make hot-pluggable memory NUMA nodes to be movable. This option is based on an assumption that any node which the kernel resides in is defined as

Re: [PATCH] f2fs-tools: support inode checksum

Hi Chao, It seems three is missing case when verifying the checksum, if the page is got from cache with some updates. We need to verify it when actually reading the node block. Let me modify your patch like this. Is that okay for you? Thanks, --- fs/f2fs/f2fs.h| 3 ++- fs/f2fs/inode.c

Re: [PATCH] f2fs-tools: support inode checksum

Hi Chao, It seems three is missing case when verifying the checksum, if the page is got from cache with some updates. We need to verify it when actually reading the node block. Let me modify your patch like this. Is that okay for you? Thanks, --- fs/f2fs/f2fs.h| 3 ++- fs/f2fs/inode.c

Re: [PATCH] x86/boot/KASLR: Extend movable_node option for KASLR

Hi Chao,Baoquan At 08/04/2017 07:49 AM, Baoquan He wrote: On 08/03/17 at 08:24pm, Chao Fan wrote: It's almost another "mem=". No, it is different. See Documentation/kernel-parameters: "mem=" will force usage of a specific amount of memory and kernel will not see the whole system memory.

Re: [PATCH] x86/boot/KASLR: Extend movable_node option for KASLR

Hi Chao,Baoquan At 08/04/2017 07:49 AM, Baoquan He wrote: On 08/03/17 at 08:24pm, Chao Fan wrote: It's almost another "mem=". No, it is different. See Documentation/kernel-parameters: "mem=" will force usage of a specific amount of memory and kernel will not see the whole system memory.

[PATCH v3 3/4] dt-bindings: mediatek: add descriptions for larbid

From: Honghui Zhang This patch add larbid descritptions for mediatek's gen1 smi larb hardware. Acked-by: Rob Herring Signed-off-by: Honghui Zhang --- .../bindings/memory-controllers/mediatek,smi-larb.txt | 15

[PATCH v3 3/4] dt-bindings: mediatek: add descriptions for larbid

From: Honghui Zhang This patch add larbid descritptions for mediatek's gen1 smi larb hardware. Acked-by: Rob Herring Signed-off-by: Honghui Zhang --- .../bindings/memory-controllers/mediatek,smi-larb.txt | 15 +++ 1 file changed, 15 insertions(+) diff --git

[PATCH v3 1/4] memory: mtk-smi: Use of_device_get_match_data helper

From: Honghui Zhang Replace custom code with generic helper to retrieve driver data. Signed-off-by: Honghui Zhang --- drivers/memory/mtk-smi.c | 14 ++ 1 file changed, 2 insertions(+), 12 deletions(-) diff --git

[PATCH v3 4/4] arm: dts: mediatek: add larbid property for larb

From: Honghui Zhang Add mediatek's hardware id information for smi larb. Signed-off-by: Honghui Zhang --- arch/arm/boot/dts/mt2701.dtsi | 3 +++ 1 file changed, 3 insertions(+) diff --git a/arch/arm/boot/dts/mt2701.dtsi

[PATCH v3 4/4] arm: dts: mediatek: add larbid property for larb

From: Honghui Zhang Add mediatek's hardware id information for smi larb. Signed-off-by: Honghui Zhang --- arch/arm/boot/dts/mt2701.dtsi | 3 +++ 1 file changed, 3 insertions(+) diff --git a/arch/arm/boot/dts/mt2701.dtsi b/arch/arm/boot/dts/mt2701.dtsi index f1efdc6..d95bfe0 100644 ---

[PATCH v3 1/4] memory: mtk-smi: Use of_device_get_match_data helper

From: Honghui Zhang Replace custom code with generic helper to retrieve driver data. Signed-off-by: Honghui Zhang --- drivers/memory/mtk-smi.c | 14 ++ 1 file changed, 2 insertions(+), 12 deletions(-) diff --git a/drivers/memory/mtk-smi.c b/drivers/memory/mtk-smi.c index

[PATCH v3 0/4] Add larbid init routine for mediatek's gen1 smi larb driver

From: Honghui Zhang Mediatek's gen1 smi need the hardware larb-id to identify the offset for the register which controls whether enable iommu for this larb. In the commit 3c8f4ad85c4b ("memory/mediatek: add support for mt2701"), the larbid was used without properly

[PATCH v3 0/4] Add larbid init routine for mediatek's gen1 smi larb driver

From: Honghui Zhang Mediatek's gen1 smi need the hardware larb-id to identify the offset for the register which controls whether enable iommu for this larb. In the commit 3c8f4ad85c4b ("memory/mediatek: add support for mt2701"), the larbid was used without properly initialized. This patchset

[PATCH v3 2/4] memory: mtk-smi: add larbid handle routine

From: Honghui Zhang In the commit 3c8f4ad85c4b ("memory/mediatek: add support for mt2701"), the larb->larbid was added but not initialized. Mediatek's gen1 smi need this hardware larbid information to get the register offset which controls whether enable iommu for

[PATCH v3 2/4] memory: mtk-smi: add larbid handle routine

From: Honghui Zhang In the commit 3c8f4ad85c4b ("memory/mediatek: add support for mt2701"), the larb->larbid was added but not initialized. Mediatek's gen1 smi need this hardware larbid information to get the register offset which controls whether enable iommu for this larb. This patch add the

Re: linux-next: Signed-off-by missing for commit in the crypto tree

On Fri, Aug 04, 2017 at 07:50:22AM +1000, Stephen Rothwell wrote: > Hi all, > > Commit > > 9577212cc0e2 ("crypto: hash - add crypto_(un)register_ahashes()") > > is missing a Signed-off-by from its author. OK, I've backed out the patches in question. Please resubmit with a sign-off. Thanks!

Re: linux-next: Signed-off-by missing for commit in the crypto tree

On Fri, Aug 04, 2017 at 07:50:22AM +1000, Stephen Rothwell wrote: > Hi all, > > Commit > > 9577212cc0e2 ("crypto: hash - add crypto_(un)register_ahashes()") > > is missing a Signed-off-by from its author. OK, I've backed out the patches in question. Please resubmit with a sign-off. Thanks!

Re: [PATCH 3/3] IPI: Avoid to use 2 cache lines for one call_single_data

Peter Zijlstra writes: [snip] > diff --git a/include/linux/smp.h b/include/linux/smp.h > index 68123c1fe549..8d817cb80a38 100644 > --- a/include/linux/smp.h > +++ b/include/linux/smp.h > @@ -14,13 +14,16 @@ > #include > > typedef void (*smp_call_func_t)(void *info); >

Re: [PATCH 3/3] IPI: Avoid to use 2 cache lines for one call_single_data

Peter Zijlstra writes: [snip] > diff --git a/include/linux/smp.h b/include/linux/smp.h > index 68123c1fe549..8d817cb80a38 100644 > --- a/include/linux/smp.h > +++ b/include/linux/smp.h > @@ -14,13 +14,16 @@ > #include > > typedef void (*smp_call_func_t)(void *info); > -struct

Re: [PATCH v2] KVM: nVMX: Fix attempting to emulate "Acknowledge interrupt on exit" when there is no interrupt which L1 requires to inject to L2

2017-08-03 21:46 GMT+08:00 Radim Krčmář : > 2017-07-31 19:25-0700, Wanpeng Li: >> From: Wanpeng Li >> >> [ cut here ] >> WARNING: CPU: 5 PID: 2288 at arch/x86/kvm/vmx.c:11124 >> nested_vmx_vmexit+0xd64/0xd70 [kvm_intel] >>

Re: [PATCH v2] KVM: nVMX: Fix attempting to emulate "Acknowledge interrupt on exit" when there is no interrupt which L1 requires to inject to L2

2017-08-03 21:46 GMT+08:00 Radim Krčmář : > 2017-07-31 19:25-0700, Wanpeng Li: >> From: Wanpeng Li >> >> [ cut here ] >> WARNING: CPU: 5 PID: 2288 at arch/x86/kvm/vmx.c:11124 >> nested_vmx_vmexit+0xd64/0xd70 [kvm_intel] >> CPU: 5 PID: 2288 Comm: qemu-system-x86 Not

[PATCH v3] printk: Add boottime and real timestamps

printk.time=1/CONFIG_PRINTK_TIME=1 adds a unmodified local hardware clock timestamp to printk messages. The local hardware clock loses time each day making it difficult to determine exactly when an issue has occurred in the kernel log, and making it difficult to determine how kernel and hardware

[PATCH v3] printk: Add boottime and real timestamps

printk.time=1/CONFIG_PRINTK_TIME=1 adds a unmodified local hardware clock timestamp to printk messages. The local hardware clock loses time each day making it difficult to determine exactly when an issue has occurred in the kernel log, and making it difficult to determine how kernel and hardware

Re: [PATCH 0/6] Support for LEGO MINDSTORMS EV3 LCD display

On 08/03/2017 08:08 PM, David Lechner wrote: On 08/03/2017 03:11 PM, Noralf Trønnes wrote: Den 03.08.2017 19.11, skrev Andy Shevchenko: On Thu, Aug 3, 2017 at 8:09 PM, Andy Shevchenko wrote: On Thu, Aug 3, 2017 at 6:18 PM, David Lechner

Re: [PATCH 0/6] Support for LEGO MINDSTORMS EV3 LCD display

On 08/03/2017 08:08 PM, David Lechner wrote: On 08/03/2017 03:11 PM, Noralf Trønnes wrote: Den 03.08.2017 19.11, skrev Andy Shevchenko: On Thu, Aug 3, 2017 at 8:09 PM, Andy Shevchenko wrote: On Thu, Aug 3, 2017 at 6:18 PM, David Lechner wrote: The particular display I have is this one:

Re: [PATCH v2] zram: Rework copy of compressor name in comp_algorithm_store()

On Thu, Aug 03, 2017 at 09:33:50AM -0700, Matthias Kaehlcke wrote: > comp_algorithm_store() passes the size of the source buffer to strlcpy() > instead of the destination buffer size. Make it explicit that the two > buffers have the same size and use strcpy() instead of strlcpy(). > The latter can

Re: [PATCH v2] zram: Rework copy of compressor name in comp_algorithm_store()

On Thu, Aug 03, 2017 at 09:33:50AM -0700, Matthias Kaehlcke wrote: > comp_algorithm_store() passes the size of the source buffer to strlcpy() > instead of the destination buffer size. Make it explicit that the two > buffers have the same size and use strcpy() instead of strlcpy(). > The latter can

Re: [PATCH 0/6] Support for LEGO MINDSTORMS EV3 LCD display

On 08/03/2017 03:11 PM, Noralf Trønnes wrote: Den 03.08.2017 19.11, skrev Andy Shevchenko: On Thu, Aug 3, 2017 at 8:09 PM, Andy Shevchenko wrote: On Thu, Aug 3, 2017 at 6:18 PM, David Lechner wrote: The particular display I have is this

Re: [PATCH 0/6] Support for LEGO MINDSTORMS EV3 LCD display

On 08/03/2017 03:11 PM, Noralf Trønnes wrote: Den 03.08.2017 19.11, skrev Andy Shevchenko: On Thu, Aug 3, 2017 at 8:09 PM, Andy Shevchenko wrote: On Thu, Aug 3, 2017 at 6:18 PM, David Lechner wrote: The particular display I have is this one:

Re: [PATCH v2] zram: Rework copy of compressor name in comp_algorithm_store()

On (08/03/17 09:33), Matthias Kaehlcke wrote: > comp_algorithm_store() passes the size of the source buffer to strlcpy() > instead of the destination buffer size. Make it explicit that the two > buffers have the same size and use strcpy() instead of strlcpy(). > The latter can be done safely since

Re: [PATCH v2] zram: Rework copy of compressor name in comp_algorithm_store()

On (08/03/17 09:33), Matthias Kaehlcke wrote: > comp_algorithm_store() passes the size of the source buffer to strlcpy() > instead of the destination buffer size. Make it explicit that the two > buffers have the same size and use strcpy() instead of strlcpy(). > The latter can be done safely since

Re: linux-next: manual merge of the tty tree with the tty.current tree

On Wed, Aug 02, 2017 at 02:26:28PM +1000, Stephen Rothwell wrote: > Hi Greg, > > Today's linux-next merge of the tty tree got a conflict in: > > drivers/tty/serial/8250/8250_core.c > > between commit: > > 9527b82ae3af ("Revert "serial: Delete dead code for CIR serial ports"") > > from the

Re: linux-next: manual merge of the tty tree with the tty.current tree

On Wed, Aug 02, 2017 at 02:26:28PM +1000, Stephen Rothwell wrote: > Hi Greg, > > Today's linux-next merge of the tty tree got a conflict in: > > drivers/tty/serial/8250/8250_core.c > > between commit: > > 9527b82ae3af ("Revert "serial: Delete dead code for CIR serial ports"") > > from the

Re: [PATCH 5/6] drm/rockchip: vop: report error when check resource error

Hi mark, 在 2017/7/31 17:49, Mark Yao 写道: The user would be confused while facing a error commit without any error report. Signed-off-by: Mark Yao --- drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git

Re: [PATCH 5/6] drm/rockchip: vop: report error when check resource error

Hi mark, 在 2017/7/31 17:49, Mark Yao 写道: The user would be confused while facing a error commit without any error report. Signed-off-by: Mark Yao --- drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git

Re: [PATCH 0/3] remove rw_page() from brd, pmem and btt

On Thu, Aug 03, 2017 at 10:05:44AM +0200, Christoph Hellwig wrote: > FYI, for the read side we should use the on-stack bio unconditionally, > as it will always be a win (or not show up at all). Think about readahead. Unconditional on-stack bio to read around pages with faulted address will cause

Re: [PATCH 0/3] remove rw_page() from brd, pmem and btt

On Thu, Aug 03, 2017 at 10:05:44AM +0200, Christoph Hellwig wrote: > FYI, for the read side we should use the on-stack bio unconditionally, > as it will always be a win (or not show up at all). Think about readahead. Unconditional on-stack bio to read around pages with faulted address will cause

Re: [PATCH 3/6] drm/rockchip: vop: fix NV12 video display error

Hi mark, 在 2017/7/31 17:49, Mark Yao 写道: fixup the scale calculation formula on the case src_height == (dst_height/2). Signed-off-by: Mark Yao --- drivers/gpu/drm/rockchip/rockchip_drm_vop.h | 3 +++ 1 file changed, 3 insertions(+) diff --git

Re: [PATCH 3/6] drm/rockchip: vop: fix NV12 video display error

Hi mark, 在 2017/7/31 17:49, Mark Yao 写道: fixup the scale calculation formula on the case src_height == (dst_height/2). Signed-off-by: Mark Yao --- drivers/gpu/drm/rockchip/rockchip_drm_vop.h | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_vop.h

Re: [PATCH 4/6] drm/rockchip: vop: round_up pitches to word align

在 2017/7/31 17:49, Mark Yao 写道: VOP pitch register is word align, need align to word. VOP_WIN0_VIR: bit[31:16] win0_vir_stride_uv Number of words of Win0 uv Virtual width bit[15:0] win0_vir_width Number of words of Win0 yrgb Virtual width ARGB888 : win0_vir_width

Re: [PATCH 4/6] drm/rockchip: vop: round_up pitches to word align

在 2017/7/31 17:49, Mark Yao 写道: VOP pitch register is word align, need align to word. VOP_WIN0_VIR: bit[31:16] win0_vir_stride_uv Number of words of Win0 uv Virtual width bit[15:0] win0_vir_width Number of words of Win0 yrgb Virtual width ARGB888 : win0_vir_width

Re: [PATCH] initcall_debug: add deferred probe times

On Tue, Jul 25, 2017 at 08:01:49PM -0700, Todd Poynor wrote: > On Tue, Jul 25, 2017 at 4:40 PM, Greg Kroah-Hartman > wrote: > > On Tue, Jul 25, 2017 at 04:31:59PM -0700, Todd Poynor wrote: > >> initcall_debug attributes all deferred device probe retries for the > >>

Re: [PATCH] initcall_debug: add deferred probe times

On Tue, Jul 25, 2017 at 08:01:49PM -0700, Todd Poynor wrote: > On Tue, Jul 25, 2017 at 4:40 PM, Greg Kroah-Hartman > wrote: > > On Tue, Jul 25, 2017 at 04:31:59PM -0700, Todd Poynor wrote: > >> initcall_debug attributes all deferred device probe retries for the > >> late_initcall level to

Re: [PATCH v5 1/6] seccomp: Sysctl to display available actions

On 08/03/2017 11:37 AM, Kees Cook wrote: > On Fri, Jul 28, 2017 at 1:55 PM, Tyler Hicks wrote: >> This patch creates a read-only sysctl containing an ordered list of >> seccomp actions that the kernel supports. The ordering, from left to >> right, is the lowest action value

Re: [PATCH v5 1/6] seccomp: Sysctl to display available actions

On 08/03/2017 11:37 AM, Kees Cook wrote: > On Fri, Jul 28, 2017 at 1:55 PM, Tyler Hicks wrote: >> This patch creates a read-only sysctl containing an ordered list of >> seccomp actions that the kernel supports. The ordering, from left to >> right, is the lowest action value (kill) to the highest

Re: [PATCH 1/2] wireless: move prism54 out to staging

On Thu, Aug 03, 2017 at 04:59:36PM -0700, Luis R. Rodriguez wrote: > prism54 is deprecated in favor of the p54pci device driver. Although > only *one soul* had reported issues with it long ago Linux most Linux > distributions these days just disable the device driver given the > conflicts with the

Re: [PATCH 1/2] wireless: move prism54 out to staging

On Thu, Aug 03, 2017 at 04:59:36PM -0700, Luis R. Rodriguez wrote: > prism54 is deprecated in favor of the p54pci device driver. Although > only *one soul* had reported issues with it long ago Linux most Linux > distributions these days just disable the device driver given the > conflicts with the

Re: perf: bug in rdpmc/mmap accounting after exec

On Wed, Aug 2, 2017 at 10:39 AM, Peter Zijlstra wrote: > On Wed, Jul 26, 2017 at 03:39:01PM -0400, Vince Weaver wrote: >> Hello >> >> so one last bug found by the PAPI testsuite. >> >> This one involves the rdpmc auto-disable on last unmap of an event >> feature. >> >>

Re: perf: bug in rdpmc/mmap accounting after exec

On Wed, Aug 2, 2017 at 10:39 AM, Peter Zijlstra wrote: > On Wed, Jul 26, 2017 at 03:39:01PM -0400, Vince Weaver wrote: >> Hello >> >> so one last bug found by the PAPI testsuite. >> >> This one involves the rdpmc auto-disable on last unmap of an event >> feature. >> >> Failing test case: >> >>

Re: [PATCH v2 1/3] kvm: svm: Add support for additional SVM NPF error codes

On 8/2/17 5:42 AM, Paolo Bonzini wrote: > On 01/08/2017 15:36, Brijesh Singh wrote: >>> The flow is: >>> >>>hardware walks page table; L2 page table points to read only memory >>>-> pf_interception (code = >>>-> kvm_handle_page_fault (need_unprotect = false) >>>->

Re: [PATCH v2 1/3] kvm: svm: Add support for additional SVM NPF error codes

On 8/2/17 5:42 AM, Paolo Bonzini wrote: > On 01/08/2017 15:36, Brijesh Singh wrote: >>> The flow is: >>> >>>hardware walks page table; L2 page table points to read only memory >>>-> pf_interception (code = >>>-> kvm_handle_page_fault (need_unprotect = false) >>>->

Re: [v5 11/15] arm64/kasan: explicitly zero kasan shadow memory

(+ arm64 maintainers) Hi Pavel, On 3 August 2017 at 22:23, Pavel Tatashin wrote: > To optimize the performance of struct page initialization, > vmemmap_populate() will no longer zero memory. > > We must explicitly zero the memory that is allocated by

Re: [v5 11/15] arm64/kasan: explicitly zero kasan shadow memory

(+ arm64 maintainers) Hi Pavel, On 3 August 2017 at 22:23, Pavel Tatashin wrote: > To optimize the performance of struct page initialization, > vmemmap_populate() will no longer zero memory. > > We must explicitly zero the memory that is allocated by vmemmap_populate() > for kasan, as this

Re: [RFC PATCH] exec: Avoid recursive modprobe for binary format handlers

On Thu, Aug 03, 2017 at 05:02:40PM -0700, Kees Cook wrote: > On Wed, Aug 2, 2017 at 4:23 PM, Luis R. Rodriguez wrote: > > On Tue, Aug 01, 2017 at 07:28:20PM -0700, Kees Cook wrote: > >> On Tue, Aug 1, 2017 at 5:12 PM, Luis R. Rodriguez > >> wrote: > >> > On

Re: [RFC PATCH] exec: Avoid recursive modprobe for binary format handlers

On Thu, Aug 03, 2017 at 05:02:40PM -0700, Kees Cook wrote: > On Wed, Aug 2, 2017 at 4:23 PM, Luis R. Rodriguez wrote: > > On Tue, Aug 01, 2017 at 07:28:20PM -0700, Kees Cook wrote: > >> On Tue, Aug 1, 2017 at 5:12 PM, Luis R. Rodriguez > >> wrote: > >> > On Fri, Jul 21, 2017 at 03:05:20PM

[PATCH] MIPS: Add missing file for eBPF JIT.

Inexplicably, commit f381bf6d82f0 ("MIPS: Add support for eBPF JIT.") lost a file somewhere on its path to Linus' tree. Add back the missing ebpf_jit.c so that we can build with CONFIG_BPF_JIT selected. This version of ebpf_jit.c is identical to the original except for two minor change need to

[PATCH] MIPS: Add missing file for eBPF JIT.

Inexplicably, commit f381bf6d82f0 ("MIPS: Add support for eBPF JIT.") lost a file somewhere on its path to Linus' tree. Add back the missing ebpf_jit.c so that we can build with CONFIG_BPF_JIT selected. This version of ebpf_jit.c is identical to the original except for two minor change need to

Re: [RFC PATCH] exec: Avoid recursive modprobe for binary format handlers

On Wed, Aug 2, 2017 at 4:23 PM, Luis R. Rodriguez wrote: > On Tue, Aug 01, 2017 at 07:28:20PM -0700, Kees Cook wrote: >> On Tue, Aug 1, 2017 at 5:12 PM, Luis R. Rodriguez wrote: >> > On Fri, Jul 21, 2017 at 03:05:20PM +0100, Matt Redfearn wrote: >> >> Commit

Re: [RFC PATCH] exec: Avoid recursive modprobe for binary format handlers

On Wed, Aug 2, 2017 at 4:23 PM, Luis R. Rodriguez wrote: > On Tue, Aug 01, 2017 at 07:28:20PM -0700, Kees Cook wrote: >> On Tue, Aug 1, 2017 at 5:12 PM, Luis R. Rodriguez wrote: >> > On Fri, Jul 21, 2017 at 03:05:20PM +0100, Matt Redfearn wrote: >> >> Commit 6d7964a722af ("kmod: throttle kmod

[PATCH v2 1/7] spi: spi-ep93xx: remove io wrappers

From: H Hartley Sweeten The io wrappers just add obfuscation to the driver. Remove them. Signed-off-by: H Hartley Sweeten --- drivers/spi/spi-ep93xx.c | 72 +--- 1 file changed, 25

[PATCH v2 1/7] spi: spi-ep93xx: remove io wrappers

From: H Hartley Sweeten The io wrappers just add obfuscation to the driver. Remove them. Signed-off-by: H Hartley Sweeten --- drivers/spi/spi-ep93xx.c | 72 +--- 1 file changed, 25 insertions(+), 47 deletions(-) diff --git

[PATCH v2 5/7] spi: spi-ep93xx: pass the spi_master pointer around

From: H Hartley Sweeten Change the parameters for some of the functions so that the spi_master pointer is passed around instead of the private data ep93xx_spi pointer. This allows removing the 'pdev' member of the private data and will help with some later cleanup.

[PATCH v2 2/7] spi: spi-ep93xx: use 32-bit read/write for all registers

From: H Hartley Sweeten All the EP93xx SSP registers are 32-bit. Since most of the upper bits are unused, this driver tries to be tricky and uses 8 or 16-bit I/O to access the registers. This really just adds a bit of confusion. Simplify the I/O by using 32-bit

[PATCH v2 5/7] spi: spi-ep93xx: pass the spi_master pointer around

From: H Hartley Sweeten Change the parameters for some of the functions so that the spi_master pointer is passed around instead of the private data ep93xx_spi pointer. This allows removing the 'pdev' member of the private data and will help with some later cleanup. Signed-off-by: H Hartley

[PATCH v2 2/7] spi: spi-ep93xx: use 32-bit read/write for all registers

From: H Hartley Sweeten All the EP93xx SSP registers are 32-bit. Since most of the upper bits are unused, this driver tries to be tricky and uses 8 or 16-bit I/O to access the registers. This really just adds a bit of confusion. Simplify the I/O by using 32-bit read/write's for all of the

[PATCH v2 4/7] spi: spi-ep93xx: absorb the interrupt enable/disable helpers

From: H Hartley Sweeten These are each only called once. Just absorb them into the callers. Signed-off-by: H Hartley Sweeten [chris: use u32 instead of unsigned int] Signed-off-by: Chris Packham

[PATCH v2 6/7] spi: spi-ep93xx: remove private data 'current_msg'

From: H Hartley Sweeten The currently in-flight message can be found from the spi master. Use that instead and remove the private data pointer. Signed-off-by: H Hartley Sweeten Reviewed-by: Andy Shevchenko

[PATCH v2 3/7] spi: spi-ep93xx: add spi master prepare_transfer_hardware()

From: H Hartley Sweeten This driver currently enables the hardware at the start of every message and disabled it when the message is complete. Make it a bit smarter by adding the prepare_transfer_hardware() and unprepare_transfer_hardware() callbacks so that the

[PATCH v2 4/7] spi: spi-ep93xx: absorb the interrupt enable/disable helpers

From: H Hartley Sweeten These are each only called once. Just absorb them into the callers. Signed-off-by: H Hartley Sweeten [chris: use u32 instead of unsigned int] Signed-off-by: Chris Packham Reviewed-by: Andy Shevchenko --- drivers/spi/spi-ep93xx.c | 32

<    1   2   3   4   5   6   7   8   9   10   >