[ANNOUNCE] 4.4.15-rt23

Dear RT Folks, I'm pleased to announce the 4.4.15-rt23 stable release. This release is just an update to the new stable 4.4.15 version and no RT specific changes have been made. You can get this release via the git tree at:

[ANNOUNCE] 4.4.15-rt23

Dear RT Folks, I'm pleased to announce the 4.4.15-rt23 stable release. This release is just an update to the new stable 4.4.15 version and no RT specific changes have been made. You can get this release via the git tree at:

[PATCH 1/2] tpm: add sysfs attributes for tpm2

Break sysfs attributes into common and TPM 1.2/2.0-specific, and create sysfs groups for TPM2.0. Signed-off-by: Andrey Pronin --- drivers/char/tpm/tpm-chip.c | 48 drivers/char/tpm/tpm-sysfs.c | 24 -- 2

[PATCH 1/2] tpm: add sysfs attributes for tpm2

Break sysfs attributes into common and TPM 1.2/2.0-specific, and create sysfs groups for TPM2.0. Signed-off-by: Andrey Pronin --- drivers/char/tpm/tpm-chip.c | 48 drivers/char/tpm/tpm-sysfs.c | 24 -- 2 files changed, 53

[PATCH 0/2] tpm: driver- and tpm2-specific sysfs attributes

This patchset adds sysfs attributes for the cases not covered by the existing TPM1.2 support: - device-specific attributes provided by drivers like tpm_tis_spi - TPM2.0 Andrey Pronin (2): tpm: add sysfs attributes for tpm2 tpm: support driver-specific sysfs attrs in tpm_tis_core

[PATCH 0/2] tpm: driver- and tpm2-specific sysfs attributes

This patchset adds sysfs attributes for the cases not covered by the existing TPM1.2 support: - device-specific attributes provided by drivers like tpm_tis_spi - TPM2.0 Andrey Pronin (2): tpm: add sysfs attributes for tpm2 tpm: support driver-specific sysfs attrs in tpm_tis_core

[PATCH 2/2] tpm: support driver-specific sysfs attrs in tpm_tis_core

Add attr_group to phy_ops that a driver relying on tpm_tis_core_init can set to have its specific attributes registered in sysfs. Signed-off-by: Andrey Pronin --- drivers/char/tpm/tpm-sysfs.c| 1 - drivers/char/tpm/tpm.h | 8 +++-

[PATCH 2/2] tpm: support driver-specific sysfs attrs in tpm_tis_core

Add attr_group to phy_ops that a driver relying on tpm_tis_core_init can set to have its specific attributes registered in sysfs. Signed-off-by: Andrey Pronin --- drivers/char/tpm/tpm-sysfs.c| 1 - drivers/char/tpm/tpm.h | 8 +++- drivers/char/tpm/tpm_tis_core.c | 3 +++

[PATCH] mmc: dw_mmc: remove parsing for each slot subnode

The intention to remove it comes from the conflict of what the mmc-core does with the way dw_mmc treats disable-wp. We could see that 'disable-wp' is supported by core but it's deprecated by dw_mmc as we don't expect it to be existed for each slot subnode but should be in the parent node. Based on

[PATCH] mmc: dw_mmc: remove parsing for each slot subnode

The intention to remove it comes from the conflict of what the mmc-core does with the way dw_mmc treats disable-wp. We could see that 'disable-wp' is supported by core but it's deprecated by dw_mmc as we don't expect it to be existed for each slot subnode but should be in the parent node. Based on

Re: [PATCH kernel] powerpc/mm/iommu: Put pages on process exit

On 14/07/16 21:52, Alexey Kardashevskiy wrote: > On 14/07/16 20:12, Balbir Singh wrote: >> On Thu, Jul 14, 2016 at 3:16 PM, Alexey Kardashevskiy wrote: >>> At the moment VFIO IOMMU SPAPR v2 driver pins all guest RAM pages when >>> the userspace starts using VFIO. When the

Re: [PATCH kernel] powerpc/mm/iommu: Put pages on process exit

On 14/07/16 21:52, Alexey Kardashevskiy wrote: > On 14/07/16 20:12, Balbir Singh wrote: >> On Thu, Jul 14, 2016 at 3:16 PM, Alexey Kardashevskiy wrote: >>> At the moment VFIO IOMMU SPAPR v2 driver pins all guest RAM pages when >>> the userspace starts using VFIO. When the userspace process

Re: [RFC 0/3] extend kexec_file_load system call

Am Donnerstag, 14 Juli 2016, 10:29:11 schrieb Arnd Bergmann: > On Wednesday, July 13, 2016 11:18:04 PM CEST Thiago Jung Bauermann wrote: > > Am Mittwoch, 13 Juli 2016, 21:59:18 schrieb Arnd Bergmann: > > > On Wednesday, July 13, 2016 3:45:41 PM CEST Thiago Jung Bauermann wrote: > > > > Am

Re: [PATCH v4 2/4] drm/rockchip: add an common abstracted PSR driver

Sean, On 07/14/2016 11:14 PM, Sean Paul wrote: On Thu, Jul 14, 2016 at 12:15:49PM +0800, Yakir Yang wrote: The PSR driver have exported four symbols for specific device driver: - rockchip_drm_psr_register() - rockchip_drm_psr_unregister() - rockchip_drm_psr_enable() -

Re: [RFC 0/3] extend kexec_file_load system call

Am Donnerstag, 14 Juli 2016, 10:29:11 schrieb Arnd Bergmann: > On Wednesday, July 13, 2016 11:18:04 PM CEST Thiago Jung Bauermann wrote: > > Am Mittwoch, 13 Juli 2016, 21:59:18 schrieb Arnd Bergmann: > > > On Wednesday, July 13, 2016 3:45:41 PM CEST Thiago Jung Bauermann wrote: > > > > Am

Re: [PATCH v4 2/4] drm/rockchip: add an common abstracted PSR driver

Sean, On 07/14/2016 11:14 PM, Sean Paul wrote: On Thu, Jul 14, 2016 at 12:15:49PM +0800, Yakir Yang wrote: The PSR driver have exported four symbols for specific device driver: - rockchip_drm_psr_register() - rockchip_drm_psr_unregister() - rockchip_drm_psr_enable() -

Re: [PATCH v4 1/4] drm/rockchip: vop: export line flag function

Sean, On 07/14/2016 10:46 PM, Sean Paul wrote: On Thu, Jul 14, 2016 at 12:15:44PM +0800, Yakir Yang wrote: VOP have integrated a hardware counter which indicate the exact display line that vop is scanning. And if we're interested in a specific line, we can set the line number to vop line_flag

Re: [PATCH v4 1/4] drm/rockchip: vop: export line flag function

Sean, On 07/14/2016 10:46 PM, Sean Paul wrote: On Thu, Jul 14, 2016 at 12:15:44PM +0800, Yakir Yang wrote: VOP have integrated a hardware counter which indicate the exact display line that vop is scanning. And if we're interested in a specific line, we can set the line number to vop line_flag

Re: [PATCH RFC] uio: allow use on nommu systems

On Thu, Jul 14, 2016 at 08:53:06PM -0400, Rich Felker wrote: > mmap of uio devices does not seem to work without further > nommu-specific support, but interrupt handling already works, and > userspace drivers for nommu systems can simply use physical mmio > addresses from userspace directly anyway

Re: [PATCH v2 02/11] mm: Hardened usercopy

On Thu, Jul 14, 2016 at 09:04:18PM -0400, Rik van Riel wrote: > On Fri, 2016-07-15 at 09:20 +1000, Balbir Singh wrote: > > > > == > > > +    ((unsigned long)end & (unsigned > > > long)PAGE_MASK))) > > > + return NULL; > > > + > > > + /* Allow if start and end are inside the same

Re: [PATCH RFC] uio: allow use on nommu systems

On Thu, Jul 14, 2016 at 08:53:06PM -0400, Rich Felker wrote: > mmap of uio devices does not seem to work without further > nommu-specific support, but interrupt handling already works, and > userspace drivers for nommu systems can simply use physical mmio > addresses from userspace directly anyway

Re: [PATCH v2 02/11] mm: Hardened usercopy

On Thu, Jul 14, 2016 at 09:04:18PM -0400, Rik van Riel wrote: > On Fri, 2016-07-15 at 09:20 +1000, Balbir Singh wrote: > > > > == > > > +    ((unsigned long)end & (unsigned > > > long)PAGE_MASK))) > > > + return NULL; > > > + > > > + /* Allow if start and end are inside the same

Re: [PATCH v10 2/4] CMDQ: Mediatek CMDQ driver

Hi Paul, On Thu, 2016-07-14 at 19:38 -0400, Paul Gortmaker wrote: > On Thu, Jul 14, 2016 at 7:28 AM, HS Liao wrote: > > This patch is first version of Mediatek Command Queue(CMDQ) driver. The > > CMDQ is used to help write registers with critical time limitation, > > such

Re: [PATCH v10 2/4] CMDQ: Mediatek CMDQ driver

Hi Paul, On Thu, 2016-07-14 at 19:38 -0400, Paul Gortmaker wrote: > On Thu, Jul 14, 2016 at 7:28 AM, HS Liao wrote: > > This patch is first version of Mediatek Command Queue(CMDQ) driver. The > > CMDQ is used to help write registers with critical time limitation, > > such as updating display

[PATCH 2/2] tpm_tis_spi: add max xfer size

Signed-off-by: Andrey Pronin --- drivers/char/tpm/tpm_tis_spi.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/char/tpm/tpm_tis_spi.c b/drivers/char/tpm/tpm_tis_spi.c index dbaad9c..b103373 100644 --- a/drivers/char/tpm/tpm_tis_spi.c +++

[PATCH 0/2] tpm: add optional max xfer size check

This patchset introduces an optional maximum transfer size that can be specified by a tpm driver. Setting the max_xfer_size helps to catch the cases when burstcnt is incorrectly reported by the device (e.g. >64 for spi - happened in practice) and gracefully handle such situations. Andrey Pronin

[PATCH 2/2] tpm_tis_spi: add max xfer size

Signed-off-by: Andrey Pronin --- drivers/char/tpm/tpm_tis_spi.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/char/tpm/tpm_tis_spi.c b/drivers/char/tpm/tpm_tis_spi.c index dbaad9c..b103373 100644 --- a/drivers/char/tpm/tpm_tis_spi.c +++ b/drivers/char/tpm/tpm_tis_spi.c @@ -206,6

[PATCH 0/2] tpm: add optional max xfer size check

This patchset introduces an optional maximum transfer size that can be specified by a tpm driver. Setting the max_xfer_size helps to catch the cases when burstcnt is incorrectly reported by the device (e.g. >64 for spi - happened in practice) and gracefully handle such situations. Andrey Pronin

[PATCH 1/2] tpm_tis_core: add optional max xfer size check

If tpm reports a bigger burstcnt than allowed by the physical protocol, re-query the burstcnt and correct, if needed, if still too large. In practice, seen in case of xfer issues (e.g. in spi interface case, lost header causing flow control issues and wrong values returned on read from TPM_STS).

[PATCH 1/2] tpm_tis_core: add optional max xfer size check

If tpm reports a bigger burstcnt than allowed by the physical protocol, re-query the burstcnt and correct, if needed, if still too large. In practice, seen in case of xfer issues (e.g. in spi interface case, lost header causing flow control issues and wrong values returned on read from TPM_STS).

[PATCH] ARM: exynos_defconfig: Enable bus frequency scaling with DEVFREQ/DEVFREQ-Event

This patch enables the bus frequency scaling driver with DEVFREQ and DEVFREQ-Event framework. This patches already was merged for Odroid-U3/XU3 ,Trats2 and Rinato/Monk boards. Signed-off-by: Chanwoo Choi --- arch/arm/configs/exynos_defconfig | 10 ++ 1 file

[PATCH] ARM: exynos_defconfig: Enable bus frequency scaling with DEVFREQ/DEVFREQ-Event

This patch enables the bus frequency scaling driver with DEVFREQ and DEVFREQ-Event framework. This patches already was merged for Odroid-U3/XU3 ,Trats2 and Rinato/Monk boards. Signed-off-by: Chanwoo Choi --- arch/arm/configs/exynos_defconfig | 10 ++ 1 file changed, 10 insertions(+)

[PATCH] spi: rockchip: limit transfers to (64K - 1) bytes

The Rockchip SPI controller's length register only supports 16-bits, yielding a maximum length of 64KiB (the CTRLR1 register holds "length - 1"). Trying to transfer more than that (e.g., with a large SPI flash read) will cause the driver to hang. Now, it seems that while theoretically we should

[PATCH] spi: rockchip: limit transfers to (64K - 1) bytes

The Rockchip SPI controller's length register only supports 16-bits, yielding a maximum length of 64KiB (the CTRLR1 register holds "length - 1"). Trying to transfer more than that (e.g., with a large SPI flash read) will cause the driver to hang. Now, it seems that while theoretically we should

Re: [PATCH v3 08/12] irqchip: add J-Core AIC driver

On Wed, May 25, 2016 at 05:43:03AM +, Rich Felker wrote: > There are two versions of the J-Core interrupt controller in use, aic1 > which generates interrupts with programmable priorities, but only > supports 8 irq lines and maps them to cpu traps in the range 17 to 24, > and aic2 which uses

Re: [PATCH v3 08/12] irqchip: add J-Core AIC driver

On Wed, May 25, 2016 at 05:43:03AM +, Rich Felker wrote: > There are two versions of the J-Core interrupt controller in use, aic1 > which generates interrupts with programmable priorities, but only > supports 8 irq lines and maps them to cpu traps in the range 17 to 24, > and aic2 which uses

Re: [PATCH v12] mtd: spi-nor: add hisilicon spi-nor flash controller driver

Hi Brian, On 2016/7/14 9:13, Brian Norris wrote: > On Tue, Jun 28, 2016 at 03:48:19PM +0800, Jiancheng Xue wrote: >> Add hisilicon spi-nor flash controller driver >> >> Signed-off-by: Binquan Peng >> Signed-off-by: Jiancheng Xue >>

Re: [PATCH v12] mtd: spi-nor: add hisilicon spi-nor flash controller driver

Hi Brian, On 2016/7/14 9:13, Brian Norris wrote: > On Tue, Jun 28, 2016 at 03:48:19PM +0800, Jiancheng Xue wrote: >> Add hisilicon spi-nor flash controller driver >> >> Signed-off-by: Binquan Peng >> Signed-off-by: Jiancheng Xue >> Acked-by: Rob Herring >> Reviewed-by: Ezequiel Garcia >>

[PATCH] arm64: dts: rockchip: add spiX aliases for rk3399

It's nicer to see this: # ls -l /sys/bus/spi/devices/ total 0 lrwxrwxrwx 1 root root 0 Dec 31 1969 spi0.0 -> ../../../devices/platform/ff1c.spi/spi_master/spi0/spi0.0 lrwxrwxrwx 1 root root 0 Dec 31 1969 spi1.0 ->

[PATCH] arm64: dts: rockchip: add spiX aliases for rk3399

It's nicer to see this: # ls -l /sys/bus/spi/devices/ total 0 lrwxrwxrwx 1 root root 0 Dec 31 1969 spi0.0 -> ../../../devices/platform/ff1c.spi/spi_master/spi0/spi0.0 lrwxrwxrwx 1 root root 0 Dec 31 1969 spi1.0 ->

Re: [PATCH] mem-hotplug: use GFP_HIGHUSER_MOVABLE and alloc from next node in alloc_migrate_target()

On 2016/7/15 6:17, David Rientjes wrote: > On Thu, 14 Jul 2016, Xishi Qiu wrote: > >> alloc_migrate_target() is called from migrate_pages(), and the page >> is always from user space, so we can add __GFP_HIGHMEM directly. >> >> Second, when we offline a node, the new page should alloced from

Re: [PATCH] mem-hotplug: use GFP_HIGHUSER_MOVABLE and alloc from next node in alloc_migrate_target()

On 2016/7/15 6:17, David Rientjes wrote: > On Thu, 14 Jul 2016, Xishi Qiu wrote: > >> alloc_migrate_target() is called from migrate_pages(), and the page >> is always from user space, so we can add __GFP_HIGHMEM directly. >> >> Second, when we offline a node, the new page should alloced from

[PATCH] arm64: dts: rockchip: remove broken-cd from sdio0

commit 1ade61c141e2 ("arm64: dts: rockchip: remove broken-cd from emmc and sdio") was intended to remove the abuse of broken-cd property from mmc. But somehow it forgot to remove this property from sdio0 node. Let's remove it now. Signed-off-by: Shawn Lin ---

[PATCH] arm64: dts: rockchip: remove broken-cd from sdio0

commit 1ade61c141e2 ("arm64: dts: rockchip: remove broken-cd from emmc and sdio") was intended to remove the abuse of broken-cd property from mmc. But somehow it forgot to remove this property from sdio0 node. Let's remove it now. Signed-off-by: Shawn Lin ---

[PATCH 1/2] tpm: define constants for tpm2 properties

Change-Id: I47cb1793736781fbea93e5bf80b783e0ac9e8628 Signed-off-by: Andrey Pronin --- drivers/char/tpm/tpm.h | 26 ++ 1 file changed, 26 insertions(+) diff --git a/drivers/char/tpm/tpm.h b/drivers/char/tpm/tpm.h index 8890df2..ad3b9d1 100644 ---

[PATCH 2/2] tpm: fix byte-order for the value read by tpm2_get_tpm_pt

Change-Id: I7d71cd379b1a3b7659d20a1b6008216762596590 Signed-off-by: Andrey Pronin --- drivers/char/tpm/tpm2-cmd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/char/tpm/tpm2-cmd.c b/drivers/char/tpm/tpm2-cmd.c index a1673dc..a88b31e 100644 ---

[PATCH 1/2] tpm: define constants for tpm2 properties

Change-Id: I47cb1793736781fbea93e5bf80b783e0ac9e8628 Signed-off-by: Andrey Pronin --- drivers/char/tpm/tpm.h | 26 ++ 1 file changed, 26 insertions(+) diff --git a/drivers/char/tpm/tpm.h b/drivers/char/tpm/tpm.h index 8890df2..ad3b9d1 100644 --- a/drivers/char/tpm/tpm.h

[PATCH 2/2] tpm: fix byte-order for the value read by tpm2_get_tpm_pt

Change-Id: I7d71cd379b1a3b7659d20a1b6008216762596590 Signed-off-by: Andrey Pronin --- drivers/char/tpm/tpm2-cmd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/char/tpm/tpm2-cmd.c b/drivers/char/tpm/tpm2-cmd.c index a1673dc..a88b31e 100644 ---

[PATCH 0/2] tpm: better support for 32-bit tpm2 properties

These patches help working with 32-bit TPM2.0-specific properties that can be read using TPM2_GetCapability(capability = TPM_CAP_TPM_PROPERTIES): - TPM_PT_PERMANENT - TPM_PT_STARTUP_CLEAR Andrey Pronin (2): tpm: define constants for tpm2 properties tpm: fix byte-order for the value read by

[PATCH 0/2] tpm: better support for 32-bit tpm2 properties

These patches help working with 32-bit TPM2.0-specific properties that can be read using TPM2_GetCapability(capability = TPM_CAP_TPM_PROPERTIES): - TPM_PT_PERMANENT - TPM_PT_STARTUP_CLEAR Andrey Pronin (2): tpm: define constants for tpm2 properties tpm: fix byte-order for the value read by

Re: [PATCH v2 02/11] mm: Hardened usercopy

On Fri, 2016-07-15 at 09:20 +1000, Balbir Singh wrote: > > == > > +    ((unsigned long)end & (unsigned > > long)PAGE_MASK))) > > + return NULL; > > + > > + /* Allow if start and end are inside the same compound > > page. */ > > + endpage = virt_to_head_page(end); > > +

Re: [PATCH v2 02/11] mm: Hardened usercopy

On Fri, 2016-07-15 at 09:20 +1000, Balbir Singh wrote: > > == > > +    ((unsigned long)end & (unsigned > > long)PAGE_MASK))) > > + return NULL; > > + > > + /* Allow if start and end are inside the same compound > > page. */ > > + endpage = virt_to_head_page(end); > > +

Re: [PATCH v7 5/9] MAINTAINERS / ACPI: add the ARM64-specific ACPI Support maintainers

Hi Rafael, On 14 July 2016 at 04:16, Rafael J. Wysocki wrote: > On Wed, Jul 13, 2016 at 7:53 PM, wrote: >> From: Fu Wei >> >> This patch add the ARM64-specific ACPI Support maintainers in >> MAINTAINERS, according to the discussion on

Re: [PATCH v7 5/9] MAINTAINERS / ACPI: add the ARM64-specific ACPI Support maintainers

Hi Rafael, On 14 July 2016 at 04:16, Rafael J. Wysocki wrote: > On Wed, Jul 13, 2016 at 7:53 PM, wrote: >> From: Fu Wei >> >> This patch add the ARM64-specific ACPI Support maintainers in >> MAINTAINERS, according to the discussion on mailing list: >> https://lkml.org/lkml/2016/6/29/580 >>

Re: [PATCH] arm64: dts: rockchip: Add basic support for orion-r68

Hi Matthias, Just some comment for mmc stuff. :) 在 2016/7/14 20:28, Matthias Brugger 写道: This patch adds basic support for the Tronsmart orion r86 set-top-box. Signed-off-by: Matthias Brugger --- Changes since v1: - change memory node to 2GB - change compatible and file

Re: [PATCH] arm64: dts: rockchip: Add basic support for orion-r68

Hi Matthias, Just some comment for mmc stuff. :) 在 2016/7/14 20:28, Matthias Brugger 写道: This patch adds basic support for the Tronsmart orion r86 set-top-box. Signed-off-by: Matthias Brugger --- Changes since v1: - change memory node to 2GB - change compatible and file name - add uart4 -

Re: [PATCH] usb: ehci-platform: use helper variables in probe function

On Thu, 14 Jul 2016, Rafał Miłecki wrote: > > Okay except for... > > > >> - priv->num_phys = of_count_phandle_with_args(dev->dev.of_node, > >> - "phys", "#phy-cells"); > >> + priv->num_phys = of_count_phandle_with_args(np, "phys", > >> +

Re: [PATCH] usb: ehci-platform: use helper variables in probe function

On Thu, 14 Jul 2016, Rafał Miłecki wrote: > > Okay except for... > > > >> - priv->num_phys = of_count_phandle_with_args(dev->dev.of_node, > >> - "phys", "#phy-cells"); > >> + priv->num_phys = of_count_phandle_with_args(np, "phys", > >> +

[PATCH] staging: skein: cleanup: Remove multiple blank lines

This patch fixes several warnings detected by the checkpatch.pl script. Signed-off-by: Hugo Miguel Silva Ferreira --- drivers/staging/skein/threefish_block.c | 16 1 file changed, 16 deletions(-) diff --git a/drivers/staging/skein/threefish_block.c

[PATCH] staging: skein: cleanup: Remove multiple blank lines

This patch fixes several warnings detected by the checkpatch.pl script. Signed-off-by: Hugo Miguel Silva Ferreira --- drivers/staging/skein/threefish_block.c | 16 1 file changed, 16 deletions(-) diff --git a/drivers/staging/skein/threefish_block.c

[PATCH RFC] uio: allow use on nommu systems

mmap of uio devices does not seem to work without further nommu-specific support, but interrupt handling already works, and userspace drivers for nommu systems can simply use physical mmio addresses from userspace directly anyway without mmap. Signed-off-by: Rich Felker --- I

[PATCH RFC] uio: allow use on nommu systems

mmap of uio devices does not seem to work without further nommu-specific support, but interrupt handling already works, and userspace drivers for nommu systems can simply use physical mmio addresses from userspace directly anyway without mmap. Signed-off-by: Rich Felker --- I don't particularly

[PATCH 4/5] f2fs: add maximum prefree segments

In 1TB storage, we need to admit 22841 prefree segments, which can consume too much segments. This patch sets 8GB in max. prefree segments in that case. Signed-off-by: Jaegeuk Kim --- fs/f2fs/segment.c | 3 +++ fs/f2fs/segment.h | 1 + 2 files changed, 4 insertions(+) diff

[PATCH 4/5] f2fs: add maximum prefree segments

In 1TB storage, we need to admit 22841 prefree segments, which can consume too much segments. This patch sets 8GB in max. prefree segments in that case. Signed-off-by: Jaegeuk Kim --- fs/f2fs/segment.c | 3 +++ fs/f2fs/segment.h | 1 + 2 files changed, 4 insertions(+) diff --git

[PATCH 3/5] f2fs: support copy_file_range

This patch implements copy_file_range in f2fs. Signed-off-by: Jaegeuk Kim --- fs/f2fs/file.c | 67 ++ 1 file changed, 67 insertions(+) diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c index dd399b3..c529884 100644 ---

[PATCH 3/5] f2fs: support copy_file_range

This patch implements copy_file_range in f2fs. Signed-off-by: Jaegeuk Kim --- fs/f2fs/file.c | 67 ++ 1 file changed, 67 insertions(+) diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c index dd399b3..c529884 100644 --- a/fs/f2fs/file.c +++

[PATCH 1/5] f2fs: refactor __exchange_data_block for speed up

This reduces the elapsed time to do xfstests/generic/017. Before: 715 s After: 458 s Signed-off-by: Jaegeuk Kim --- fs/f2fs/file.c | 236 + fs/f2fs/node.c | 1 + 2 files changed, 171 insertions(+), 66 deletions(-)

[PATCH 1/5] f2fs: refactor __exchange_data_block for speed up

This reduces the elapsed time to do xfstests/generic/017. Before: 715 s After: 458 s Signed-off-by: Jaegeuk Kim --- fs/f2fs/file.c | 236 + fs/f2fs/node.c | 1 + 2 files changed, 171 insertions(+), 66 deletions(-) diff --git

[PATCH 5/5] f2fs: use blk_plug in all the possible paths

This patch reverts 19a5f5e2ef37 (f2fs: drop any block plugging), and adds blk_plug in write paths additionally. The main reason is that blk_start_plug can be used to wake up from low-power mode before submitting further bios. Signed-off-by: Jaegeuk Kim ---

[PATCH 2/5] f2fs: disable extent_cache for fcollapse/finsert inodes

This reduces the elapsed time to do xfstests/generic/017. Before: 458 s After: 390 s Signed-off-by: Jaegeuk Kim --- fs/f2fs/extent_cache.c | 13 + fs/f2fs/f2fs.h | 1 + fs/f2fs/file.c | 5 + 3 files changed, 19 insertions(+) diff --git

[PATCH 5/5] f2fs: use blk_plug in all the possible paths

This patch reverts 19a5f5e2ef37 (f2fs: drop any block plugging), and adds blk_plug in write paths additionally. The main reason is that blk_start_plug can be used to wake up from low-power mode before submitting further bios. Signed-off-by: Jaegeuk Kim --- fs/f2fs/checkpoint.c | 7 +++

[PATCH 2/5] f2fs: disable extent_cache for fcollapse/finsert inodes

This reduces the elapsed time to do xfstests/generic/017. Before: 458 s After: 390 s Signed-off-by: Jaegeuk Kim --- fs/f2fs/extent_cache.c | 13 + fs/f2fs/f2fs.h | 1 + fs/f2fs/file.c | 5 + 3 files changed, 19 insertions(+) diff --git

Re: [PATCH 1/2] net: ethernet: ll_temac: use phydev from struct net_device

From: Philippe Reynes Date: Thu, 14 Jul 2016 01:48:51 +0200 > The private structure contain a pointer to phydev, but the structure > net_device already contain such pointer. So we can remove the pointer > phy in the private structure, and update the driver to use the > one

Re: [PATCH 1/2] net: ethernet: ll_temac: use phydev from struct net_device

From: Philippe Reynes Date: Thu, 14 Jul 2016 01:48:51 +0200 > The private structure contain a pointer to phydev, but the structure > net_device already contain such pointer. So we can remove the pointer > phy in the private structure, and update the driver to use the > one contained in struct

Re: [PATCH 2/2] net: ethernet: ll_temac: use phy_ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Thu, 14 Jul 2016 01:48:52 +0200 > There are two generics functions phy_ethtool_{get|set}_link_ksettings, > so we can use them instead of defining the same code in the driver. > > Signed-off-by: Philippe Reynes Applied.

Re: [PATCH 2/2] net: ethernet: ll_temac: use phy_ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Thu, 14 Jul 2016 01:48:52 +0200 > There are two generics functions phy_ethtool_{get|set}_link_ksettings, > so we can use them instead of defining the same code in the driver. > > Signed-off-by: Philippe Reynes Applied.

Re: pull-request: wireless-drivers-next 2016-07-13

From: Kalle Valo Date: Wed, 13 Jul 2016 21:29:13 +0300 > here's a pull request for net-next. This time there are few conflicts > due to the cfg80211 scan API changes, and one of them is easy to miss, > so please pay extra attention to them. Otherwise there's not nothing >

Re: pull-request: wireless-drivers-next 2016-07-13

From: Kalle Valo Date: Wed, 13 Jul 2016 21:29:13 +0300 > here's a pull request for net-next. This time there are few conflicts > due to the cfg80211 scan API changes, and one of them is easy to miss, > so please pay extra attention to them. Otherwise there's not nothing > really out of ordinary.

Re: [PATCH v3] locking/qrwlock: Let qrwlock has same layout regardless of the endian

On Thu, Jul 14, 2016 at 11:46:26AM +0200, Peter Zijlstra wrote: > On Thu, Jul 14, 2016 at 11:37:33AM +0200, Peter Zijlstra wrote: > > static inline u8 *__qspinlock_lock_byte(struct qspinlock *lock) > > { > > return (u8 *)lock + 3 * IS_BUILTIN(__BIG_ENDIAN); > > } > > Bugger, that doesn't

Re: [PATCH v3] locking/qrwlock: Let qrwlock has same layout regardless of the endian

On Thu, Jul 14, 2016 at 11:46:26AM +0200, Peter Zijlstra wrote: > On Thu, Jul 14, 2016 at 11:37:33AM +0200, Peter Zijlstra wrote: > > static inline u8 *__qspinlock_lock_byte(struct qspinlock *lock) > > { > > return (u8 *)lock + 3 * IS_BUILTIN(__BIG_ENDIAN); > > } > > Bugger, that doesn't

Re: [PATCH] Enclose multiple statements macros in a do while loop

On Thu, Jul 14, 2016 at 05:01:51PM +0800, Sunbing wrote: > The formatting of macros definetion in ks7010/michael_mic.c is not > consistent with the general kernel coding style. > > Fix it by the result of scripts/checkpatch.pl. > > No functional changes. > > Signed-off-by: Sunbing

Re: [PATCH] Enclose multiple statements macros in a do while loop

On Thu, Jul 14, 2016 at 05:01:51PM +0800, Sunbing wrote: > The formatting of macros definetion in ks7010/michael_mic.c is not > consistent with the general kernel coding style. > > Fix it by the result of scripts/checkpatch.pl. > > No functional changes. > > Signed-off-by: Sunbing We need a

[PATCH] tpm_tis_core: convert max timeouts from msec to jiffies

tpm_tis_core was missing conversion from msec when assigning max timeouts from constants. Signed-off-by: Andrey Pronin --- drivers/char/tpm/tpm_tis_core.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/char/tpm/tpm_tis_core.c

[PATCH] tpm_tis_core: convert max timeouts from msec to jiffies

tpm_tis_core was missing conversion from msec when assigning max timeouts from constants. Signed-off-by: Andrey Pronin --- drivers/char/tpm/tpm_tis_core.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/char/tpm/tpm_tis_core.c

Re: [patch V2 30/67] powerpc/numa: Convert to hotplug state machine

Hi Anna-Maria, > >> Install the callbacks via the state machine and let the core invoke > >> the callbacks on the already online CPUs. > > > > This is causing an oops on ppc64le QEMU, looks like a NULL > > pointer: > > Did you tested it against tip WIP.hotplug? I noticed tip started failing

Re: [patch V2 30/67] powerpc/numa: Convert to hotplug state machine

Hi Anna-Maria, > >> Install the callbacks via the state machine and let the core invoke > >> the callbacks on the already online CPUs. > > > > This is causing an oops on ppc64le QEMU, looks like a NULL > > pointer: > > Did you tested it against tip WIP.hotplug? I noticed tip started failing

Re: [PATCH v3 6/8] thunderbolt: Networking state machine

On Thu, Jul 14, 2016 at 7:28 AM, Amir Levy wrote: > Negotiation states that a peer goes through in order to establish > the communication with the second peer. > This includes communication with upper layer and additional > infrastructure support to communicate with the

Re: [PATCH v3 6/8] thunderbolt: Networking state machine

On Thu, Jul 14, 2016 at 7:28 AM, Amir Levy wrote: > Negotiation states that a peer goes through in order to establish > the communication with the second peer. > This includes communication with upper layer and additional > infrastructure support to communicate with the second peer through ICM. >

perf probe -F with wildcards

Hi Masami, I think this worked at some point? [root@jouet acme]# perf probe -F | tail zswap_frontswap_init zswap_frontswap_invalidate_area zswap_frontswap_invalidate_page zswap_frontswap_load zswap_frontswap_store zswap_pool_create zswap_pool_current zswap_update_total_size

perf probe -F with wildcards

Hi Masami, I think this worked at some point? [root@jouet acme]# perf probe -F | tail zswap_frontswap_init zswap_frontswap_invalidate_area zswap_frontswap_invalidate_page zswap_frontswap_load zswap_frontswap_store zswap_pool_create zswap_pool_current zswap_update_total_size

Re: [PATCH v6 1/3] x86/platform/p2sb: New Primary to Sideband bridge support driver for Intel SOC's

On Thu, Jul 14, 2016 at 4:11 AM, Tan Jui Nee wrote: > From: Andy Shevchenko > > There is already one and at least one more user coming which > require an access to Primary to Sideband bridge (P2SB) in order > to get IO or MMIO bar hidden

Re: [PATCH v6 1/3] x86/platform/p2sb: New Primary to Sideband bridge support driver for Intel SOC's

On Thu, Jul 14, 2016 at 4:11 AM, Tan Jui Nee wrote: > From: Andy Shevchenko > > There is already one and at least one more user coming which > require an access to Primary to Sideband bridge (P2SB) in order > to get IO or MMIO bar hidden by BIOS. > Create a driver to access P2SB for x86 devices.

Re: [patch V2 30/67] powerpc/numa: Convert to hotplug state machine

Hi, On 2016-07-14 23:42, Anton Blanchard wrote: Hi, From: Sebastian Andrzej Siewior Install the callbacks via the state machine and let the core invoke the callbacks on the already online CPUs. This is causing an oops on ppc64le QEMU, looks like a NULL pointer:

Re: [patch V2 30/67] powerpc/numa: Convert to hotplug state machine

Hi, On 2016-07-14 23:42, Anton Blanchard wrote: Hi, From: Sebastian Andrzej Siewior Install the callbacks via the state machine and let the core invoke the callbacks on the already online CPUs. This is causing an oops on ppc64le QEMU, looks like a NULL pointer: Did you tested it against

Re: [Query] Preemption (hogging) of the work handler

Sorry, but I failed to do any testing on this and answer the questions you raise. But I saw this again today and here are some important points. On 12-07-16, 23:03, Sergey Senozhatsky wrote: > so, I'm looking at this thing now: > > : [ 12.874909] sched: RT throttling activated for rt_rq

Re: [Query] Preemption (hogging) of the work handler

Sorry, but I failed to do any testing on this and answer the questions you raise. But I saw this again today and here are some important points. On 12-07-16, 23:03, Sergey Senozhatsky wrote: > so, I'm looking at this thing now: > > : [ 12.874909] sched: RT throttling activated for rt_rq

Re: [PATCH v10 2/4] CMDQ: Mediatek CMDQ driver

On Thu, Jul 14, 2016 at 7:28 AM, HS Liao wrote: > This patch is first version of Mediatek Command Queue(CMDQ) driver. The > CMDQ is used to help write registers with critical time limitation, > such as updating display configuration during the vblank. It controls > Global

Re: [PATCH v10 2/4] CMDQ: Mediatek CMDQ driver

On Thu, Jul 14, 2016 at 7:28 AM, HS Liao wrote: > This patch is first version of Mediatek Command Queue(CMDQ) driver. The > CMDQ is used to help write registers with critical time limitation, > such as updating display configuration during the vblank. It controls > Global Command Engine (GCE)

Re: [PATCH v2 02/11] mm: Hardened usercopy

On Wed, Jul 13, 2016 at 02:55:55PM -0700, Kees Cook wrote: > This is the start of porting PAX_USERCOPY into the mainline kernel. This > is the first set of features, controlled by CONFIG_HARDENED_USERCOPY. The > work is based on code by PaX Team and Brad Spengler, and an earlier port > from Casey

Re: [PATCH v2 02/11] mm: Hardened usercopy

On Wed, Jul 13, 2016 at 02:55:55PM -0700, Kees Cook wrote: > This is the start of porting PAX_USERCOPY into the mainline kernel. This > is the first set of features, controlled by CONFIG_HARDENED_USERCOPY. The > work is based on code by PaX Team and Brad Spengler, and an earlier port > from Casey

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