Re: Sleeping BUG in khugepaged for i586

On Thu, 8 Jun 2017, Michal Hocko wrote: > I would just pull the cond_resched out of __collapse_huge_page_copy > right after pte_unmap. But I am not really sure why this cond_resched is > really needed because the changelog of the patch which adds is is quite > terse on details. I'm not sure what

Re: Sleeping BUG in khugepaged for i586

On Thu, 8 Jun 2017, Michal Hocko wrote: > I would just pull the cond_resched out of __collapse_huge_page_copy > right after pte_unmap. But I am not really sure why this cond_resched is > really needed because the changelog of the patch which adds is is quite > terse on details. I'm not sure what

[git pull] IOMMU Fixes for Linux v4.12-rc4

Hi Linus, The following changes since commit 5ed02dbb497422bf225783f46e6eadd237d23d6b: Linux 4.12-rc3 (2017-05-28 17:20:53 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fixes-v4.12-rc4 for you to fetch changes up to

[git pull] IOMMU Fixes for Linux v4.12-rc4

Hi Linus, The following changes since commit 5ed02dbb497422bf225783f46e6eadd237d23d6b: Linux 4.12-rc3 (2017-05-28 17:20:53 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fixes-v4.12-rc4 for you to fetch changes up to

Re: [PATCH v4 6/7] ARM: dts: meson8: switch to new bindings for UART nodes

Hi Neil, On Fri, Jun 9, 2017 at 11:49 AM, Neil Armstrong wrote: > Switch to the stable UART bindings by adding a XTAL node and using the > proper compatible strings. unfortunately this won't apply now that Kevin has merged my "ARM: dts: meson8: add and use the real clock

Re: [PATCH v4 6/7] ARM: dts: meson8: switch to new bindings for UART nodes

Hi Neil, On Fri, Jun 9, 2017 at 11:49 AM, Neil Armstrong wrote: > Switch to the stable UART bindings by adding a XTAL node and using the > proper compatible strings. unfortunately this won't apply now that Kevin has merged my "ARM: dts: meson8: add and use the real clock controller" on the other

Re: [PATCH] thermal: int340x: check for sensor when PTYP is missing

On Sat, Jun 10, 2017 at 1:23 AM, Srinivas Pandruvada wrote: > On Wed, 2017-06-07 at 13:55 +0300, Andy Shevchenko wrote: >> On Wed, Jun 7, 2017 at 2:00 AM, Srinivas Pandruvada >> wrote: >> > This change checks for the

Re: [PATCH] thermal: int340x: check for sensor when PTYP is missing

On Sat, Jun 10, 2017 at 1:23 AM, Srinivas Pandruvada wrote: > On Wed, 2017-06-07 at 13:55 +0300, Andy Shevchenko wrote: >> On Wed, Jun 7, 2017 at 2:00 AM, Srinivas Pandruvada >> wrote: >> > This change checks for the presence of _TMP method and if present, >> > then >> > treats this device as a

[patch v2 -mm] mm, hugetlb: schedule when potentially allocating many hugepages

A few hugetlb allocators loop while calling the page allocator and can potentially prevent rescheduling if the page allocator slowpath is not utilized. Conditionally schedule when large numbers of hugepages can be allocated. Signed-off-by: David Rientjes --- Based on -mm

[patch v2 -mm] mm, hugetlb: schedule when potentially allocating many hugepages

A few hugetlb allocators loop while calling the page allocator and can potentially prevent rescheduling if the page allocator slowpath is not utilized. Conditionally schedule when large numbers of hugepages can be allocated. Signed-off-by: David Rientjes --- Based on -mm only to prevent merge

Re: [PATCH v8 14/34] ARM: dts: imx6-sabreauto: add the ADV7180 video decoder

On 06/09/2017 02:38 PM, Pavel Machek wrote: On Thu 2017-06-08 13:36:12, Steve Longerbeam wrote: On 06/08/2017 01:25 PM, Tim Harvey wrote: Steve, You need to remove the fim node now that you've moved this to V4L2 controls. Yep, I caught this just after sending the v8 patchset. I'll

Re: [PATCH v8 14/34] ARM: dts: imx6-sabreauto: add the ADV7180 video decoder

On 06/09/2017 02:38 PM, Pavel Machek wrote: On Thu 2017-06-08 13:36:12, Steve Longerbeam wrote: On 06/08/2017 01:25 PM, Tim Harvey wrote: Steve, You need to remove the fim node now that you've moved this to V4L2 controls. Yep, I caught this just after sending the v8 patchset. I'll

Re: [patch -mm] mm, hugetlb: schedule when potentially allocating many hugepages

On Wed, 7 Jun 2017, Mike Kravetz wrote: > > @@ -2364,6 +2366,7 @@ static unsigned long set_max_huge_pages(struct hstate > > *h, unsigned long count, > > ret = alloc_fresh_gigantic_page(h, nodes_allowed); > > else > > ret =

Re: [patch -mm] mm, hugetlb: schedule when potentially allocating many hugepages

On Wed, 7 Jun 2017, Mike Kravetz wrote: > > @@ -2364,6 +2366,7 @@ static unsigned long set_max_huge_pages(struct hstate > > *h, unsigned long count, > > ret = alloc_fresh_gigantic_page(h, nodes_allowed); > > else > > ret =

Re: [PATCH] mm: Drop useless local parameters of register_one_node()

On Thu, 8 Jun 2017, Dou Liyang wrote: > ... initializes local parameters "p_node" & "parent" for > register_node(). > > But, register_node() does not use them. > > Remove the related code of "parent" node, cleanup register_one_node() > and register_node(). > > [Test in Qemu by 4 hotpluggable

Re: [PATCH] mm: Drop useless local parameters of register_one_node()

On Thu, 8 Jun 2017, Dou Liyang wrote: > ... initializes local parameters "p_node" & "parent" for > register_node(). > > But, register_node() does not use them. > > Remove the related code of "parent" node, cleanup register_one_node() > and register_node(). > > [Test in Qemu by 4 hotpluggable

[PATCH] ARM: OMAP: PM: stop early on systems without twl

Motorola Droid 4 has an OMAP4, but no TWL6030. It currently complains verbosely about this during boot: twl: not initialized twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660 twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660

[PATCH] ARM: OMAP: PM: stop early on systems without twl

Motorola Droid 4 has an OMAP4, but no TWL6030. It currently complains verbosely about this during boot: twl: not initialized twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660 twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660

Re: [PATCH 1/4] dt-bindings: tps65217: Update binding documentation.

Hello Rob, 2017-06-09 16:03 GMT+02:00 Rob Herring : > On Wed, Jun 07, 2017 at 12:32:39PM +0200, Enric Balletbo i Serra wrote: >> This patch adds a new binding documentation for the TPS65217 MFD and >> updates the documentation for all the sub-devices in accordance to get >> each

Re: [PATCH 1/4] dt-bindings: tps65217: Update binding documentation.

Hello Rob, 2017-06-09 16:03 GMT+02:00 Rob Herring : > On Wed, Jun 07, 2017 at 12:32:39PM +0200, Enric Balletbo i Serra wrote: >> This patch adds a new binding documentation for the TPS65217 MFD and >> updates the documentation for all the sub-devices in accordance to get >> each individual

Re: [PATCH] thermal: int340x: check for sensor when PTYP is missing

On Wed, 2017-06-07 at 13:55 +0300, Andy Shevchenko wrote: > On Wed, Jun 7, 2017 at 2:00 AM, Srinivas Pandruvada > wrote: > > > > For INT3403 sensor PTYP field is mandatory. But some platforms > > didn't > > have this field for sensors. This cause load failure

Re: [PATCH] thermal: int340x: check for sensor when PTYP is missing

On Wed, 2017-06-07 at 13:55 +0300, Andy Shevchenko wrote: > On Wed, Jun 7, 2017 at 2:00 AM, Srinivas Pandruvada > wrote: > > > > For INT3403 sensor PTYP field is mandatory. But some platforms > > didn't > > have this field for sensors. This cause load failure for int3403 > > driver. > > > >

Re: [PATCH 4/7] iommu: Add driver-not-bound notification

On Fri, Jun 09, 2017 at 03:59:59PM -0600, Alex Williamson wrote: > The driver core supports a BUS_NOTIFY_DRIVER_NOT_BOUND notification > sent if a driver fails to bind to a device. Extend IOMMU group > notifications to include a version of this. > > Signed-off-by: Alex Williamson

Re: [PATCH 4/7] iommu: Add driver-not-bound notification

On Fri, Jun 09, 2017 at 03:59:59PM -0600, Alex Williamson wrote: > The driver core supports a BUS_NOTIFY_DRIVER_NOT_BOUND notification > sent if a driver fails to bind to a device. Extend IOMMU group > notifications to include a version of this. > > Signed-off-by: Alex Williamson > Cc: Joerg

RE: [PATCH v1 3/3] ACPI / PMIC: Add TI PMIC TPS68470 operation region driver

Hi Hans, > -Original Message- > From: Hans de Goede [mailto:hdego...@redhat.com] > Sent: Tuesday, June 06, 2017 8:22 AM > To: Andy Shevchenko ; Mani, Rajmohan > > Cc: linux-kernel@vger.kernel.org; linux-g...@vger.kernel.org; linux- >

RE: [PATCH v1 3/3] ACPI / PMIC: Add TI PMIC TPS68470 operation region driver

Hi Hans, > -Original Message- > From: Hans de Goede [mailto:hdego...@redhat.com] > Sent: Tuesday, June 06, 2017 8:22 AM > To: Andy Shevchenko ; Mani, Rajmohan > > Cc: linux-kernel@vger.kernel.org; linux-g...@vger.kernel.org; linux- > a...@vger.kernel.org; Lee Jones ; Linus Walleij > ;

RE: [PATCH v1 3/3] ACPI / PMIC: Add TI PMIC TPS68470 operation region driver

Hi Andy, Thanks for the reviews and patience. > -Original Message- > From: Andy Shevchenko [mailto:andy.shevche...@gmail.com] > Sent: Tuesday, June 06, 2017 7:24 AM > To: Mani, Rajmohan ; Hans de Goede > > Cc: linux-kernel@vger.kernel.org;

RE: [PATCH v1 3/3] ACPI / PMIC: Add TI PMIC TPS68470 operation region driver

Hi Andy, Thanks for the reviews and patience. > -Original Message- > From: Andy Shevchenko [mailto:andy.shevche...@gmail.com] > Sent: Tuesday, June 06, 2017 7:24 AM > To: Mani, Rajmohan ; Hans de Goede > > Cc: linux-kernel@vger.kernel.org; linux-g...@vger.kernel.org; linux- >

Re: [PATCH] l2tp: cast l2tp traffic counter to unsigned

On Fri, 9 Jun 2017 16:29:47 +0200 Dominik Heidler wrote: > This fixes a counter problem on 32bit systems: > When the rx_bytes counter reached 2 GiB, it jumpd to (2^64 Bytes - 2GiB) > Bytes. > > rtnl_link_stats64 has __u64 type and atomic_long_read returns > atomic_long_t

Re: [PATCH] l2tp: cast l2tp traffic counter to unsigned

On Fri, 9 Jun 2017 16:29:47 +0200 Dominik Heidler wrote: > This fixes a counter problem on 32bit systems: > When the rx_bytes counter reached 2 GiB, it jumpd to (2^64 Bytes - 2GiB) > Bytes. > > rtnl_link_stats64 has __u64 type and atomic_long_read returns > atomic_long_t which is signed. Due

RE: [PATCH v1 1/3] mfd: Add new mfd device TPS68470

Hi Andy, > On Tue, Jun 06, 2017 at 03:59:49PM +0300, Andy Shevchenko wrote: > > On Tue, Jun 6, 2017 at 2:55 PM, Rajmohan Mani > wrote: > > > The TPS68470 device is an advanced power management unit that powers > > > a Compact Camera Module (CCM), generates clocks for

RE: [PATCH v1 1/3] mfd: Add new mfd device TPS68470

Hi Andy, > On Tue, Jun 06, 2017 at 03:59:49PM +0300, Andy Shevchenko wrote: > > On Tue, Jun 6, 2017 at 2:55 PM, Rajmohan Mani > wrote: > > > The TPS68470 device is an advanced power management unit that powers > > > a Compact Camera Module (CCM), generates clocks for image sensors, > > > drives

RE: [PATCH v1 1/3] mfd: Add new mfd device TPS68470

Hi Andy, Thanks for the reviews and patience. > -Original Message- > From: Andy Shevchenko [mailto:andy.shevche...@gmail.com] > Sent: Tuesday, June 06, 2017 6:00 AM > To: Mani, Rajmohan > Cc: linux-kernel@vger.kernel.org; linux-g...@vger.kernel.org; linux- >

RE: [PATCH v1 1/3] mfd: Add new mfd device TPS68470

Hi Andy, Thanks for the reviews and patience. > -Original Message- > From: Andy Shevchenko [mailto:andy.shevche...@gmail.com] > Sent: Tuesday, June 06, 2017 6:00 AM > To: Mani, Rajmohan > Cc: linux-kernel@vger.kernel.org; linux-g...@vger.kernel.org; linux- > a...@vger.kernel.org; Lee

Re: [PATCH 06/10] fpga manager: Add altera-ps-spi driver for Altera FPGAs

On Friday, June 9, 2017 3:18:40 PM PDT Anatolij Gustschin wrote: > On Fri, 9 Jun 2017 11:51:12 +0200 > Greg Kroah-Hartman gre...@linuxfoundation.org wrote: > ... > > >I get the following build error with this patch: > > > >ERROR: "__spi_register_driver" [drivers/fpga/altera-ps-spi.ko] undefined!

Re: [PATCH 06/10] fpga manager: Add altera-ps-spi driver for Altera FPGAs

On Friday, June 9, 2017 3:18:40 PM PDT Anatolij Gustschin wrote: > On Fri, 9 Jun 2017 11:51:12 +0200 > Greg Kroah-Hartman gre...@linuxfoundation.org wrote: > ... > > >I get the following build error with this patch: > > > >ERROR: "__spi_register_driver" [drivers/fpga/altera-ps-spi.ko] undefined!

RE: [PATCH v1 1/3] mfd: Add new mfd device TPS68470

Hi Heikki, Thanks for the reviews and patience. > -Original Message- > From: Heikki Krogerus [mailto:heikki.kroge...@linux.intel.com] > Sent: Tuesday, June 06, 2017 5:49 AM > To: Mani, Rajmohan > Cc: linux-kernel@vger.kernel.org; linux-g...@vger.kernel.org;

RE: [PATCH v1 1/3] mfd: Add new mfd device TPS68470

Hi Heikki, Thanks for the reviews and patience. > -Original Message- > From: Heikki Krogerus [mailto:heikki.kroge...@linux.intel.com] > Sent: Tuesday, June 06, 2017 5:49 AM > To: Mani, Rajmohan > Cc: linux-kernel@vger.kernel.org; linux-g...@vger.kernel.org; linux- >

[PATCH 7/7] vfio: Use driver_override to avert binding to compromising drivers

If a device is bound to a non-vfio, non-whitelisted driver while a group is in use, then the integrity of the group is compromised and will result in hitting a BUG_ON. This code tries to avoid this case by mangling driver_override to force a no-match for the driver. The driver-core will either

[PATCH 7/7] vfio: Use driver_override to avert binding to compromising drivers

If a device is bound to a non-vfio, non-whitelisted driver while a group is in use, then the integrity of the group is compromised and will result in hitting a BUG_ON. This code tries to avoid this case by mangling driver_override to force a no-match for the driver. The driver-core will either

[PATCH 3/7] vfio: New external user group/file match

At the point where the kvm-vfio pseudo device wants to release its vfio group reference, we can't always acquire a new reference to make that happen. The group can be in a state where we wouldn't allow a new reference to be added. This new helper function allows a caller to match a file to a

[PATCH 3/7] vfio: New external user group/file match

At the point where the kvm-vfio pseudo device wants to release its vfio group reference, we can't always acquire a new reference to make that happen. The group can be in a state where we wouldn't allow a new reference to be added. This new helper function allows a caller to match a file to a

[PATCH 6/7] vfio: Register pci, platform, amba, and mdev bus drivers

Hook into vfio bus driver register/unregister support. Signed-off-by: Alex Williamson Cc: Baptiste Reynal Cc: Kirti Wankhede Cc: Eric Auger --- drivers/vfio/mdev/vfio_mdev.c |

[PATCH 5/7] vfio: Create interface for vfio bus drivers to register

Generally we don't know about vfio bus drivers until a device is added to the vfio-core with vfio_add_group_dev(), this optional registration with vfio_register_bus_driver() allows vfio-core to track known drivers. Our current use for this information is to know whether a driver is vfio

[PATCH 6/7] vfio: Register pci, platform, amba, and mdev bus drivers

Hook into vfio bus driver register/unregister support. Signed-off-by: Alex Williamson Cc: Baptiste Reynal Cc: Kirti Wankhede Cc: Eric Auger --- drivers/vfio/mdev/vfio_mdev.c | 13 - drivers/vfio/pci/vfio_pci.c |7 +++ drivers/vfio/platform/vfio_amba.c

[PATCH 5/7] vfio: Create interface for vfio bus drivers to register

Generally we don't know about vfio bus drivers until a device is added to the vfio-core with vfio_add_group_dev(), this optional registration with vfio_register_bus_driver() allows vfio-core to track known drivers. Our current use for this information is to know whether a driver is vfio

[PATCH 4/7] iommu: Add driver-not-bound notification

The driver core supports a BUS_NOTIFY_DRIVER_NOT_BOUND notification sent if a driver fails to bind to a device. Extend IOMMU group notifications to include a version of this. Signed-off-by: Alex Williamson Cc: Joerg Roedel --- drivers/iommu/iommu.c

[PATCH 4/7] iommu: Add driver-not-bound notification

The driver core supports a BUS_NOTIFY_DRIVER_NOT_BOUND notification sent if a driver fails to bind to a device. Extend IOMMU group notifications to include a version of this. Signed-off-by: Alex Williamson Cc: Joerg Roedel --- drivers/iommu/iommu.c |2 ++ include/linux/iommu.h |1 + 2

[PATCH 2/7] kvm-vfio: Decouple only when we match a group

Unset-KVM and decrement-assignment only when we find the group in our list. Otherwise we can get out of sync if the user triggers this for groups that aren't currently on our list. Signed-off-by: Alex Williamson Cc: Paolo Bonzini ---

[PATCH 1/7] vfio: Fix group release deadlock

If vfio_iommu_group_notifier() acquires a group reference and that reference becomes the last reference to the group, then vfio_group_put introduces a deadlock code path where we're trying to unregister from the iommu notifier chain from within a callout of that chain. Use a work_struct to

[PATCH 2/7] kvm-vfio: Decouple only when we match a group

Unset-KVM and decrement-assignment only when we find the group in our list. Otherwise we can get out of sync if the user triggers this for groups that aren't currently on our list. Signed-off-by: Alex Williamson Cc: Paolo Bonzini --- virt/kvm/vfio.c |6 ++ 1 file changed, 2

[PATCH 1/7] vfio: Fix group release deadlock

If vfio_iommu_group_notifier() acquires a group reference and that reference becomes the last reference to the group, then vfio_group_put introduces a deadlock code path where we're trying to unregister from the iommu notifier chain from within a callout of that chain. Use a work_struct to

[PATCH 0/7] vfio: Fix release ordering races and use driver_override

VM hotplug testing reveals a number of races in the vfio device, group, container shutdown path, some attributed to libvirt's ask/take unplug behavior and some long standing with groups potentially composed of multiple devices, where each device can be independently bound to drivers. Libvirt's

[PATCH 0/7] vfio: Fix release ordering races and use driver_override

VM hotplug testing reveals a number of races in the vfio device, group, container shutdown path, some attributed to libvirt's ask/take unplug behavior and some long standing with groups potentially composed of multiple devices, where each device can be independently bound to drivers. Libvirt's

Re: [PATCH 08/17] dts: include documentation for the RISC-V interrupt controllers

Ugh. Clicked reply without being done writing the reply! On Thu, Jun 8, 2017 at 3:52 AM, Mark Rutland wrote: > Edge vs level, active high vs active low. Typically some of these are > programmable, and are described as flags in the interrupt-specifier. > > See the examples

Re: [PATCH 08/17] dts: include documentation for the RISC-V interrupt controllers

Ugh. Clicked reply without being done writing the reply! On Thu, Jun 8, 2017 at 3:52 AM, Mark Rutland wrote: > Edge vs level, active high vs active low. Typically some of these are > programmable, and are described as flags in the interrupt-specifier. > > See the examples in: > >

Re: [PATCH 15/16] platform/x86: wmi-mof: New driver to expose embedded WMI MOF metadata

On Friday 09 June 2017 17:46:12 mario.limoncie...@dell.com wrote: > > -Original Message- > > From: Pali Rohár [mailto:pali.ro...@gmail.com] > > Sent: Wednesday, June 7, 2017 3:50 PM > > To: Limonciello, Mario > > Cc: l...@amacapital.net; dvh...@infradead.org;

Re: [PATCH 15/16] platform/x86: wmi-mof: New driver to expose embedded WMI MOF metadata

On Friday 09 June 2017 17:46:12 mario.limoncie...@dell.com wrote: > > -Original Message- > > From: Pali Rohár [mailto:pali.ro...@gmail.com] > > Sent: Wednesday, June 7, 2017 3:50 PM > > To: Limonciello, Mario > > Cc: l...@amacapital.net; dvh...@infradead.org; platform-driver- > >

[PATCH] net: aquantia: atlantic: remove declaration of hw_atl_utils_hw_set_power

This function is not defined, so no need to declare it. As I don't have the hardware, I'd be very pleased if someone may test this patch. Signed-off-by: Philippe Reynes --- .../aquantia/atlantic/hw_atl/hw_atl_utils.h|3 --- 1 files changed, 0 insertions(+), 3

[PATCH] net: aquantia: atlantic: remove declaration of hw_atl_utils_hw_set_power

This function is not defined, so no need to declare it. As I don't have the hardware, I'd be very pleased if someone may test this patch. Signed-off-by: Philippe Reynes --- .../aquantia/atlantic/hw_atl/hw_atl_utils.h|3 --- 1 files changed, 0 insertions(+), 3 deletions(-) diff

Re: [PATCH] mtd: nand: fsl_ifc: remove unused variable

On Fri 2017-06-09 12:47:43, Arnd Bergmann wrote: > This one was accidentally introduced without any references, > and it causes a harmless warning: > > drivers/mtd/nand/fsl_ifc_nand.c: In function 'fsl_ifc_read_page': > drivers/mtd/nand/fsl_ifc_nand.c:696:7: error: unused variable 'res' >

Re: [PATCH] mtd: nand: fsl_ifc: remove unused variable

On Fri 2017-06-09 12:47:43, Arnd Bergmann wrote: > This one was accidentally introduced without any references, > and it causes a harmless warning: > > drivers/mtd/nand/fsl_ifc_nand.c: In function 'fsl_ifc_read_page': > drivers/mtd/nand/fsl_ifc_nand.c:696:7: error: unused variable 'res' >

Re: [PATCH 08/17] dts: include documentation for the RISC-V interrupt controllers

On Thu, Jun 8, 2017 at 3:52 AM, Mark Rutland wrote: >> What flags? > > Edge vs level, active high vs active low. Typically some of these are > programmable, and are described as flags in the interrupt-specifier. > > See the examples in: > >

Re: [PATCH 08/17] dts: include documentation for the RISC-V interrupt controllers

On Thu, Jun 8, 2017 at 3:52 AM, Mark Rutland wrote: >> What flags? > > Edge vs level, active high vs active low. Typically some of these are > programmable, and are described as flags in the interrupt-specifier. > > See the examples in: > >

Re: [PATCH v8 14/34] ARM: dts: imx6-sabreauto: add the ADV7180 video decoder

On Thu 2017-06-08 13:36:12, Steve Longerbeam wrote: > > > On 06/08/2017 01:25 PM, Tim Harvey wrote: > > > > > >Steve, > > > >You need to remove the fim node now that you've moved this to V4L2 controls. > > > > Yep, I caught this just after sending the v8 patchset. I'll send > a v9 of this

Re: [PATCH v8 14/34] ARM: dts: imx6-sabreauto: add the ADV7180 video decoder

On Thu 2017-06-08 13:36:12, Steve Longerbeam wrote: > > > On 06/08/2017 01:25 PM, Tim Harvey wrote: > > > > > >Steve, > > > >You need to remove the fim node now that you've moved this to V4L2 controls. > > > > Yep, I caught this just after sending the v8 patchset. I'll send > a v9 of this

[git pull] first batch of ufs fixes

That's just the obvious backport fodder; I'm pretty sure that there will be more - definitely so wrt performance and quite possibly correctness as well. The following changes since commit a8c39544a6eb2093c04afd5005b6192bd0e880c6: osf_wait4(): fix infoleak (2017-05-21 13:10:07 -0400)

[git pull] first batch of ufs fixes

That's just the obvious backport fodder; I'm pretty sure that there will be more - definitely so wrt performance and quite possibly correctness as well. The following changes since commit a8c39544a6eb2093c04afd5005b6192bd0e880c6: osf_wait4(): fix infoleak (2017-05-21 13:10:07 -0400)

[PATCH] [media] davinci/dm644x: work around ccdc_update_raw_params trainwreck

Now that the davinci drivers can be enabled in compile tests on other architectures, I ran into this warning on a 64-bit build: drivers/media/platform/davinci/dm644x_ccdc.c: In function 'ccdc_update_raw_params': drivers/media/platform/davinci/dm644x_ccdc.c:279:7: error: cast to pointer from

[PATCH] [media] davinci/dm644x: work around ccdc_update_raw_params trainwreck

Now that the davinci drivers can be enabled in compile tests on other architectures, I ran into this warning on a 64-bit build: drivers/media/platform/davinci/dm644x_ccdc.c: In function 'ccdc_update_raw_params': drivers/media/platform/davinci/dm644x_ccdc.c:279:7: error: cast to pointer from

[PATCH] drm/core: Fail atomic IOCTL with no CRTC state but with signaling.

Problem: While running IGT kms_atomic_transition test suite i encountered a hang in drmHandleEvent immidietly follwoing an atomic_commit. After dumping the atomic state I relized that in this case there was not even one CRTC attached to the state and only disabled planes. This probably due to a

[PATCH] drm/core: Fail atomic IOCTL with no CRTC state but with signaling.

Problem: While running IGT kms_atomic_transition test suite i encountered a hang in drmHandleEvent immidietly follwoing an atomic_commit. After dumping the atomic state I relized that in this case there was not even one CRTC attached to the state and only disabled planes. This probably due to a

Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback

On Thu, Jun 8, 2017 at 6:33 PM, Luis R. Rodriguez wrote: > On Thu, Jun 8, 2017 at 6:14 PM, Andy Lutomirski wrote: >> That's what I meant, but I said it unclearly. I meant that, if we're >> going to start allowing interruption, we would need to audit all the

Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback

On Thu, Jun 8, 2017 at 6:33 PM, Luis R. Rodriguez wrote: > On Thu, Jun 8, 2017 at 6:14 PM, Andy Lutomirski wrote: >> That's what I meant, but I said it unclearly. I meant that, if we're >> going to start allowing interruption, we would need to audit all the >> callers. Ugh. > > There are

Re: [linux-sunxi] Re: [PATCH v2 01/11] dt-bindings: update the binding for Allwinner H3 TVE support

Hi! Dne petek, 09. junij 2017 ob 18:51:02 CEST je Icenowy Zheng napisal(a): > 于 2017年6月10日 GMT+08:00 上午12:49:15, Maxime Ripard 写到: > >On Wed, Jun 07, 2017 at 04:48:50PM +0800, Icenowy Zheng wrote: > >> >> @@ -189,6 +211,8 @@ supported. > >> >> > >> >>

Re: [linux-sunxi] Re: [PATCH v2 01/11] dt-bindings: update the binding for Allwinner H3 TVE support

Hi! Dne petek, 09. junij 2017 ob 18:51:02 CEST je Icenowy Zheng napisal(a): > 于 2017年6月10日 GMT+08:00 上午12:49:15, Maxime Ripard 写到: > >On Wed, Jun 07, 2017 at 04:48:50PM +0800, Icenowy Zheng wrote: > >> >> @@ -189,6 +211,8 @@ supported. > >> >> > >> >> Required properties: > >> >>-

Re: [PATCH 1/3] mm: add vm_insert_mixed_mkwrite()

On Wed, Jun 7, 2017 at 1:48 PM, Ross Zwisler wrote: > To be able to use the common 4k zero page in DAX we need to have our PTE > fault path look more like our PMD fault path where a PTE entry can be > marked as dirty and writeable as it is first inserted, rather than

Re: [PATCH 1/3] mm: add vm_insert_mixed_mkwrite()

On Wed, Jun 7, 2017 at 1:48 PM, Ross Zwisler wrote: > To be able to use the common 4k zero page in DAX we need to have our PTE > fault path look more like our PMD fault path where a PTE entry can be > marked as dirty and writeable as it is first inserted, rather than waiting > for a follow-up

Re: [PATCH v6 10/34] x86, x86/mm, x86/xen, olpc: Use __va() against just the physical address in cr3

On 6/9/2017 1:46 PM, Andy Lutomirski wrote: On Thu, Jun 8, 2017 at 3:38 PM, Tom Lendacky wrote: On 6/8/2017 1:05 AM, Andy Lutomirski wrote: On Wed, Jun 7, 2017 at 12:14 PM, Tom Lendacky wrote: The cr3 register entry can contain the SME

Re: [PATCH v6 10/34] x86, x86/mm, x86/xen, olpc: Use __va() against just the physical address in cr3

On 6/9/2017 1:46 PM, Andy Lutomirski wrote: On Thu, Jun 8, 2017 at 3:38 PM, Tom Lendacky wrote: On 6/8/2017 1:05 AM, Andy Lutomirski wrote: On Wed, Jun 7, 2017 at 12:14 PM, Tom Lendacky wrote: The cr3 register entry can contain the SME encryption bit that indicates the PGD is encrypted.

Re: [PATCH v2 0/6] Appended signatures support for IMA appraisal

Michael Ellerman writes: > Thiago Jung Bauermann writes: > >> On the OpenPOWER platform, secure boot and trusted boot are being >> implemented using IMA for taking measurements and verifying signatures. > > I still want you to implement

Re: [PATCH v2 0/6] Appended signatures support for IMA appraisal

Michael Ellerman writes: > Thiago Jung Bauermann writes: > >> On the OpenPOWER platform, secure boot and trusted boot are being >> implemented using IMA for taking measurements and verifying signatures. > > I still want you to implement arch_kexec_kernel_verify_sig() as well :) Yes, I will

[PATCH] hil_kbd: Use more common logging style

Remove use of #define PREFIX and use #define pr_fmt Miscellanea: o Convert printk(KERN_ to pr_ o Realign arguments o Remove duplicate "HIL" prefixes from a few messages Signed-off-by: Joe Perches --- drivers/input/keyboard/hil_kbd.c | 23 +-- 1 file

[PATCH] hil_kbd: Use more common logging style

Remove use of #define PREFIX and use #define pr_fmt Miscellanea: o Convert printk(KERN_ to pr_ o Realign arguments o Remove duplicate "HIL" prefixes from a few messages Signed-off-by: Joe Perches --- drivers/input/keyboard/hil_kbd.c | 23 +-- 1 file changed, 9

Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback

On Fri, Jun 09, 2017 at 09:40:47AM +0200, Martin Fuzzey wrote: > On 09/06/17 03:57, Luis R. Rodriguez wrote: > > On Thu, Jun 8, 2017 at 6:10 PM, Luis R. Rodriguez wrote: > > > > Android didn't send the signal, the kernel did (SIGCHLD). > > > > > > > > Like this: > > > > > > >

Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback

On Fri, Jun 09, 2017 at 09:40:47AM +0200, Martin Fuzzey wrote: > On 09/06/17 03:57, Luis R. Rodriguez wrote: > > On Thu, Jun 8, 2017 at 6:10 PM, Luis R. Rodriguez wrote: > > > > Android didn't send the signal, the kernel did (SIGCHLD). > > > > > > > > Like this: > > > > > > > > 1) Android init

[PATCH] Staging: vc04_services: bcm2835-audio: bcm2835-ctl.c: Fixed alignment to match open parenthesis.

Fixed alignment so that it matched open parenthesis. Signed-off-by: srishti sharma --- drivers/staging/vc04_services/bcm2835-audio/bcm2835-ctl.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/vc04_services/bcm2835-audio/bcm2835-ctl.c

[PATCH] Staging: vc04_services: bcm2835-audio: bcm2835-ctl.c: Fixed alignment to match open parenthesis.

Fixed alignment so that it matched open parenthesis. Signed-off-by: srishti sharma --- drivers/staging/vc04_services/bcm2835-audio/bcm2835-ctl.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/vc04_services/bcm2835-audio/bcm2835-ctl.c

Re: [PATCH 1/3] mtd: sharpsl: add sharpslpart MTD partition parser

Hi Boris, On Fri, Jun 09, 2017 at 09:16:43AM +0200, Boris Brezillon wrote: > On Thu, 8 Jun 2017 19:32:51 -0700 > Brian Norris wrote: > > On Tue, Apr 18, 2017 at 11:35:56AM +0200, Boris Brezillon wrote: > > > On Tue, 18 Apr 2017 10:58:02 +0200 > > > Andrea Adami

Re: [PATCH 1/3] mtd: sharpsl: add sharpslpart MTD partition parser

Hi Boris, On Fri, Jun 09, 2017 at 09:16:43AM +0200, Boris Brezillon wrote: > On Thu, 8 Jun 2017 19:32:51 -0700 > Brian Norris wrote: > > On Tue, Apr 18, 2017 at 11:35:56AM +0200, Boris Brezillon wrote: > > > On Tue, 18 Apr 2017 10:58:02 +0200 > > > Andrea Adami wrote: > > > > On Mon, Apr 17,

Re: [PATCH v2 1/2] dt-bindings: Add bindings for nvidia,tegra186-ccplex-cluster

On Thu, Jun 8, 2017 at 2:32 AM, Mikko Perttunen wrote: > On 08.06.2017 01:11, Rob Herring wrote: >> >> On Thu, Jun 01, 2017 at 11:04:04AM +0300, Mikko Perttunen wrote: >>> >>> The Tegra186 CCPLEX_CLUSTER area contains memory-mapped >>> registers that initiate CPU

Re: [PATCH v2 1/2] dt-bindings: Add bindings for nvidia,tegra186-ccplex-cluster

On Thu, Jun 8, 2017 at 2:32 AM, Mikko Perttunen wrote: > On 08.06.2017 01:11, Rob Herring wrote: >> >> On Thu, Jun 01, 2017 at 11:04:04AM +0300, Mikko Perttunen wrote: >>> >>> The Tegra186 CCPLEX_CLUSTER area contains memory-mapped >>> registers that initiate CPU frequency/voltage transitions. >>

[PATCH v12 04/14] sun4i-codec: Add Mic1 Boost Volume, Mic2 Boost Volume.

--- sound/soc/sunxi/sun4i-codec.c | 33 + 1 file changed, 33 insertions(+) diff --git a/sound/soc/sunxi/sun4i-codec.c b/sound/soc/sunxi/sun4i-codec.c index 42952af..c69b55c 100644 --- a/sound/soc/sunxi/sun4i-codec.c +++ b/sound/soc/sunxi/sun4i-codec.c @@ -95,6

[PATCH v12 05/14] sun4i-codec: Merge sun4i_codec_left_mixer_controls and sun4i_codec_right_mixer_controls into sun4i_codec_mixer_controls.

Since it's now possible to have a DAPM mixer control with multiple channels, use it to cut down the total number of controls. --- sound/soc/sunxi/sun4i-codec.c | 27 --- 1 file changed, 12 insertions(+), 15 deletions(-) diff --git a/sound/soc/sunxi/sun4i-codec.c

[PATCH v12 04/14] sun4i-codec: Add Mic1 Boost Volume, Mic2 Boost Volume.

--- sound/soc/sunxi/sun4i-codec.c | 33 + 1 file changed, 33 insertions(+) diff --git a/sound/soc/sunxi/sun4i-codec.c b/sound/soc/sunxi/sun4i-codec.c index 42952af..c69b55c 100644 --- a/sound/soc/sunxi/sun4i-codec.c +++ b/sound/soc/sunxi/sun4i-codec.c @@ -95,6

[PATCH v12 05/14] sun4i-codec: Merge sun4i_codec_left_mixer_controls and sun4i_codec_right_mixer_controls into sun4i_codec_mixer_controls.

Since it's now possible to have a DAPM mixer control with multiple channels, use it to cut down the total number of controls. --- sound/soc/sunxi/sun4i-codec.c | 27 --- 1 file changed, 12 insertions(+), 15 deletions(-) diff --git a/sound/soc/sunxi/sun4i-codec.c

[PATCH v12 03/14] sun4i-codec: Add support for extra controls to struct sun4i_codec_quirks and use them.

Some controls use different registers depending on which Allwinner chip it is. Provide a means of specifying and adding those controls. --- sound/soc/sunxi/sun4i-codec.c | 33 +++-- 1 file changed, 23 insertions(+), 10 deletions(-) diff --git

[PATCH v12 03/14] sun4i-codec: Add support for extra controls to struct sun4i_codec_quirks and use them.

Some controls use different registers depending on which Allwinner chip it is. Provide a means of specifying and adding those controls. --- sound/soc/sunxi/sun4i-codec.c | 33 +++-- 1 file changed, 23 insertions(+), 10 deletions(-) diff --git

[PATCH v12 09/14] sun4i-codec: Add Line Playback Volume.

--- sound/soc/sunxi/sun4i-codec.c | 8 1 file changed, 8 insertions(+) diff --git a/sound/soc/sunxi/sun4i-codec.c b/sound/soc/sunxi/sun4i-codec.c index 234ded2..c47ffd5 100644 --- a/sound/soc/sunxi/sun4i-codec.c +++ b/sound/soc/sunxi/sun4i-codec.c @@ -64,8 +64,11 @@ #define

[PATCH v12 09/14] sun4i-codec: Add Line Playback Volume.

--- sound/soc/sunxi/sun4i-codec.c | 8 1 file changed, 8 insertions(+) diff --git a/sound/soc/sunxi/sun4i-codec.c b/sound/soc/sunxi/sun4i-codec.c index 234ded2..c47ffd5 100644 --- a/sound/soc/sunxi/sun4i-codec.c +++ b/sound/soc/sunxi/sun4i-codec.c @@ -64,8 +64,11 @@ #define

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