Re: [PATCH v11 13/22] vfio: Introduce common function to add capabilities

On 11/8/2016 12:59 PM, Alexey Kardashevskiy wrote: > On 05/11/16 08:10, Kirti Wankhede wrote: >> Vendor driver using mediated device framework should use >> vfio_info_add_capability() to add capabilities. >> Introduced this function to reduce code duplication in vendor drivers. >> >>

Re: [PATCH v11 13/22] vfio: Introduce common function to add capabilities

On 11/8/2016 12:59 PM, Alexey Kardashevskiy wrote: > On 05/11/16 08:10, Kirti Wankhede wrote: >> Vendor driver using mediated device framework should use >> vfio_info_add_capability() to add capabilities. >> Introduced this function to reduce code duplication in vendor drivers. >> >>

Re: [PATCH v2 22/23] staging: iio: tsl2583: updated copyright and MODULE_AUTHOR

On 08/11/16 10:16, Brian Masney wrote: > Added Brian Masney's copyright to the header and to the MODULE_AUTHOR > for all of the staging cleanups that has been done to this driver. > > Signed-off-by: Brian Masney > --- > drivers/staging/iio/light/tsl2583.c | 3 ++- > 1

Re: [PATCH v2 22/23] staging: iio: tsl2583: updated copyright and MODULE_AUTHOR

On 08/11/16 10:16, Brian Masney wrote: > Added Brian Masney's copyright to the header and to the MODULE_AUTHOR > for all of the staging cleanups that has been done to this driver. > > Signed-off-by: Brian Masney > --- > drivers/staging/iio/light/tsl2583.c | 3 ++- > 1 file changed, 2

Re: [PATCH v11 17/22] vfio_platform: Updated to use vfio_set_irqs_validate_and_prepare()

On 11/8/2016 2:22 PM, Alexey Kardashevskiy wrote: > On 05/11/16 08:10, Kirti Wankhede wrote: >> Updated vfio_platform_common.c file to use >> vfio_set_irqs_validate_and_prepare() >> >> Signed-off-by: Kirti Wankhede >> Signed-off-by: Neo Jia >> Change-Id:

Re: [PATCH v11 17/22] vfio_platform: Updated to use vfio_set_irqs_validate_and_prepare()

On 11/8/2016 2:22 PM, Alexey Kardashevskiy wrote: > On 05/11/16 08:10, Kirti Wankhede wrote: >> Updated vfio_platform_common.c file to use >> vfio_set_irqs_validate_and_prepare() >> >> Signed-off-by: Kirti Wankhede >> Signed-off-by: Neo Jia >> Change-Id:

Re: Linux-4.X-rcY patches can't be applied with git?

Hi! > > But in that case, what if your patch generation script used a filter to > > exclude those binary files? No harm to that target audience, and it would > > actually make them behave better for distro builds. Though that might be > > counter to the goal of making them disappear entirely. :)

Re: Linux-4.X-rcY patches can't be applied with git?

Hi! > > But in that case, what if your patch generation script used a filter to > > exclude those binary files? No harm to that target audience, and it would > > actually make them behave better for distro builds. Though that might be > > counter to the goal of making them disappear entirely. :)

Re: [PATCH] nfsd: constify reply_cache_stats_operations structure

On Mon, Aug 29, 2016 at 06:57:47AM -0400, Jeff Layton wrote: > On Sun, 2016-08-28 at 22:36 +0200, Julia Lawall wrote: > > reply_cache_stats_operations, of type struct file_operations, is > > never > > modified, so declare it as const. > > > > Done with the help of Coccinelle. > > > >

Re: [PATCH] nfsd: constify reply_cache_stats_operations structure

On Mon, Aug 29, 2016 at 06:57:47AM -0400, Jeff Layton wrote: > On Sun, 2016-08-28 at 22:36 +0200, Julia Lawall wrote: > > reply_cache_stats_operations, of type struct file_operations, is > > never > > modified, so declare it as const. > > > > Done with the help of Coccinelle. > > > >

Re: [PATCH] x86/MCE: Remove MCP_TIMESTAMP

On Tue, 8 Nov 2016, Borislav Petkov wrote: > > Also, this fixes another bug where machine_check_poll() would clear > mce.tsc unconditionally even if we requested precise MCP_TIMESTAMP > logging. > @@ -713,7 +713,6 @@ bool machine_check_poll(enum mcp_flags flags, mce_banks_t > *b) >

Re: [PATCH] x86/MCE: Remove MCP_TIMESTAMP

On Tue, 8 Nov 2016, Borislav Petkov wrote: > > Also, this fixes another bug where machine_check_poll() would clear > mce.tsc unconditionally even if we requested precise MCP_TIMESTAMP > logging. > @@ -713,7 +713,6 @@ bool machine_check_poll(enum mcp_flags flags, mce_banks_t > *b) >

Re: [PATCH v2 2/2] scsi: ufs: Use the resource-managed function to add devfreq device

On 2016-11-08 01:16, Chanwoo Choi wrote: This patch uses the resource-managed to add the devfreq device. This function will make it easy to handle the devfreq device. - struct devfreq *devm_devfreq_add_device(struct device *dev, struct devfreq_dev_profile

Re: [PATCH v2 2/2] scsi: ufs: Use the resource-managed function to add devfreq device

On 2016-11-08 01:16, Chanwoo Choi wrote: This patch uses the resource-managed to add the devfreq device. This function will make it easy to handle the devfreq device. - struct devfreq *devm_devfreq_add_device(struct device *dev, struct devfreq_dev_profile

Re: [PATCH 3/3] ARM: gr8: evb: Add i2s codec

On Tue, Nov 08, 2016 at 03:57:48PM +0800, Chen-Yu Tsai wrote: > On Tue, Nov 8, 2016 at 3:44 PM, Maxime Ripard > wrote: > > On Mon, Nov 07, 2016 at 10:11:45PM +0800, Chen-Yu Tsai wrote: > >> On Mon, Nov 7, 2016 at 9:08 PM, Maxime Ripard > >>

Re: [PATCH v18 0/4] Introduce usb charger framework to deal with the usb gadget power negotation

On Tue, Nov 08 2016, Peter Chen wrote: > On Thu, Nov 03, 2016 at 12:25:42PM +1100, NeilBrown wrote: >> >> >> >> 2/ Change all usb phys to register an extcon and to send appropriate >>notifications. Many already do, but I don't think it is universal. >>It is probable that the extcon

Re: [PATCH] drm/sun4i: Fix error handling

Salut, On Sat, Nov 05, 2016 at 07:15:45AM +0100, Christophe JAILLET wrote: > Le 02/11/2016 à 19:14, Maxime Ripard a écrit : > > Hi, > > > > On Sun, Oct 30, 2016 at 12:53:02PM +0100, Christophe JAILLET wrote: > > > BTW, memory allocation in 'sun4i_layers_init()' looks spurious, especially > > >

Re: [PATCH 3/3] ARM: gr8: evb: Add i2s codec

On Tue, Nov 08, 2016 at 03:57:48PM +0800, Chen-Yu Tsai wrote: > On Tue, Nov 8, 2016 at 3:44 PM, Maxime Ripard > wrote: > > On Mon, Nov 07, 2016 at 10:11:45PM +0800, Chen-Yu Tsai wrote: > >> On Mon, Nov 7, 2016 at 9:08 PM, Maxime Ripard > >> wrote: > >> > The GR8-EVB comes with a wm8978 codec

Re: [PATCH v18 0/4] Introduce usb charger framework to deal with the usb gadget power negotation

On Tue, Nov 08 2016, Peter Chen wrote: > On Thu, Nov 03, 2016 at 12:25:42PM +1100, NeilBrown wrote: >> >> >> >> 2/ Change all usb phys to register an extcon and to send appropriate >>notifications. Many already do, but I don't think it is universal. >>It is probable that the extcon

Re: [PATCH] drm/sun4i: Fix error handling

Salut, On Sat, Nov 05, 2016 at 07:15:45AM +0100, Christophe JAILLET wrote: > Le 02/11/2016 à 19:14, Maxime Ripard a écrit : > > Hi, > > > > On Sun, Oct 30, 2016 at 12:53:02PM +0100, Christophe JAILLET wrote: > > > BTW, memory allocation in 'sun4i_layers_init()' looks spurious, especially > > >

linux-next: bad commit in the omap tree

Hi Tony, Commit 63fdf6527272 ("ARM: OMAP5: Add basic cpuidle MPU CSWR support") in the omap tree has no Signed-off-by from you as the committer. -- Cheers, Stephen Rothwell

Re: [RFC][PATCH] usb: dwc2: Make sure we disconnect the gadget state on reset

On Mon, Oct 31, 2016 at 4:18 AM, Felipe Balbi wrote: > John Stultz writes: >> I had seen some odd behavior with HiKey's usb-gadget interface >> that I finally seemed to have chased down. Basically every other >> time I pluged in the OTG port,

Re: BUG: 'list_empty(>free_vbufs)' is true!

On Mon, Nov 07, 2016 at 09:43:24AM +0100, Jiri Slaby wrote: > Hi, > > I can relatively easily reproduce this bug: > BUG: 'list_empty(>free_vbufs)' is true! > [ cut here ] > kernel BUG at /home/latest/linux/drivers/gpu/drm/virtio/virtgpu_vq.c:130! > invalid opcode:

linux-next: bad commit in the omap tree

Hi Tony, Commit 63fdf6527272 ("ARM: OMAP5: Add basic cpuidle MPU CSWR support") in the omap tree has no Signed-off-by from you as the committer. -- Cheers, Stephen Rothwell

Re: [RFC][PATCH] usb: dwc2: Make sure we disconnect the gadget state on reset

On Mon, Oct 31, 2016 at 4:18 AM, Felipe Balbi wrote: > John Stultz writes: >> I had seen some odd behavior with HiKey's usb-gadget interface >> that I finally seemed to have chased down. Basically every other >> time I pluged in the OTG port, the gadget interface would >> properly initialize.

Re: BUG: 'list_empty(>free_vbufs)' is true!

On Mon, Nov 07, 2016 at 09:43:24AM +0100, Jiri Slaby wrote: > Hi, > > I can relatively easily reproduce this bug: > BUG: 'list_empty(>free_vbufs)' is true! > [ cut here ] > kernel BUG at /home/latest/linux/drivers/gpu/drm/virtio/virtgpu_vq.c:130! > invalid opcode:

[PATCH v4 2/8] iio: inkern: add helpers to query available values from channels

Specifically a helper for reading the available maximum raw value of a channel and a helper for forwarding read_avail requests for raw values from one iio driver to an iio channel that is consumed. These rather specific helpers are in turn built with generic helpers making it easy to build more

[PATCH v4 2/8] iio: inkern: add helpers to query available values from channels

Specifically a helper for reading the available maximum raw value of a channel and a helper for forwarding read_avail requests for raw values from one iio driver to an iio channel that is consumed. These rather specific helpers are in turn built with generic helpers making it easy to build more

[PATCH v4 7/8] dt-bindings: iio: document envelope-detector bindings

Acked-by: Rob Herring Signed-off-by: Peter Rosin --- .../bindings/iio/adc/envelope-detector.txt | 54 ++ MAINTAINERS| 6 +++ 2 files changed, 60 insertions(+) create mode 100644

[PATCH v4 7/8] dt-bindings: iio: document envelope-detector bindings

Acked-by: Rob Herring Signed-off-by: Peter Rosin --- .../bindings/iio/adc/envelope-detector.txt | 54 ++ MAINTAINERS| 6 +++ 2 files changed, 60 insertions(+) create mode 100644

Re: [PATCH 3/3] ARM: dts: da850: add usb device node

Hi Axel, [auto build test ERROR on usb/usb-testing] [also build test ERROR on next-20161108] [cannot apply to robh/for-next v4.9-rc4] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Axel-Haslam

Re: [PATCH 3/3] ARM: dts: da850: add usb device node

Hi Axel, [auto build test ERROR on usb/usb-testing] [also build test ERROR on next-20161108] [cannot apply to robh/for-next v4.9-rc4] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Axel-Haslam

Re: [PATCH 2/2] iio: gyro: mpu3050: add I2C dependency

On 08/11/16 15:40, Linus Walleij wrote: > On Tue, Nov 8, 2016 at 2:59 PM, Arnd Bergmann wrote: > >> The new mpu3050 driver fails to build if I2C is disabled: >> >> drivers/iio/built-in.o: In function `mpu3050_i2c_driver_exit': >> mpu3050-i2c.c:(.exit.text+0x17f): undefined

Re: [PATCH v4 1/3] leds: Introduce userspace leds driver

On 11/08/2016 08:08 PM, David Lechner wrote: On 11/8/16 5:26 AM, Jacek Anaszewski wrote: Hi David, +struct uleds_device { +struct uleds_user_devuser_dev; +struct led_classdevled_cdev; +struct mutexmutex; +enum uleds_statestate; +wait_queue_head_t

[PATCH v2] ARC: [plat-eznps] remove IPI clear from SMP operations

From: Noam Camus Today we register to plat_smp_ops.clear() method which actually is acking the IPI. However this is already taking care by our irqchip driver specifically by the irq_chip.irq_eoi() method. This is perfect timing where it should be done and no special handling

Re: [PATCH 2/2] iio: gyro: mpu3050: add I2C dependency

On 08/11/16 15:40, Linus Walleij wrote: > On Tue, Nov 8, 2016 at 2:59 PM, Arnd Bergmann wrote: > >> The new mpu3050 driver fails to build if I2C is disabled: >> >> drivers/iio/built-in.o: In function `mpu3050_i2c_driver_exit': >> mpu3050-i2c.c:(.exit.text+0x17f): undefined reference to

Re: [PATCH v4 1/3] leds: Introduce userspace leds driver

On 11/08/2016 08:08 PM, David Lechner wrote: On 11/8/16 5:26 AM, Jacek Anaszewski wrote: Hi David, +struct uleds_device { +struct uleds_user_devuser_dev; +struct led_classdevled_cdev; +struct mutexmutex; +enum uleds_statestate; +wait_queue_head_t

[PATCH v2] ARC: [plat-eznps] remove IPI clear from SMP operations

From: Noam Camus Today we register to plat_smp_ops.clear() method which actually is acking the IPI. However this is already taking care by our irqchip driver specifically by the irq_chip.irq_eoi() method. This is perfect timing where it should be done and no special handling is needed at

Re: Summary of LPC guest MSI discussion in Santa Fe (was: Re: [RFC 0/8] KVM PCIe/MSI passthrough on ARM/ARM64 (Alt II))

Hi Will, On Tue, Nov 08, 2016 at 02:45:59AM +, Will Deacon wrote: > Hi all, > > I figured this was a reasonable post to piggy-back on for the LPC minutes > relating to guest MSIs on arm64. > > On Thu, Nov 03, 2016 at 10:02:05PM -0600, Alex Williamson wrote: > > We can always have QEMU

Re: [PATCH 1/2] iio: gyro: mpu3050: remove duplicate initializer

On 08/11/16 15:39, Linus Walleij wrote: > On Tue, Nov 8, 2016 at 2:59 PM, Arnd Bergmann wrote: > >> The newly added mpu3050 driver has two initializations for the >> module owner, which causes a warning for 'make W=1': >> >> include/linux/export.h:37:21: error: initialized field

Re: [PATCH 1/2] iio: gyro: mpu3050: remove duplicate initializer

On 08/11/16 15:39, Linus Walleij wrote: > On Tue, Nov 8, 2016 at 2:59 PM, Arnd Bergmann wrote: > >> The newly added mpu3050 driver has two initializations for the >> module owner, which causes a warning for 'make W=1': >> >> include/linux/export.h:37:21: error: initialized field overwritten >>

Re: Summary of LPC guest MSI discussion in Santa Fe (was: Re: [RFC 0/8] KVM PCIe/MSI passthrough on ARM/ARM64 (Alt II))

Hi Will, On Tue, Nov 08, 2016 at 02:45:59AM +, Will Deacon wrote: > Hi all, > > I figured this was a reasonable post to piggy-back on for the LPC minutes > relating to guest MSIs on arm64. > > On Thu, Nov 03, 2016 at 10:02:05PM -0600, Alex Williamson wrote: > > We can always have QEMU

Re: [PATCH] staging: iio: tsl2583: fix unused function warning

On 08/11/16 14:01, Arnd Bergmann wrote: > Removing a call to the taos_chip_off() makes it unused when CONFIG_PM > is disabled: > > drivers/staging/iio/light/tsl2583.c:438:12: error: ‘taos_chip_off’ defined > but not used [-Werror=unused-function] > > This removes all the #ifdef in this file,

Re: [PATCH] staging: iio: tsl2583: fix unused function warning

On 08/11/16 14:01, Arnd Bergmann wrote: > Removing a call to the taos_chip_off() makes it unused when CONFIG_PM > is disabled: > > drivers/staging/iio/light/tsl2583.c:438:12: error: ‘taos_chip_off’ defined > but not used [-Werror=unused-function] > > This removes all the #ifdef in this file,

Re: [PATCH v11 15/22] vfio: Introduce vfio_set_irqs_validate_and_prepare()

On 11/8/2016 2:16 PM, Alexey Kardashevskiy wrote: > On 05/11/16 08:10, Kirti Wankhede wrote: >> Vendor driver using mediated device framework would use same mechnism to >> validate and prepare IRQs. Introducing this function to reduce code >> replication in multiple drivers. >> >> Signed-off-by:

Re: [PATCH v11 15/22] vfio: Introduce vfio_set_irqs_validate_and_prepare()

On 11/8/2016 2:16 PM, Alexey Kardashevskiy wrote: > On 05/11/16 08:10, Kirti Wankhede wrote: >> Vendor driver using mediated device framework would use same mechnism to >> validate and prepare IRQs. Introducing this function to reduce code >> replication in multiple drivers. >> >> Signed-off-by:

Re: [PATCH v4 0/2] ARC: Set of patches for IRQ subsystem

On 11/07/2016 11:08 PM, Yuriy Kolerov wrote: > The first patch fixes misuse of IRQ numbers. In some places of the > Linux kernel for ARC hardware IRQ numbers are used as virtual IRQ > numbers and obviously it is wrong. > > The second patch forces the kernel to set a simple distribution mode > for

Re: [PATCH v4 0/2] ARC: Set of patches for IRQ subsystem

On 11/07/2016 11:08 PM, Yuriy Kolerov wrote: > The first patch fixes misuse of IRQ numbers. In some places of the > Linux kernel for ARC hardware IRQ numbers are used as virtual IRQ > numbers and obviously it is wrong. > > The second patch forces the kernel to set a simple distribution mode > for

Re: [PATCH] staging: iio: ad9832: allocate data before using

On 08/11/16 14:00, Arnd Bergmann wrote: > The regulator changes assigned data to an uninitialized pointer: > > drivers/staging/iio/frequency/ad9832.c: In function 'ad9832_probe': > drivers/staging/iio/frequency/ad9832.c:214:11: error: 'st' may be used > uninitialized in this function

Re: [PATCH] staging: iio: ad9832: allocate data before using

On 08/11/16 14:00, Arnd Bergmann wrote: > The regulator changes assigned data to an uninitialized pointer: > > drivers/staging/iio/frequency/ad9832.c: In function 'ad9832_probe': > drivers/staging/iio/frequency/ad9832.c:214:11: error: 'st' may be used > uninitialized in this function

Re: [PATCH v4 1/2] ARC: IRQ: Do not use hwirq as virq and vice versa

On 11/07/2016 11:08 PM, Yuriy Kolerov wrote: > At first smp_ipi_irq_setup() takes a cpu number and a hwirq number for > the per core local interrupt line in the root interrupt controller and > registers an appropriate IPI handler per cpu. However this function tries > to bind a handler to the

Re: [PATCH v4 1/2] ARC: IRQ: Do not use hwirq as virq and vice versa

On 11/07/2016 11:08 PM, Yuriy Kolerov wrote: > At first smp_ipi_irq_setup() takes a cpu number and a hwirq number for > the per core local interrupt line in the root interrupt controller and > registers an appropriate IPI handler per cpu. However this function tries > to bind a handler to the

Re: [v4.9-rc4] dvb-usb/cinergyT2 NULL pointer dereference

Em Tue, 8 Nov 2016 10:42:03 -0800 Linus Torvalds escreveu: > On Sun, Nov 6, 2016 at 7:40 AM, Jörg Otte wrote: > > Since v4.9-rc4 I get following crash in dvb-usb-cinergyT2 module. > > Looks like it's commit 5ef8ed0e5608f ("[media]

Re: [v4.9-rc4] dvb-usb/cinergyT2 NULL pointer dereference

Em Tue, 8 Nov 2016 10:42:03 -0800 Linus Torvalds escreveu: > On Sun, Nov 6, 2016 at 7:40 AM, Jörg Otte wrote: > > Since v4.9-rc4 I get following crash in dvb-usb-cinergyT2 module. > > Looks like it's commit 5ef8ed0e5608f ("[media] cinergyT2-core: don't > do DMA on stack"), which movced the

Re: [PATCH 0/2] qla2xxx: fix errors in PCI device remove with ongoing I/O

On 11/7/16, 11:53 AM, "Mauricio Faria de Oliveira" wrote: >This patchset addresses a couple of errors that might happen during >PCI device remove (e.g., PCI hotplug, PowerVM DLPAR), which prevent >the successful removal and re-addition of the adapter to the

Re: [PATCH 0/2] qla2xxx: fix errors in PCI device remove with ongoing I/O

On 11/7/16, 11:53 AM, "Mauricio Faria de Oliveira" wrote: >This patchset addresses a couple of errors that might happen during >PCI device remove (e.g., PCI hotplug, PowerVM DLPAR), which prevent >the successful removal and re-addition of the adapter to the system, >and cause an oops and/or

Re: [PATCH 1/1 v7] ARM: imx: Added perf functionality to mmdc driver

On Tue, Nov 8, 2016 at 2:11 PM, Peter Zijlstra wrote: > On Tue, Nov 08, 2016 at 01:21:47PM -0600, Zhi Li wrote: >> On Tue, Nov 8, 2016 at 1:00 PM, Paul Gortmaker >> > I just noticed this commit now that linux-next is back after the week off. >> > >> > This should probably

Re: [PATCH 1/1 v7] ARM: imx: Added perf functionality to mmdc driver

On Tue, Nov 8, 2016 at 2:11 PM, Peter Zijlstra wrote: > On Tue, Nov 08, 2016 at 01:21:47PM -0600, Zhi Li wrote: >> On Tue, Nov 8, 2016 at 1:00 PM, Paul Gortmaker >> > I just noticed this commit now that linux-next is back after the week off. >> > >> > This should probably use core_param or

Re: [PATCH v6 0/5] Functional dependencies between devices

On Tue, Nov 08, 2016 at 07:36:45AM +0100, Marek Szyprowski wrote: > Hi Luis, > > > On 2016-11-07 22:15, Luis R. Rodriguez wrote: > > On Wed, Nov 02, 2016 at 08:58:38AM +0100, Marek Szyprowski wrote: > > > On 2016-10-31 18:47, Greg Kroah-Hartman wrote: > > > > On Sun, Oct 30, 2016 at 05:22:13PM

Re: [PATCH v6 0/5] Functional dependencies between devices

On Tue, Nov 08, 2016 at 07:36:45AM +0100, Marek Szyprowski wrote: > Hi Luis, > > > On 2016-11-07 22:15, Luis R. Rodriguez wrote: > > On Wed, Nov 02, 2016 at 08:58:38AM +0100, Marek Szyprowski wrote: > > > On 2016-10-31 18:47, Greg Kroah-Hartman wrote: > > > > On Sun, Oct 30, 2016 at 05:22:13PM

[PATCH] pci-hyperv: use kmalloc to allocate hypercall params buffer

From: Long Li hv_do_hypercall assumes that we pass a segment from a physically continuous buffer. Buffer allocated on the stack may not work if CONFIG_VMAP_STACK=y is set. Change to use kmalloc to allocate this buffer. The v2 patch adds locking to access the pre-allocated

[PATCH] pci-hyperv: use kmalloc to allocate hypercall params buffer

From: Long Li hv_do_hypercall assumes that we pass a segment from a physically continuous buffer. Buffer allocated on the stack may not work if CONFIG_VMAP_STACK=y is set. Change to use kmalloc to allocate this buffer. The v2 patch adds locking to access the pre-allocated buffer.

Re: [PATCH 1/1 v7] ARM: imx: Added perf functionality to mmdc driver

On Tue, Nov 08, 2016 at 01:21:47PM -0600, Zhi Li wrote: > On Tue, Nov 8, 2016 at 1:00 PM, Paul Gortmaker > > I just noticed this commit now that linux-next is back after the week off. > > > > This should probably use core_param or setup_param since the Kconfig > > for this is bool and not

Re: [PATCH 1/1 v7] ARM: imx: Added perf functionality to mmdc driver

On Tue, Nov 08, 2016 at 01:21:47PM -0600, Zhi Li wrote: > On Tue, Nov 8, 2016 at 1:00 PM, Paul Gortmaker > > I just noticed this commit now that linux-next is back after the week off. > > > > This should probably use core_param or setup_param since the Kconfig > > for this is bool and not

Re: [PATCH v10 6/7] x86/arch_prctl: Add ARCH_[GET|SET]_CPUID

On Tue, 8 Nov 2016, Kyle Huey wrote: > Intel supports faulting on the CPUID instruction beginning with Ivy Bridge. > When enabled, the processor will fault on attempts to execute the CPUID > instruction with CPL>0. Exposing this feature to userspace will allow a > ptracer to trap and emulate the

Re: [PATCH v10 6/7] x86/arch_prctl: Add ARCH_[GET|SET]_CPUID

On Tue, 8 Nov 2016, Kyle Huey wrote: > Intel supports faulting on the CPUID instruction beginning with Ivy Bridge. > When enabled, the processor will fault on attempts to execute the CPUID > instruction with CPL>0. Exposing this feature to userspace will allow a > ptracer to trap and emulate the

Re: [PATCH] m32r: add simple dma

On Thursday 03 November 2016 07:13 PM, Andrew Morton wrote: On Sun, 30 Oct 2016 23:47:29 +0530 Sudip Mukherjee wrote: On Friday 21 October 2016 08:59 AM, Andrew Morton wrote: On Sat, 8 Oct 2016 23:23:18 +0530 Sudip Mukherjee wrote:

Re: [PATCH] m32r: add simple dma

On Thursday 03 November 2016 07:13 PM, Andrew Morton wrote: On Sun, 30 Oct 2016 23:47:29 +0530 Sudip Mukherjee wrote: On Friday 21 October 2016 08:59 AM, Andrew Morton wrote: On Sat, 8 Oct 2016 23:23:18 +0530 Sudip Mukherjee wrote: Some builds of m32r were failing as it tried to build

[RFC 1/2] mmc: sdhci-pci: Add PCI ID for Intel byt sdio host controller sub-vended by NI

Add PCI ID for Intel byt sdio host controller sub-vended by NI. The controller has different behavior because of the board layout NI puts it on. Signed-off-by: Zach Brown --- drivers/mmc/host/sdhci-pci-core.c | 20 1 file changed, 20 insertions(+) diff

[RFC 1/2] mmc: sdhci-pci: Add PCI ID for Intel byt sdio host controller sub-vended by NI

Add PCI ID for Intel byt sdio host controller sub-vended by NI. The controller has different behavior because of the board layout NI puts it on. Signed-off-by: Zach Brown --- drivers/mmc/host/sdhci-pci-core.c | 20 1 file changed, 20 insertions(+) diff --git

[RFC 0/2] mmc: sdhci-pci: Use ACPI to set max frequency of sdio host

On some boards, max SDIO frequency is limited by trace lengths and other layout choices. We would like a way to specify this limitation so the driver can behave accordingly. This patch set assumes that the limitation has been reported in an ACPI table which the driver can check to get the max

[RFC 0/2] mmc: sdhci-pci: Use ACPI to set max frequency of sdio host

On some boards, max SDIO frequency is limited by trace lengths and other layout choices. We would like a way to specify this limitation so the driver can behave accordingly. This patch set assumes that the limitation has been reported in an ACPI table which the driver can check to get the max

[RFC 2/2] mmc: sdhci-pci: Use ACPI to get max frequency for Intel byt sdio host controller sub-vended by NI

On NI 9037 boards the max SDIO frequency is limited by trace lengths and other layout choices. The max SDIO frequency is stored in an ACPI table, as MXFQ. The driver reads the ACPI entry MXFQ during sdio_probe_slot and sets the f_max field of the host with it. Signed-off-by: Nathan Sullivan

[RFC 2/2] mmc: sdhci-pci: Use ACPI to get max frequency for Intel byt sdio host controller sub-vended by NI

On NI 9037 boards the max SDIO frequency is limited by trace lengths and other layout choices. The max SDIO frequency is stored in an ACPI table, as MXFQ. The driver reads the ACPI entry MXFQ during sdio_probe_slot and sets the f_max field of the host with it. Signed-off-by: Nathan Sullivan

Re: [Linux-ima-devel] [PATCH v6 04/10] ima: maintain memory size needed for serializing the measurement list

On Fri, Oct 21, 2016 at 5:44 AM, Thiago Jung Bauermann wrote: > From: Mimi Zohar > > In preparation for serializing the binary_runtime_measurements, this patch > maintains the amount of memory required. > > Changelog v5: > - replace

Re: [Linux-ima-devel] [PATCH v6 04/10] ima: maintain memory size needed for serializing the measurement list

On Fri, Oct 21, 2016 at 5:44 AM, Thiago Jung Bauermann wrote: > From: Mimi Zohar > > In preparation for serializing the binary_runtime_measurements, this patch > maintains the amount of memory required. > > Changelog v5: > - replace CONFIG_KEXEC_FILE with architecture CONFIG_HAVE_IMA_KEXEC

RE: [PATCH V3 07/14] Drivers: hv: vss: Operation timeouts should match host expectation

This looks messy, weird line wrap?? +/* + * Timeout values are based on expecations from host */ #define +VSS_FREEZE_TIMEOUT (15 * 60)

RE: [PATCH V3 07/14] Drivers: hv: vss: Operation timeouts should match host expectation

This looks messy, weird line wrap?? +/* + * Timeout values are based on expecations from host */ #define +VSS_FREEZE_TIMEOUT (15 * 60)

Re: [RFC v3 1/6] Track the active utilisation

On 08/11/16 20:09, Luca Abeni wrote: > Hi again, > > On Tue, 8 Nov 2016 18:53:09 + > Juri Lelli wrote: > [...] > > > > Also, AFAIU, do_exit() works on current and the TASK_DEAD case is > > > > handled in finish_task_switch(), so I don't think we are taking > > > > care of

Re: [RFC v3 1/6] Track the active utilisation

On 08/11/16 20:09, Luca Abeni wrote: > Hi again, > > On Tue, 8 Nov 2016 18:53:09 + > Juri Lelli wrote: > [...] > > > > Also, AFAIU, do_exit() works on current and the TASK_DEAD case is > > > > handled in finish_task_switch(), so I don't think we are taking > > > > care of the "task is dying"

Re: [PATCH v11 11/22] vfio iommu: Add blocking notifier to notify DMA_UNMAP

On 11/8/2016 11:16 PM, Alex Williamson wrote: > On Tue, 8 Nov 2016 21:56:29 +0530 > Kirti Wankhede wrote: > >> On 11/8/2016 5:15 AM, Alex Williamson wrote: >>> On Sat, 5 Nov 2016 02:40:45 +0530 >>> Kirti Wankhede wrote: >>> >> ...

Re: [PATCH v11 11/22] vfio iommu: Add blocking notifier to notify DMA_UNMAP

On 11/8/2016 11:16 PM, Alex Williamson wrote: > On Tue, 8 Nov 2016 21:56:29 +0530 > Kirti Wankhede wrote: > >> On 11/8/2016 5:15 AM, Alex Williamson wrote: >>> On Sat, 5 Nov 2016 02:40:45 +0530 >>> Kirti Wankhede wrote: >>> >> ... +int vfio_register_notifier(struct device *dev,

Re: [PATCH v6 4/4] of/fdt: mark hotpluggable memory

On Tue, Nov 08, 2016 at 09:59:26AM +0800, kbuild test robot wrote: All errors (new ones prefixed by >>): drivers/of/fdt.c: In function 'early_init_dt_scan_memory': drivers/of/fdt.c:1064:3: error: implicit declaration of function 'memblock_mark_hotplug' cc1: some warnings being treated as

Re: [PATCH v6 4/4] of/fdt: mark hotpluggable memory

On Tue, Nov 08, 2016 at 09:59:26AM +0800, kbuild test robot wrote: All errors (new ones prefixed by >>): drivers/of/fdt.c: In function 'early_init_dt_scan_memory': drivers/of/fdt.c:1064:3: error: implicit declaration of function 'memblock_mark_hotplug' cc1: some warnings being treated as

Re: [PATCH] sched/rt: RT_RUNTIME_GREED sched feature

On Tue, Nov 08, 2016 at 08:29:49PM +0100, Daniel Bristot de Oliveira wrote: > > > On 11/08/2016 07:05 PM, Peter Zijlstra wrote: > >> > > >> > I know what we want to do, but there's some momentous problems that > >> > need to be solved first. > > Like what? > > The problem is that using

Re: [PATCH] sched/rt: RT_RUNTIME_GREED sched feature

On Tue, Nov 08, 2016 at 08:29:49PM +0100, Daniel Bristot de Oliveira wrote: > > > On 11/08/2016 07:05 PM, Peter Zijlstra wrote: > >> > > >> > I know what we want to do, but there's some momentous problems that > >> > need to be solved first. > > Like what? > > The problem is that using

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

On Tue, Nov 08, 2016 at 07:40:53PM +0100, Jiri Slaby wrote: > On 11/08/2016, 11:15 AM, Greg KH wrote: > > On Tue, Nov 08, 2016 at 04:30:13PM +1100, Stephen Rothwell wrote: > >> Hi Greg, > >> > >> Today's linux-next merge of the tty tree got a conflict in: > >> > >>

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

On Tue, Nov 08, 2016 at 07:40:53PM +0100, Jiri Slaby wrote: > On 11/08/2016, 11:15 AM, Greg KH wrote: > > On Tue, Nov 08, 2016 at 04:30:13PM +1100, Stephen Rothwell wrote: > >> Hi Greg, > >> > >> Today's linux-next merge of the tty tree got a conflict in: > >> > >>

[PATCH v3 2/4] KVM: x86: save one bit in ctxt->d

Alignments are exclusive, so 5 modes can be expressed in 3 bits. Signed-off-by: Radim Krčmář --- arch/x86/kvm/emulate.c | 23 +-- 1 file changed, 13 insertions(+), 10 deletions(-) diff --git a/arch/x86/kvm/emulate.c b/arch/x86/kvm/emulate.c index

[PATCH v3 2/4] KVM: x86: save one bit in ctxt->d

Alignments are exclusive, so 5 modes can be expressed in 3 bits. Signed-off-by: Radim Krčmář --- arch/x86/kvm/emulate.c | 23 +-- 1 file changed, 13 insertions(+), 10 deletions(-) diff --git a/arch/x86/kvm/emulate.c b/arch/x86/kvm/emulate.c index eb74d3b56e1c..14624d6bf112

[PATCH v3 4/4] KVM: x86: emulate FXSAVE and FXRSTOR

Internal errors were reported on 16 bit fxsave and fxrstor with ipxe. Old Intels don't have unrestricted_guest, so we have to emulate them. The patch takes advantage of the hardware implementation. Signed-off-by: Radim Krčmář --- v3: - remove fxsave64 and extra colons at

[PATCH v3 4/4] KVM: x86: emulate FXSAVE and FXRSTOR

Internal errors were reported on 16 bit fxsave and fxrstor with ipxe. Old Intels don't have unrestricted_guest, so we have to emulate them. The patch takes advantage of the hardware implementation. Signed-off-by: Radim Krčmář --- v3: - remove fxsave64 and extra colons at the end of asm to

[PATCH v3 3/4] KVM: x86: add asm_safe wrapper

Move the existing exception handling for inline assembly into a macro and switch its return values to X86EMUL type. Signed-off-by: Radim Krčmář --- v2: new --- arch/x86/kvm/emulate.c | 34 +++--- 1 file changed, 23 insertions(+), 11 deletions(-)

[PATCH v3 0/4] KVM: x86: emulate FXSAVE and FXRSTOR

v2: http://www.spinics.net/lists/kvm/msg139681.html v3 brings compatibility with old compilers and has been compile-tested with GCC-4.4 on Debian Wheezy, GCC-4.4 on RHEL 6, and GCC-4.1 on RHEL 5. [4/4] still has the hidden assumption that guest and host CPUID match. Emulating a guest that does

[PATCH v3 1/4] KVM: x86: add Align16 instruction flag

Needed for FXSAVE and FXRSTOR. Signed-off-by: Radim Krčmář --- v2: split into a separate patch --- arch/x86/kvm/emulate.c | 20 1 file changed, 12 insertions(+), 8 deletions(-) diff --git a/arch/x86/kvm/emulate.c b/arch/x86/kvm/emulate.c index

[PATCH v3 3/4] KVM: x86: add asm_safe wrapper

Move the existing exception handling for inline assembly into a macro and switch its return values to X86EMUL type. Signed-off-by: Radim Krčmář --- v2: new --- arch/x86/kvm/emulate.c | 34 +++--- 1 file changed, 23 insertions(+), 11 deletions(-) diff --git

[PATCH v3 0/4] KVM: x86: emulate FXSAVE and FXRSTOR

v2: http://www.spinics.net/lists/kvm/msg139681.html v3 brings compatibility with old compilers and has been compile-tested with GCC-4.4 on Debian Wheezy, GCC-4.4 on RHEL 6, and GCC-4.1 on RHEL 5. [4/4] still has the hidden assumption that guest and host CPUID match. Emulating a guest that does

[PATCH v3 1/4] KVM: x86: add Align16 instruction flag

Needed for FXSAVE and FXRSTOR. Signed-off-by: Radim Krčmář --- v2: split into a separate patch --- arch/x86/kvm/emulate.c | 20 1 file changed, 12 insertions(+), 8 deletions(-) diff --git a/arch/x86/kvm/emulate.c b/arch/x86/kvm/emulate.c index cbd7b92585bb..eb74d3b56e1c

Re: [PATCH v2] irqchip/renesas-irqc: Postpone driver initialization

Hi Florian, On Tue, Nov 8, 2016 at 8:42 PM, Florian Fainelli wrote: > On 11/08/2016 11:35 AM, Geert Uytterhoeven wrote: >> Currently the renesas-irqc driver uses postcore_initcall(). >> >> However, the new CPG/MSSR driver uses subsys_initcall(). Hence the >> IRQC's probe

Re: [PATCH v2] irqchip/renesas-irqc: Postpone driver initialization

Hi Florian, On Tue, Nov 8, 2016 at 8:42 PM, Florian Fainelli wrote: > On 11/08/2016 11:35 AM, Geert Uytterhoeven wrote: >> Currently the renesas-irqc driver uses postcore_initcall(). >> >> However, the new CPG/MSSR driver uses subsys_initcall(). Hence the >> IRQC's probe will be deferred, which

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