Re: [PATCH v4 3/3] ARM: dts: exynos: Remove the display-timing and delay from rinato dts

On Tue, Aug 29, 2017 at 4:52 AM, Hoegeun Kwon wrote: > Hi Krzysztof, > > The driver has been merged into exynos-drm-misc. > Could you please check this patch(3/3). Hi, OK, no problems for me but it is too late for current cycle so it will go in for v4.15. Best regards,

Re: [PATCH v4 3/3] ARM: dts: exynos: Remove the display-timing and delay from rinato dts

On Tue, Aug 29, 2017 at 4:52 AM, Hoegeun Kwon wrote: > Hi Krzysztof, > > The driver has been merged into exynos-drm-misc. > Could you please check this patch(3/3). Hi, OK, no problems for me but it is too late for current cycle so it will go in for v4.15. Best regards, Krzysztof > > Best

[PATCH 4/4] [media] zr364xx: Fix a typo in a comment line of the file header

From: Markus Elfring Date: Mon, 28 Aug 2017 22:46:30 +0200 Fix a word in this description. Signed-off-by: Markus Elfring --- drivers/media/usb/zr364xx/zr364xx.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 4/4] [media] zr364xx: Fix a typo in a comment line of the file header

From: Markus Elfring Date: Mon, 28 Aug 2017 22:46:30 +0200 Fix a word in this description. Signed-off-by: Markus Elfring --- drivers/media/usb/zr364xx/zr364xx.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/media/usb/zr364xx/zr364xx.c

[PATCH 3/4] [media] zr364xx: Adjust ten checks for null pointers

From: Markus Elfring Date: Mon, 28 Aug 2017 22:40:47 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The script “checkpatch.pl” pointed information out like the following. Comparison to NULL could be written !… Thus

[PATCH 3/4] [media] zr364xx: Adjust ten checks for null pointers

From: Markus Elfring Date: Mon, 28 Aug 2017 22:40:47 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The script “checkpatch.pl” pointed information out like the following. Comparison to NULL could be written !… Thus fix the affected source code

[PATCH 2/4] [media] zr364xx: Improve a size determination in zr364xx_probe()

From: Markus Elfring Date: Mon, 28 Aug 2017 22:28:02 +0200 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style

[PATCH 2/4] [media] zr364xx: Improve a size determination in zr364xx_probe()

From: Markus Elfring Date: Mon, 28 Aug 2017 22:28:02 +0200 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style convention. This issue was

Re: [PATCH v8 2/3] PCI: iproc: retry request when CRS returned from EP

On Tue, Aug 29, 2017 at 3:17 AM, Bjorn Helgaas wrote: > On Thu, Aug 24, 2017 at 10:34:25AM +0530, Oza Pawandeep wrote: >> PCIe spec r3.1, sec 2.3.2 >> If CRS software visibility is not enabled, the RC must reissue the >> config request as a new request. >> >> - If CRS software

Re: [PATCH v8 2/3] PCI: iproc: retry request when CRS returned from EP

On Tue, Aug 29, 2017 at 3:17 AM, Bjorn Helgaas wrote: > On Thu, Aug 24, 2017 at 10:34:25AM +0530, Oza Pawandeep wrote: >> PCIe spec r3.1, sec 2.3.2 >> If CRS software visibility is not enabled, the RC must reissue the >> config request as a new request. >> >> - If CRS software visibility is

[PATCH 1/4] [media] zr364xx: Delete an error message for a failed memory allocation in two functions

From: Markus Elfring Date: Mon, 28 Aug 2017 22:23:56 +0200 Omit an extra message for a memory allocation failure in these functions. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH 1/4] [media] zr364xx: Delete an error message for a failed memory allocation in two functions

From: Markus Elfring Date: Mon, 28 Aug 2017 22:23:56 +0200 Omit an extra message for a memory allocation failure in these functions. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- drivers/media/usb/zr364xx/zr364xx.c | 8 ++-- 1 file changed, 2

[PATCH 0/4] [media] zr364xx: Adjustments for some function implementations

From: Markus Elfring Date: Tue, 29 Aug 2017 07:17:07 +0200 A few update suggestions were taken into account from static source code analysis. Markus Elfring (4): Delete an error message for a failed memory allocation in two functions Improve a size

[PATCH 0/4] [media] zr364xx: Adjustments for some function implementations

From: Markus Elfring Date: Tue, 29 Aug 2017 07:17:07 +0200 A few update suggestions were taken into account from static source code analysis. Markus Elfring (4): Delete an error message for a failed memory allocation in two functions Improve a size determination in zr364xx_probe() Adjust

Re: [PATCH v8 0/3] PCI: iproc: SOC specific fixes

On Tue, Aug 29, 2017 at 3:23 AM, Bjorn Helgaas wrote: > On Thu, Aug 24, 2017 at 10:34:23AM +0530, Oza Pawandeep wrote: >> PCI: iproc: Retry request when CRS returned from EP Above patch adds >> support for CRS in PCI RC driver, otherwise if not handled at lower >> level, the

Re: [PATCH v8 0/3] PCI: iproc: SOC specific fixes

On Tue, Aug 29, 2017 at 3:23 AM, Bjorn Helgaas wrote: > On Thu, Aug 24, 2017 at 10:34:23AM +0530, Oza Pawandeep wrote: >> PCI: iproc: Retry request when CRS returned from EP Above patch adds >> support for CRS in PCI RC driver, otherwise if not handled at lower >> level, the user space PMD (poll

Re: [Cocci] cocci: remove unnecessary casts of void * while avoiding casts with __user or __force ?

On Mon, 28 Aug 2017, Joe Perches wrote: > A simple cocci script that removes unnecessary casts of > a void * will also remove casts with __force or __user Unfortunately, attributes are currently not supported inside casts. This can be done in a hackish way (possible false negatives) as

Re: [Cocci] cocci: remove unnecessary casts of void * while avoiding casts with __user or __force ?

On Mon, 28 Aug 2017, Joe Perches wrote: > A simple cocci script that removes unnecessary casts of > a void * will also remove casts with __force or __user Unfortunately, attributes are currently not supported inside casts. This can be done in a hackish way (possible false negatives) as

[no subject]

Sup Linux http://www.imr-asso.org/wp-content/uploads/innovation.php?corn=pks2ea81htmcx01ew Venkat

[no subject]

Sup Linux http://www.imr-asso.org/wp-content/uploads/innovation.php?corn=pks2ea81htmcx01ew Venkat

Re: [PATCH v3 1/3] mfd: Add support for Cherry Trail Dollar Cove TI PMIC

On Tue, 29 Aug 2017 00:31:15 +0200, Rafael J. Wysocki wrote: > > On Fri, Aug 25, 2017 at 3:44 PM, Takashi Iwai wrote: > > This patch adds the MFD driver for Dollar Cove (TI version) PMIC with > > ACPI INT33F5 that is found on some Intel Cherry Trail devices. > > The driver is

Re: [PATCH v3 1/3] mfd: Add support for Cherry Trail Dollar Cove TI PMIC

On Tue, 29 Aug 2017 00:31:15 +0200, Rafael J. Wysocki wrote: > > On Fri, Aug 25, 2017 at 3:44 PM, Takashi Iwai wrote: > > This patch adds the MFD driver for Dollar Cove (TI version) PMIC with > > ACPI INT33F5 that is found on some Intel Cherry Trail devices. > > The driver is based on the

Re: [PATCH] lsm_audit: use get_task_comm

On 2017-08-28 17:54, Paul Moore wrote: > On Mon, Aug 28, 2017 at 9:58 AM, Geliang Tang wrote: > > get_task_comm() copys the task's comm under the task_lock, it's safer > > than directly using memcpy(). > > > > Signed-off-by: Geliang Tang > > --- > >

Re: [PATCH] lsm_audit: use get_task_comm

On 2017-08-28 17:54, Paul Moore wrote: > On Mon, Aug 28, 2017 at 9:58 AM, Geliang Tang wrote: > > get_task_comm() copys the task's comm under the task_lock, it's safer > > than directly using memcpy(). > > > > Signed-off-by: Geliang Tang > > --- > > security/lsm_audit.c | 4 ++-- > > 1 file

Re: [PATCH 0/4] irda: move it to drivers/staging so we can delete it

On Mon, Aug 28, 2017 at 04:46:07PM -0700, Joe Perches wrote: > On Mon, 2017-08-28 at 16:42 -0700, David Miller wrote: > > From: Greg Kroah-Hartman > > Date: Sun, 27 Aug 2017 17:03:30 +0200 > > > > > The IRDA code has long been obsolete and broken.  So, to keep people

Re: [PATCH 0/4] irda: move it to drivers/staging so we can delete it

On Mon, Aug 28, 2017 at 04:46:07PM -0700, Joe Perches wrote: > On Mon, 2017-08-28 at 16:42 -0700, David Miller wrote: > > From: Greg Kroah-Hartman > > Date: Sun, 27 Aug 2017 17:03:30 +0200 > > > > > The IRDA code has long been obsolete and broken.  So, to keep people > > > from trying to use it,

Re: [PATCH 4.12 00/99] 4.12.10-stable review

On Mon, Aug 28, 2017 at 01:40:29PM -0600, Shuah Khan wrote: > On 08/28/2017 02:03 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.12.10 release. > > There are 99 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [PATCH 4.12 00/99] 4.12.10-stable review

On Mon, Aug 28, 2017 at 01:40:29PM -0600, Shuah Khan wrote: > On 08/28/2017 02:03 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.12.10 release. > > There are 99 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [PATCH 4.12 00/99] 4.12.10-stable review

On Mon, Aug 28, 2017 at 05:11:03PM -0700, Guenter Roeck wrote: > On 08/28/2017 01:03 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.12.10 release. > > There are 99 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [PATCH 4.12 00/99] 4.12.10-stable review

On Mon, Aug 28, 2017 at 05:11:03PM -0700, Guenter Roeck wrote: > On 08/28/2017 01:03 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.12.10 release. > > There are 99 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [PATCH] Revert "xhci: Limit USB2 port wake support for AMD Promontory hosts"

On Mon, Aug 28, 2017 at 6:14 PM, Mathias Nyman wrote: > On 28.08.2017 12:29, Greg KH wrote: >> >> On Tue, Aug 22, 2017 at 05:14:47PM +0800, Kai-Heng Feng wrote: >>> >>> This reverts commit dec08194ffeccfa1cf085906b53d301930eae18f. >>> >>> Commit dec08194ffec ("xhci:

[PATCH RESEND 2/2] dmaengine: sun6i: support V3s SoC variant

From: Icenowy Zheng Allwinner V3s has a DMA engine similar to the ones from A31, but with fewer channels and DRQs. Add support for it. Signed-off-by: Icenowy Zheng Acked-by: Chen-Yu Tsai Acked-by: Rob Herring ---

Re: [PATCH] Revert "xhci: Limit USB2 port wake support for AMD Promontory hosts"

On Mon, Aug 28, 2017 at 6:14 PM, Mathias Nyman wrote: > On 28.08.2017 12:29, Greg KH wrote: >> >> On Tue, Aug 22, 2017 at 05:14:47PM +0800, Kai-Heng Feng wrote: >>> >>> This reverts commit dec08194ffeccfa1cf085906b53d301930eae18f. >>> >>> Commit dec08194ffec ("xhci: Limit USB2 port wake support

[PATCH RESEND 2/2] dmaengine: sun6i: support V3s SoC variant

From: Icenowy Zheng Allwinner V3s has a DMA engine similar to the ones from A31, but with fewer channels and DRQs. Add support for it. Signed-off-by: Icenowy Zheng Acked-by: Chen-Yu Tsai Acked-by: Rob Herring --- Documentation/devicetree/bindings/dma/sun6i-dma.txt | 1 +

[PATCH RESEND 1/2] dmaengine: sun6i: make gate bit in sun8i's DMA engines a common quirk

From: Icenowy Zheng Originally we enable a special gate bit when the compatible indicates A23/33. But according to BSP sources and user manuals, more SoCs will need this gate bit. So make it a common quirk configured in the config struct. Signed-off-by: Icenowy Zheng

[PATCH RESEND 1/2] dmaengine: sun6i: make gate bit in sun8i's DMA engines a common quirk

From: Icenowy Zheng Originally we enable a special gate bit when the compatible indicates A23/33. But according to BSP sources and user manuals, more SoCs will need this gate bit. So make it a common quirk configured in the config struct. Signed-off-by: Icenowy Zheng Reviewed-by: Chen-Yu

[PATCH RESEND 0/2] Allwinner V3s DMA support

This is a dedicated patchset of Allwinner V3s DMA support, which used to be part of the audio codec support patchset. It's a derivation of the DMA part of v3 of the codec patchset. Icenowy Zheng (2): dmaengine: sun6i: make gate bit in sun8i's DMA engines a common quirk dmaengine: sun6i:

[PATCH RESEND 0/2] Allwinner V3s DMA support

This is a dedicated patchset of Allwinner V3s DMA support, which used to be part of the audio codec support patchset. It's a derivation of the DMA part of v3 of the codec patchset. Icenowy Zheng (2): dmaengine: sun6i: make gate bit in sun8i's DMA engines a common quirk dmaengine: sun6i:

Re: [PATCH v2 15/30] xfs: Define usercopy region in xfs_inode slab cache

On Mon, Aug 28, 2017 at 02:57:14PM -0700, Kees Cook wrote: > On Mon, Aug 28, 2017 at 2:49 PM, Darrick J. Wong > wrote: > > On Mon, Aug 28, 2017 at 02:34:56PM -0700, Kees Cook wrote: > >> From: David Windsor > >> > >> The XFS inline inode data, stored

Re: [PATCH v2 15/30] xfs: Define usercopy region in xfs_inode slab cache

On Mon, Aug 28, 2017 at 02:57:14PM -0700, Kees Cook wrote: > On Mon, Aug 28, 2017 at 2:49 PM, Darrick J. Wong > wrote: > > On Mon, Aug 28, 2017 at 02:34:56PM -0700, Kees Cook wrote: > >> From: David Windsor > >> > >> The XFS inline inode data, stored in struct xfs_inode_t field > >>

Re: [RFC 2/3] sched/fair: use util_est in LB

On Fri, Aug 25, 2017 at 3:50 PM, Patrick Bellasi wrote: > When the scheduler looks at the CPU utlization, the current PELT value > for a CPU is returned straight away. In certain scenarios this can have > undesired side effects on task placement. > > +/** > + *

Re: [RFC 2/3] sched/fair: use util_est in LB

On Fri, Aug 25, 2017 at 3:50 PM, Patrick Bellasi wrote: > When the scheduler looks at the CPU utlization, the current PELT value > for a CPU is returned straight away. In certain scenarios this can have > undesired side effects on task placement. > > +/** > + * cpu_util_est: estimated

Re: [PATCH net-next] hinic: don't build the module by default

From: Vitaly Kuznetsov Date: Mon, 28 Aug 2017 15:16:05 +0200 > We probably don't want to enable code supporting particular hardware by > default e.g. when someone does 'make defconfig'. Other ethernet modules > don't do it. > > Signed-off-by: Vitaly Kuznetsov

Re: [PATCH net-next] hinic: don't build the module by default

From: Vitaly Kuznetsov Date: Mon, 28 Aug 2017 15:16:05 +0200 > We probably don't want to enable code supporting particular hardware by > default e.g. when someone does 'make defconfig'. Other ethernet modules > don't do it. > > Signed-off-by: Vitaly Kuznetsov Applied, thanks.

Re: [PATCH net-next v2 00/10] net: dsa: add generic debugfs interface

From: Vivien Didelot Date: Mon, 28 Aug 2017 15:17:38 -0400 > This patch series adds a generic debugfs interface for the DSA > framework, so that all switch devices benefit from it, e.g. Marvell, > Broadcom, Microchip or any other DSA driver. I've been

Re: [PATCH net-next v2 00/10] net: dsa: add generic debugfs interface

From: Vivien Didelot Date: Mon, 28 Aug 2017 15:17:38 -0400 > This patch series adds a generic debugfs interface for the DSA > framework, so that all switch devices benefit from it, e.g. Marvell, > Broadcom, Microchip or any other DSA driver. I've been thinking this over and I agree with the

Re: [RFC 1/3] sched/fair: add util_est on top of PELT

Hi Patrick, On Fri, Aug 25, 2017 at 3:50 PM, Patrick Bellasi wrote: > The util_avg signal computed by PELT is too variable for some use-cases. > For example, a big task waking up after a long sleep period will have its > utilization almost completely decayed. This

Re: [RFC 1/3] sched/fair: add util_est on top of PELT

Hi Patrick, On Fri, Aug 25, 2017 at 3:50 PM, Patrick Bellasi wrote: > The util_avg signal computed by PELT is too variable for some use-cases. > For example, a big task waking up after a long sleep period will have its > utilization almost completely decayed. This introduces some latency before

Re: iov_iter_pipe warning.

On Mon, Aug 28, 2017 at 04:31:30PM -0400, Dave Jones wrote: > On Mon, Aug 07, 2017 at 04:18:18PM -0400, Dave Jones wrote: > > On Fri, Apr 28, 2017 at 06:20:25PM +0100, Al Viro wrote: > > > On Fri, Apr 28, 2017 at 12:50:24PM -0400, Dave Jones wrote: > > > > currently running

Re: iov_iter_pipe warning.

On Mon, Aug 28, 2017 at 04:31:30PM -0400, Dave Jones wrote: > On Mon, Aug 07, 2017 at 04:18:18PM -0400, Dave Jones wrote: > > On Fri, Apr 28, 2017 at 06:20:25PM +0100, Al Viro wrote: > > > On Fri, Apr 28, 2017 at 12:50:24PM -0400, Dave Jones wrote: > > > > currently running

Re: [PATCH] be2net: Fix some u16 fields appropriately

From: 严海双 Date: Tue, 29 Aug 2017 09:04:57 +0800 > The GET_TX_COMPL_BITS comes from amap_get which also returns a 32-bit value: It never returns a value with more than 16-bits of significance for this specific call. Please stop trying to be semantically clever

Re: [PATCH] be2net: Fix some u16 fields appropriately

From: 严海双 Date: Tue, 29 Aug 2017 09:04:57 +0800 > The GET_TX_COMPL_BITS comes from amap_get which also returns a 32-bit value: It never returns a value with more than 16-bits of significance for this specific call. Please stop trying to be semantically clever when arguing about this change.

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

Hi Shaohua, Today's linux-next merge of the md tree got a conflict in: drivers/md/raid5-ppl.c between commit: 74d46992e0d9 ("block: replace bi_bdev with a gendisk pointer and partitions index") from the block tree and commit: ddc088238cd6 ("md: Runtime support for multiple ppls")

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

Hi Shaohua, Today's linux-next merge of the md tree got a conflict in: drivers/md/raid5-ppl.c between commit: 74d46992e0d9 ("block: replace bi_bdev with a gendisk pointer and partitions index") from the block tree and commit: ddc088238cd6 ("md: Runtime support for multiple ppls")

[PATCH v6] FlexRM support in VFIO platform

This patchset primarily adds Broadcom FlexRM reset module for VFIO platform driver. The patches are based on Linux-4.13-rc3 and can also be found at flexrm-vfio-v6 branch of https://github.com/Broadcom/arm64-linux.git Changes since v5: - Make kconfig option VFIO_PLATFORM_BCMFLEXRM_RESET

[PATCH v6] FlexRM support in VFIO platform

This patchset primarily adds Broadcom FlexRM reset module for VFIO platform driver. The patches are based on Linux-4.13-rc3 and can also be found at flexrm-vfio-v6 branch of https://github.com/Broadcom/arm64-linux.git Changes since v5: - Make kconfig option VFIO_PLATFORM_BCMFLEXRM_RESET

[PATCH v6] vfio: platform: reset: Add Broadcom FlexRM reset module

This patch adds Broadcom FlexRM low-level reset for VFIO platform. It will do the following: 1. Disable/Deactivate each FlexRM ring 2. Flush each FlexRM ring The cleanup sequence for FlexRM rings is adapted from Broadcom FlexRM mailbox driver. Signed-off-by: Anup Patel

[PATCH v6] vfio: platform: reset: Add Broadcom FlexRM reset module

This patch adds Broadcom FlexRM low-level reset for VFIO platform. It will do the following: 1. Disable/Deactivate each FlexRM ring 2. Flush each FlexRM ring The cleanup sequence for FlexRM rings is adapted from Broadcom FlexRM mailbox driver. Signed-off-by: Anup Patel Reviewed-by: Oza Oza

Re: [PATCH] initramfs: Fix disabling of initramfs (and its compression)

On 08/28/2017 08:09 PM, Nicholas Piggin wrote: > On Mon, 28 Aug 2017 13:03:31 -0700 > Florian Fainelli wrote: > >> On 05/21/2017 07:46 PM, Nicholas Piggin wrote: >>> On Sat, 20 May 2017 20:33:35 -0700 >>> Florian Fainelli wrote: >>> Commit

Re: [PATCH] initramfs: Fix disabling of initramfs (and its compression)

On 08/28/2017 08:09 PM, Nicholas Piggin wrote: > On Mon, 28 Aug 2017 13:03:31 -0700 > Florian Fainelli wrote: > >> On 05/21/2017 07:46 PM, Nicholas Piggin wrote: >>> On Sat, 20 May 2017 20:33:35 -0700 >>> Florian Fainelli wrote: >>> Commit db2aa7fd15e8 ("initramfs: allow again choice

[PATCH v5 1/2] dt-bindings: i2c: Add Spreadtrum I2C controller documentation

This patch adds the binding documentation for Spreadtrum I2C controller device. Signed-off-by: Baolin Wang Acked-by: Rob Herring --- Changes since v4: - No updates. Changes since v3: - Add Ack from RobH. Changes since v2: - Change compatible

[PATCH v5 1/2] dt-bindings: i2c: Add Spreadtrum I2C controller documentation

This patch adds the binding documentation for Spreadtrum I2C controller device. Signed-off-by: Baolin Wang Acked-by: Rob Herring --- Changes since v4: - No updates. Changes since v3: - Add Ack from RobH. Changes since v2: - Change compatible strings to be SoC specific. Changes since v1:

[PATCH v5 2/2] i2c: Add Spreadtrum I2C controller driver

This patch adds the I2C controller driver for Spreadtrum SC9860 platform. Signed-off-by: Baolin Wang Reviewed-by: Andy Shevchenko --- Changes since v4: - Remove dump registers function. - Change 'unsigned int' to 'u32' type. - Invert ack

[PATCH v5 2/2] i2c: Add Spreadtrum I2C controller driver

This patch adds the I2C controller driver for Spreadtrum SC9860 platform. Signed-off-by: Baolin Wang Reviewed-by: Andy Shevchenko --- Changes since v4: - Remove dump registers function. - Change 'unsigned int' to 'u32' type. - Invert ack logic to make it clear. - Modify some comments and

Re: [PATCH] libnvdimm: clean up command definitions

On Mon, Aug 28, 2017 at 6:03 PM, Yasunori Goto wrote: >> On Mon, Aug 28, 2017 at 1:50 PM, Jerry Hoemann wrote: >> > >> > On Mon, Aug 28, 2017 at 08:45:32AM -0700, Dan Williams wrote: >> >> Remove the command payloads that do not have an associated

Re: [PATCH] libnvdimm: clean up command definitions

On Mon, Aug 28, 2017 at 6:03 PM, Yasunori Goto wrote: >> On Mon, Aug 28, 2017 at 1:50 PM, Jerry Hoemann wrote: >> > >> > On Mon, Aug 28, 2017 at 08:45:32AM -0700, Dan Williams wrote: >> >> Remove the command payloads that do not have an associated libnvdimm >> >> ioctl. I.e. remove the payloads

Re: [PATCH v15 4/5] mm: support reporting free page blocks

On 08/28/2017 09:33 PM, Michal Hocko wrote: On Mon 28-08-17 18:08:32, Wei Wang wrote: This patch adds support to walk through the free page blocks in the system and report them via a callback function. Some page blocks may leave the free list after zone->lock is released, so it is the caller's

Re: [PATCH v15 4/5] mm: support reporting free page blocks

On 08/28/2017 09:33 PM, Michal Hocko wrote: On Mon 28-08-17 18:08:32, Wei Wang wrote: This patch adds support to walk through the free page blocks in the system and report them via a callback function. Some page blocks may leave the free list after zone->lock is released, so it is the caller's

Re: [PATCH] initramfs: Fix disabling of initramfs (and its compression)

On Mon, 28 Aug 2017 13:03:31 -0700 Florian Fainelli wrote: > On 05/21/2017 07:46 PM, Nicholas Piggin wrote: > > On Sat, 20 May 2017 20:33:35 -0700 > > Florian Fainelli wrote: > > > >> Commit db2aa7fd15e8 ("initramfs: allow again choice of the

Re: [PATCH] initramfs: Fix disabling of initramfs (and its compression)

On Mon, 28 Aug 2017 13:03:31 -0700 Florian Fainelli wrote: > On 05/21/2017 07:46 PM, Nicholas Piggin wrote: > > On Sat, 20 May 2017 20:33:35 -0700 > > Florian Fainelli wrote: > > > >> Commit db2aa7fd15e8 ("initramfs: allow again choice of the embedded > >> initram compression algorithm")

Re: [PATCH v15 3/5] virtio-balloon: VIRTIO_BALLOON_F_SG

On 08/29/2017 02:03 AM, Michael S. Tsirkin wrote: On Mon, Aug 28, 2017 at 06:08:31PM +0800, Wei Wang wrote: Add a new feature, VIRTIO_BALLOON_F_SG, which enables the transfer of balloon (i.e. inflated/deflated) pages using scatter-gather lists to the host. The implementation of the previous

Re: [PATCH v15 3/5] virtio-balloon: VIRTIO_BALLOON_F_SG

On 08/29/2017 02:03 AM, Michael S. Tsirkin wrote: On Mon, Aug 28, 2017 at 06:08:31PM +0800, Wei Wang wrote: Add a new feature, VIRTIO_BALLOON_F_SG, which enables the transfer of balloon (i.e. inflated/deflated) pages using scatter-gather lists to the host. The implementation of the previous

Re: [RFC PATCH v5 0/5] vfio-pci: Add support for mmapping MSI-X table

On 21/08/17 12:47, Alexey Kardashevskiy wrote: > Folks, > > Ok, people did talk, exchanged ideas, lovely :) What happens now? Do I > repost this or go back to PCI bus flags or something else? Thanks. Anyone, any help? How do we proceed with this? Thanks. > > > > On 14/08/17 19:45, Alexey

Re: [RFC PATCH v5 0/5] vfio-pci: Add support for mmapping MSI-X table

On 21/08/17 12:47, Alexey Kardashevskiy wrote: > Folks, > > Ok, people did talk, exchanged ideas, lovely :) What happens now? Do I > repost this or go back to PCI bus flags or something else? Thanks. Anyone, any help? How do we proceed with this? Thanks. > > > > On 14/08/17 19:45, Alexey

Re: [PATCH v4 3/3] ARM: dts: exynos: Remove the display-timing and delay from rinato dts

Hi Krzysztof, The driver has been merged into exynos-drm-misc. Could you please check this patch(3/3). Best regards, Hoegeun On 07/13/2017 11:20 AM, Hoegeun Kwon wrote: The display-timing and delay are included in the panel driver. So it should be removed in dts. Signed-off-by: Hoegeun Kwon

Re: [PATCH v4 3/3] ARM: dts: exynos: Remove the display-timing and delay from rinato dts

Hi Krzysztof, The driver has been merged into exynos-drm-misc. Could you please check this patch(3/3). Best regards, Hoegeun On 07/13/2017 11:20 AM, Hoegeun Kwon wrote: The display-timing and delay are included in the panel driver. So it should be removed in dts. Signed-off-by: Hoegeun Kwon

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

On Tue, Aug 29, 2017 at 09:10:56AM +1000, Stephen Rothwell wrote: > Hi Vinod, > > Commit > > 966e5e01f420 ("dmaengine: altera: Use macros instead of structs to describe > the registers") > > is missing a Signed-off-by from its committer. Oops, missed fixing that up while running with -i :(.

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

On Tue, Aug 29, 2017 at 09:10:56AM +1000, Stephen Rothwell wrote: > Hi Vinod, > > Commit > > 966e5e01f420 ("dmaengine: altera: Use macros instead of structs to describe > the registers") > > is missing a Signed-off-by from its committer. Oops, missed fixing that up while running with -i :(.

[PATCH] docs: highres: fix broken urls

Some urls is invalid. I find alternative urls. Signed-off-by: stephen lu --- Documentation/timers/highres.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/timers/highres.txt b/Documentation/timers/highres.txt index e878997..9d88f67

[PATCH] docs: highres: fix broken urls

Some urls is invalid. I find alternative urls. Signed-off-by: stephen lu --- Documentation/timers/highres.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/timers/highres.txt b/Documentation/timers/highres.txt index e878997..9d88f67 100644 ---

RE: [PATCH] vsock: only load vmci transport on VMware hypervisor by default

> From: Dexuan Cui > Sent: Tuesday, August 22, 2017 21:21 > > ... > > ... > > The only problem here would be the potential for a guest and a host app > to > > have a conflict wrt port numbers, even though they would be able to > > operate fine, if restricted to their appropriate transport. > > > >

RE: [PATCH] vsock: only load vmci transport on VMware hypervisor by default

> From: Dexuan Cui > Sent: Tuesday, August 22, 2017 21:21 > > ... > > ... > > The only problem here would be the potential for a guest and a host app > to > > have a conflict wrt port numbers, even though they would be able to > > operate fine, if restricted to their appropriate transport. > > > >

Re: module: Remove const attribute from alias for MODULE_DEVICE_TABLE

On 2017-08-28 10:41, Kees Cook wrote: > On Mon, Aug 28, 2017 at 10:38 AM, Nick Desaulniers > wrote: >> I think Kees' proposal is a better solution; rather than require all >> usage of device table to remember to add const, have the macro add it >> for all users.

Re: module: Remove const attribute from alias for MODULE_DEVICE_TABLE

On 2017-08-28 10:41, Kees Cook wrote: > On Mon, Aug 28, 2017 at 10:38 AM, Nick Desaulniers > wrote: >> I think Kees' proposal is a better solution; rather than require all >> usage of device table to remember to add const, have the macro add it >> for all users. Otherwise if you require caller's

linux-next: manual merge of the net-next tree with the net tree

Hi all, Today's linux-next merge of the net-next tree got a conflict in: drivers/net/ethernet/marvell/mvpp2.c between commit: 4c2286826451 ("net: mvpp2: fix the mac address used when using PPv2.2") from the net tree and commits: 09f8397553a2 ("net: mvpp2: introduce per-port nrxqs/ntxqs

linux-next: manual merge of the net-next tree with the net tree

Hi all, Today's linux-next merge of the net-next tree got a conflict in: drivers/net/ethernet/marvell/mvpp2.c between commit: 4c2286826451 ("net: mvpp2: fix the mac address used when using PPv2.2") from the net tree and commits: 09f8397553a2 ("net: mvpp2: introduce per-port nrxqs/ntxqs

Re: [PATCH v3 4/5] input: Add MediaTek PMIC keys support

On Mon, 2017-08-28 at 09:57 -0700, Dmitry Torokhov wrote: > Hi Chen, > > On Fri, Aug 25, 2017 at 02:32:32PM +0800, Chen Zhong wrote: > > +static int mtk_pmic_key_setup(struct mtk_pmic_keys *keys, > > + struct pmic_keys_info *info) > > +{ > > + int ret; > > + > > + info->keys = keys;

Re: [PATCH v3 4/5] input: Add MediaTek PMIC keys support

On Mon, 2017-08-28 at 09:57 -0700, Dmitry Torokhov wrote: > Hi Chen, > > On Fri, Aug 25, 2017 at 02:32:32PM +0800, Chen Zhong wrote: > > +static int mtk_pmic_key_setup(struct mtk_pmic_keys *keys, > > + struct pmic_keys_info *info) > > +{ > > + int ret; > > + > > + info->keys = keys;

[PATCH v7 07/11] sparc64: optimized struct page zeroing

Add an optimized mm_zero_struct_page(), so struct page's are zeroed without calling memset(). We do eight to ten regular stores based on the size of struct page. Compiler optimizes out the conditions of switch() statement. SPARC-M6 with 15T of memory, single thread performance:

[PATCH v7 07/11] sparc64: optimized struct page zeroing

Add an optimized mm_zero_struct_page(), so struct page's are zeroed without calling memset(). We do eight to ten regular stores based on the size of struct page. Compiler optimizes out the conditions of switch() statement. SPARC-M6 with 15T of memory, single thread performance:

[PATCH v7 00/11] complete deferred page initialization

Changelog: v7 - v6 - Addressed comments from Michal Hocko - memblock_discard() patch was removed from this series and integrated separately - Fixed bug reported by kbuild test robot new patch: mm: zero reserved and unavailable struct pages - Removed patch x86/mm: reserve only exiting low

[PATCH v7 00/11] complete deferred page initialization

Changelog: v7 - v6 - Addressed comments from Michal Hocko - memblock_discard() patch was removed from this series and integrated separately - Fixed bug reported by kbuild test robot new patch: mm: zero reserved and unavailable struct pages - Removed patch x86/mm: reserve only exiting low

[PATCH v7 09/11] x86/kasan: explicitly zero kasan shadow memory

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 memory does not go through struct page initialization path. Signed-off-by: Pavel Tatashin

[PATCH v7 09/11] x86/kasan: explicitly zero kasan shadow memory

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 memory does not go through struct page initialization path. Signed-off-by: Pavel Tatashin

[PATCH v7 04/11] sparc64: simplify vmemmap_populate

Remove duplicating code by using common functions vmemmap_pud_populate and vmemmap_pgd_populate. Signed-off-by: Pavel Tatashin Reviewed-by: Steven Sistare Reviewed-by: Daniel Jordan Reviewed-by: Bob Picco

[PATCH v7 04/11] sparc64: simplify vmemmap_populate

Remove duplicating code by using common functions vmemmap_pud_populate and vmemmap_pgd_populate. Signed-off-by: Pavel Tatashin Reviewed-by: Steven Sistare Reviewed-by: Daniel Jordan Reviewed-by: Bob Picco --- arch/sparc/mm/init_64.c | 23 ++- 1 file changed, 6

[PATCH v7 08/11] mm: zero reserved and unavailable struct pages

Some memory is reserved but unavailable: not present in memblock.memory (because not backed by physical pages), but present in memblock.reserved. Such memory has backing struct pages, but they are not initialized by going through __init_single_page(). In some cases these struct pages are accessed

[PATCH v7 08/11] mm: zero reserved and unavailable struct pages

Some memory is reserved but unavailable: not present in memblock.memory (because not backed by physical pages), but present in memblock.reserved. Such memory has backing struct pages, but they are not initialized by going through __init_single_page(). In some cases these struct pages are accessed

[PATCH v7 10/11] arm64/kasan: explicitly zero kasan shadow memory

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 memory does not go through struct page initialization path. Signed-off-by: Pavel Tatashin

[PATCH v7 02/11] sparc64/mm: setting fields in deferred pages

Without deferred struct page feature (CONFIG_DEFERRED_STRUCT_PAGE_INIT), flags and other fields in "struct page"es are never changed prior to first initializing struct pages by going through __init_single_page(). With deferred struct page feature enabled there is a case where we set some fields

  1   2   3   4   5   6   7   8   9   10   >