Re: [PATCH 1/2] x86/arch_prctl: add ARCH_SET_{COMPAT,NATIVE} to change compatible mode

[cc Dave Hansen for MPX] On Apr 6, 2016 9:30 AM, "Dmitry Safonov" wrote: > > Now each process that runs natively on x86_64 may execute 32-bit code > by proper setting it's CS selector: either from LDT or reuse Linux's > USER32_CS. The vice-versa is also valid: running

Re: [PATCH 1/2] x86/arch_prctl: add ARCH_SET_{COMPAT,NATIVE} to change compatible mode

[cc Dave Hansen for MPX] On Apr 6, 2016 9:30 AM, "Dmitry Safonov" wrote: > > Now each process that runs natively on x86_64 may execute 32-bit code > by proper setting it's CS selector: either from LDT or reuse Linux's > USER32_CS. The vice-versa is also valid: running 64-bit code in > compatible

Re: [PATCH v5 3/6] smp: add function to execute a function synchronously on a cpu

On Wed, Apr 06, 2016 at 04:17:43PM +0200, Juergen Gross wrote: > On some hardware models (e.g. Dell Studio 1555 laptop) some hardware > related functions (e.g. SMIs) are to be executed on physical cpu 0 > only. Instead of open coding such a functionality multiple times in > the kernel add a

Re: [PATCH v5 3/6] smp: add function to execute a function synchronously on a cpu

On Wed, Apr 06, 2016 at 04:17:43PM +0200, Juergen Gross wrote: > On some hardware models (e.g. Dell Studio 1555 laptop) some hardware > related functions (e.g. SMIs) are to be executed on physical cpu 0 > only. Instead of open coding such a functionality multiple times in > the kernel add a

Re: [PATCH v2 14/14] USB: ch341: implement tx_empty callback

On 04/03/2016 06:03 PM, Karl Palsson wrote: > > Grigori Goronzy wrote: >> The status bit was found with USB captures of the Windows >> driver and some luck. Tested on CH340G and CH341A. > > By my reversing, bit 0x4, is "multiple status changes since last > interrupt" >

Re: [PATCH v2 14/14] USB: ch341: implement tx_empty callback

On 04/03/2016 06:03 PM, Karl Palsson wrote: > > Grigori Goronzy wrote: >> The status bit was found with USB captures of the Windows >> driver and some luck. Tested on CH340G and CH341A. > > By my reversing, bit 0x4, is "multiple status changes since last > interrupt" > Thanks, I can add the

Re: [PATCH] KERNEL: resource: Fix bug on leakage in /proc/iomem file

On Wed, Apr 6, 2016 at 6:03 AM, Emrah Demir wrote: > From: Emrah Demir Hi! Thanks for sending this patch; I'm always glad to see new faces helping. :) I have a few comments inline and a larger suggestion at the end. > Even though KASLR is aiming to mitigate

Re: [PATCH] KERNEL: resource: Fix bug on leakage in /proc/iomem file

On Wed, Apr 6, 2016 at 6:03 AM, Emrah Demir wrote: > From: Emrah Demir Hi! Thanks for sending this patch; I'm always glad to see new faces helping. :) I have a few comments inline and a larger suggestion at the end. > Even though KASLR is aiming to mitigate remote attacks, with a simple LFI

Re: [PATCH 0/3] crypto: af_alg - add TLS type encryption

Hi Herbert, On 04/05/2016 04:29 AM, Herbert Xu wrote: > On Sat, Mar 05, 2016 at 05:20:44PM -0800, Tadeusz Struk wrote: >> > Hi, >> > The following series adds TLS type authentication. To do this a new >> > template, encauth, is introduced. It is derived from the existing authenc >> > template and

Re: [PATCH 0/3] crypto: af_alg - add TLS type encryption

Hi Herbert, On 04/05/2016 04:29 AM, Herbert Xu wrote: > On Sat, Mar 05, 2016 at 05:20:44PM -0800, Tadeusz Struk wrote: >> > Hi, >> > The following series adds TLS type authentication. To do this a new >> > template, encauth, is introduced. It is derived from the existing authenc >> > template and

Re: [PATCH v2 10/14] USB: ch341: fix coding style

On 04/02/2016 07:29 PM, Joe Perches wrote: > Most of the whitespace only changes are undesired. > Well, the style wasn't very consistent. I think consistency is important. So I took the liberty of deciding for one style and stuck to it. > Multi-line statements here are using alignment to >

Re: [PATCH v2 10/14] USB: ch341: fix coding style

On 04/02/2016 07:29 PM, Joe Perches wrote: > Most of the whitespace only changes are undesired. > Well, the style wasn't very consistent. I think consistency is important. So I took the liberty of deciding for one style and stuck to it. > Multi-line statements here are using alignment to >

Re: [PATCH] KERNEL: resource: Fix bug on leakage in /proc/iomem file

On Wed, Apr 6, 2016 at 8:20 AM, Linus Torvalds wrote: > > I'd much rather just not insert the resources in the first place then. So I'd find a patch like the attached to be perfectly acceptable (in fact, we should have done this long ago). That said, for a kernel

Re: [PATCH] KERNEL: resource: Fix bug on leakage in /proc/iomem file

On Wed, Apr 6, 2016 at 8:20 AM, Linus Torvalds wrote: > > I'd much rather just not insert the resources in the first place then. So I'd find a patch like the attached to be perfectly acceptable (in fact, we should have done this long ago). That said, for a kernel hardening thing, I think it

Re: [PATCH] x86 get_unmapped_area: Add PMD alignment for DAX PMD mmap

On Wed, 2016-04-06 at 12:50 -0400, Matthew Wilcox wrote: > On Wed, Apr 06, 2016 at 07:58:09AM -0600, Toshi Kani wrote: > > > > When CONFIG_FS_DAX_PMD is set, DAX supports mmap() using PMD page > > size.  This feature relies on both mmap virtual address and FS > > block data (i.e. physical

Re: [PATCH] x86 get_unmapped_area: Add PMD alignment for DAX PMD mmap

On Wed, 2016-04-06 at 12:50 -0400, Matthew Wilcox wrote: > On Wed, Apr 06, 2016 at 07:58:09AM -0600, Toshi Kani wrote: > > > > When CONFIG_FS_DAX_PMD is set, DAX supports mmap() using PMD page > > size.  This feature relies on both mmap virtual address and FS > > block data (i.e. physical

Re: [PATCH v5 0/9] arm64: Add support for KVM with ACPI

Hi Christoffer, On 06/04/2016 18:28, Christoffer Dall wrote: On Mon, Apr 04, 2016 at 12:37:31PM +0100, Julien Grall wrote: Hello, This patch series allows KVM to work with ACPI on ARM64. Currently, the firmware tables are parsed by the the virtual timer and virtual GIC code in order to

Re: [PATCH v5 0/9] arm64: Add support for KVM with ACPI

Hi Christoffer, On 06/04/2016 18:28, Christoffer Dall wrote: On Mon, Apr 04, 2016 at 12:37:31PM +0100, Julien Grall wrote: Hello, This patch series allows KVM to work with ACPI on ARM64. Currently, the firmware tables are parsed by the the virtual timer and virtual GIC code in order to

Re: [LINUX PATCH v2] gpio_keys: Added support to read the IRQ_FLAGS from devicetree

On Wed, Apr 06, 2016 at 11:32:55AM +, Nava kishore Manne wrote: > > -Original Message- > > From: Linus Walleij [mailto:linus.wall...@linaro.org] > > Sent: Monday, April 04, 2016 4:38 PM > > To: Nava kishore Manne > > Cc: Dmitry Torokhov; Andersson, Björn; Nava kishore Manne; Peng Fan;

Re: [LINUX PATCH v2] gpio_keys: Added support to read the IRQ_FLAGS from devicetree

On Wed, Apr 06, 2016 at 11:32:55AM +, Nava kishore Manne wrote: > > -Original Message- > > From: Linus Walleij [mailto:linus.wall...@linaro.org] > > Sent: Monday, April 04, 2016 4:38 PM > > To: Nava kishore Manne > > Cc: Dmitry Torokhov; Andersson, Björn; Nava kishore Manne; Peng Fan;

Re: [PATCH 09/11] mm, compaction: Abstract compaction feedback to helpers

On Tue, 5 Apr 2016 17:55:39 -0700 (PDT) Hugh Dickins wrote: > > I ended up doing this: > > > > /* Checks for THP-specific high-order allocations */ > > if (!is_thp_allocation(gfp_mask, order)) > > migration_mode = MIGRATE_SYNC_LIGHT; > > > > /* > >

Re: [PATCH v5 6/9] irqchip/gic-v3: Parse and export virtual GIC information

Hi Christoffer, On 06/04/2016 18:22, Christoffer Dall wrote: On Mon, Apr 04, 2016 at 12:37:37PM +0100, Julien Grall wrote: +static void __init gic_acpi_setup_kvm_info(void) +{ + int irq; + + if (!gic_acpi_collect_virt_info()) { + pr_warn("Unable to get hardware

Re: [PATCH 09/11] mm, compaction: Abstract compaction feedback to helpers

On Tue, 5 Apr 2016 17:55:39 -0700 (PDT) Hugh Dickins wrote: > > I ended up doing this: > > > > /* Checks for THP-specific high-order allocations */ > > if (!is_thp_allocation(gfp_mask, order)) > > migration_mode = MIGRATE_SYNC_LIGHT; > > > > /* > > * Checks for

Re: [PATCH v5 6/9] irqchip/gic-v3: Parse and export virtual GIC information

Hi Christoffer, On 06/04/2016 18:22, Christoffer Dall wrote: On Mon, Apr 04, 2016 at 12:37:37PM +0100, Julien Grall wrote: +static void __init gic_acpi_setup_kvm_info(void) +{ + int irq; + + if (!gic_acpi_collect_virt_info()) { + pr_warn("Unable to get hardware

Re: [PATCH v5 4/9] irqchip/gic-v2: Parse and export virtual GIC information

Hi Christoffer, On 06/04/2016 18:04, Christoffer Dall wrote: On Mon, Apr 04, 2016 at 12:37:35PM +0100, Julien Grall wrote: diff --git a/include/linux/irqchip/arm-gic-common.h b/include/linux/irqchip/arm-gic-common.h new file mode 100644 index 000..ef34f6f --- /dev/null +++

Re: [PATCH v5 4/9] irqchip/gic-v2: Parse and export virtual GIC information

Hi Christoffer, On 06/04/2016 18:04, Christoffer Dall wrote: On Mon, Apr 04, 2016 at 12:37:35PM +0100, Julien Grall wrote: diff --git a/include/linux/irqchip/arm-gic-common.h b/include/linux/irqchip/arm-gic-common.h new file mode 100644 index 000..ef34f6f --- /dev/null +++

Re: [PATCH] Input: Do not add SYN_REPORT in between a single packet data

On Wed, Apr 06, 2016 at 08:26:39PM +0530, Aniroop Mathur wrote: > On Sat, Apr 2, 2016 at 10:31 PM, Aniroop Mathur > wrote: > > Hello Mr. Torokhov, > > > > First of all, Thank you for your reply. > > > > On Sat, Apr 2, 2016 at 3:21 AM, Dmitry Torokhov > >

Re: [PATCH] Input: Do not add SYN_REPORT in between a single packet data

On Wed, Apr 06, 2016 at 08:26:39PM +0530, Aniroop Mathur wrote: > On Sat, Apr 2, 2016 at 10:31 PM, Aniroop Mathur > wrote: > > Hello Mr. Torokhov, > > > > First of all, Thank you for your reply. > > > > On Sat, Apr 2, 2016 at 3:21 AM, Dmitry Torokhov > > wrote: > >> On Fri, Mar 11, 2016 at

[PATCH 3/4] mailbox/omap: remove FSF mailing address paragraph

Remove the paragraph about writing to the Free Software Foundation's mailing address from the GPL license header as this address can change. This fixes the corresponding checkpatch warning. Signed-off-by: Suman Anna --- drivers/mailbox/omap-mailbox.c | 6 -- 1 file changed, 6

[PATCH 1/4] mailbox/omap: drop legacy platform device support

OMAP mailbox devices can no longer be created in legacy non-DT mode, all the relevant code has been cleaned up. The OMAP mailbox driver will only support devices created from DT going forward, so drop the legacy platform device support from the driver. Signed-off-by: Suman Anna

[PATCH 4/4] mailbox/omap: add blank lines after declarations

Fix couple of checkpatch warnings of the type, "WARNING: Missing a blank line after declarations" Also, fixed a warning about a space after a typecast while at this. Signed-off-by: Suman Anna --- drivers/mailbox/omap-mailbox.c | 7 ++- 1 file changed, 6 insertions(+), 1

[PATCH 3/4] mailbox/omap: remove FSF mailing address paragraph

Remove the paragraph about writing to the Free Software Foundation's mailing address from the GPL license header as this address can change. This fixes the corresponding checkpatch warning. Signed-off-by: Suman Anna --- drivers/mailbox/omap-mailbox.c | 6 -- 1 file changed, 6 deletions(-)

[PATCH 1/4] mailbox/omap: drop legacy platform device support

OMAP mailbox devices can no longer be created in legacy non-DT mode, all the relevant code has been cleaned up. The OMAP mailbox driver will only support devices created from DT going forward, so drop the legacy platform device support from the driver. Signed-off-by: Suman Anna ---

[PATCH 4/4] mailbox/omap: add blank lines after declarations

Fix couple of checkpatch warnings of the type, "WARNING: Missing a blank line after declarations" Also, fixed a warning about a space after a typecast while at this. Signed-off-by: Suman Anna --- drivers/mailbox/omap-mailbox.c | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-) diff

[PATCH 0/4] OMAP Mailbox legacy platform device support removal

Hi Jassi, This series cleans up the OMAP Mailbox driver dropping the support for legacy non-DT platform devices. The infrastructure for creating any such devices has all been cleaned up from the mach-omap2 layers. The removal from the driver is accomplished in patch 1, while the remaining

[PATCH 2/4] mailbox/omap: use variable name for sizeof() operator

Fix the code formatting to use the kernel preferred style of using the actual variables to determize the size using the sizeof() operator. This fixes the corresponding checkpatch warning as well. Signed-off-by: Suman Anna --- drivers/mailbox/omap-mailbox.c | 2 +- 1 file changed,

[PATCH 0/4] OMAP Mailbox legacy platform device support removal

Hi Jassi, This series cleans up the OMAP Mailbox driver dropping the support for legacy non-DT platform devices. The infrastructure for creating any such devices has all been cleaned up from the mach-omap2 layers. The removal from the driver is accomplished in patch 1, while the remaining

[PATCH 2/4] mailbox/omap: use variable name for sizeof() operator

Fix the code formatting to use the kernel preferred style of using the actual variables to determize the size using the sizeof() operator. This fixes the corresponding checkpatch warning as well. Signed-off-by: Suman Anna --- drivers/mailbox/omap-mailbox.c | 2 +- 1 file changed, 1

Re: [PATCH] csiostor: Fix backwards locking in the function __csio_unreg_rnode

On 2016-04-06 01:28 PM, James Bottomley wrote: > On Wed, 2016-04-06 at 13:23 -0400, Bastien Philbert wrote: >> >> On 2016-04-06 01:14 PM, James Bottomley wrote: >>> On Wed, 2016-04-06 at 10:36 -0400, Bastien Philbert wrote: On 2016-04-06 10:24 AM, James Bottomley wrote: > On Wed,

Re: [PATCH] csiostor: Fix backwards locking in the function __csio_unreg_rnode

On 2016-04-06 01:28 PM, James Bottomley wrote: > On Wed, 2016-04-06 at 13:23 -0400, Bastien Philbert wrote: >> >> On 2016-04-06 01:14 PM, James Bottomley wrote: >>> On Wed, 2016-04-06 at 10:36 -0400, Bastien Philbert wrote: On 2016-04-06 10:24 AM, James Bottomley wrote: > On Wed,

[PATCH] extcon: usb-gpio: switch to use pm wakeirq apis

Switch to use PM wakeirq APIs which automates wakeup IRQs enabling/disabling and so allows to make code simpler. Signed-off-by: Grygorii Strashko --- Unfortunately this simple patch depends on: "[RFC PATCH] PM / wakeirq: fix wakeirq setting after wakup re-configuration

[PATCH] extcon: usb-gpio: switch to use pm wakeirq apis

Switch to use PM wakeirq APIs which automates wakeup IRQs enabling/disabling and so allows to make code simpler. Signed-off-by: Grygorii Strashko --- Unfortunately this simple patch depends on: "[RFC PATCH] PM / wakeirq: fix wakeirq setting after wakup re-configuration from sysfs"

Re: [PATCH v4 3/3] ARM: dts: use syscon in cygnus touchscreen dt node

On Sat, Feb 27, 2016 at 12:29:56PM +0530, Raveendra Padasalagi wrote: > In Cygnus SOC touch screen controller registers are shared > with ADC and flex timer. Using readl/writel could lead to > race condition. So touchscreen driver is enhanced to support > syscon based register access to take care

Re: [PATCH v4 3/3] ARM: dts: use syscon in cygnus touchscreen dt node

On Sat, Feb 27, 2016 at 12:29:56PM +0530, Raveendra Padasalagi wrote: > In Cygnus SOC touch screen controller registers are shared > with ADC and flex timer. Using readl/writel could lead to > race condition. So touchscreen driver is enhanced to support > syscon based register access to take care

Re: [PATCH v5 0/9] arm64: Add support for KVM with ACPI

On Mon, Apr 04, 2016 at 12:37:31PM +0100, Julien Grall wrote: > Hello, > > This patch series allows KVM to work with ACPI on ARM64. > > Currently, the firmware tables are parsed by the the virtual timer and virtual > GIC code in order to configure them correctly. > > However the parsing of

Re: [PATCH v5 0/9] arm64: Add support for KVM with ACPI

On Mon, Apr 04, 2016 at 12:37:31PM +0100, Julien Grall wrote: > Hello, > > This patch series allows KVM to work with ACPI on ARM64. > > Currently, the firmware tables are parsed by the the virtual timer and virtual > GIC code in order to configure them correctly. > > However the parsing of

Re: [PATCH] csiostor: Fix backwards locking in the function __csio_unreg_rnode

On Wed, 2016-04-06 at 13:23 -0400, Bastien Philbert wrote: > > On 2016-04-06 01:14 PM, James Bottomley wrote: > > On Wed, 2016-04-06 at 10:36 -0400, Bastien Philbert wrote: > > > > > > On 2016-04-06 10:24 AM, James Bottomley wrote: > > > > On Wed, 2016-04-06 at 10:11 -0400, Bastien Philbert

Re: [PATCH] csiostor: Fix backwards locking in the function __csio_unreg_rnode

On Wed, 2016-04-06 at 13:23 -0400, Bastien Philbert wrote: > > On 2016-04-06 01:14 PM, James Bottomley wrote: > > On Wed, 2016-04-06 at 10:36 -0400, Bastien Philbert wrote: > > > > > > On 2016-04-06 10:24 AM, James Bottomley wrote: > > > > On Wed, 2016-04-06 at 10:11 -0400, Bastien Philbert

Re: [PATCH v5 5/9] irqchip/gic-v3: Gather all ACPI specific data in a single structure

On Mon, Apr 04, 2016 at 12:37:36PM +0100, Julien Grall wrote: > The ACPI code requires to use global variales in order to collect s/variales/variables/ > information from the tables. > > To make clear those variables are ACPI specific, gather all of them in a > single structure. > >

Re: [PATCH v5 8/9] KVM: arm/arm64: vgic: Rely on the GIC driver to parse the firmware tables

On Mon, Apr 04, 2016 at 12:37:39PM +0100, Julien Grall wrote: > Currently, the firmware tables are parsed 2 times: once in the GIC > drivers, the other time when initializing the vGIC. It means code > duplication and make more tedious to add the support for another > firmware table (like ACPI). >

Re: [PATCH v5 5/9] irqchip/gic-v3: Gather all ACPI specific data in a single structure

On Mon, Apr 04, 2016 at 12:37:36PM +0100, Julien Grall wrote: > The ACPI code requires to use global variales in order to collect s/variales/variables/ > information from the tables. > > To make clear those variables are ACPI specific, gather all of them in a > single structure. > >

Re: [PATCH v5 8/9] KVM: arm/arm64: vgic: Rely on the GIC driver to parse the firmware tables

On Mon, Apr 04, 2016 at 12:37:39PM +0100, Julien Grall wrote: > Currently, the firmware tables are parsed 2 times: once in the GIC > drivers, the other time when initializing the vGIC. It means code > duplication and make more tedious to add the support for another > firmware table (like ACPI). >

Re: [PATCH v5 1/9] clocksource: arm_arch_timer: Gather KVM specific information in a structure

On Mon, Apr 04, 2016 at 12:37:32PM +0100, Julien Grall wrote: > Introduce a structure which are filled up by the arch timer driver and > used by the virtual timer in KVM. > > The first member of this structure will be the timecounter. More members > will be added later. > > A stub for the new

Re: [PATCH v5 2/9] clocksource: arm_arch_timer: Extend arch_timer_kvm_info to get the virtual IRQ

On Mon, Apr 04, 2016 at 12:37:33PM +0100, Julien Grall wrote: > Currently, the firmware table is parsed by the virtual timer code in > order to retrieve the virtual timer interrupt. However, this is already > done by the arch timer driver. > > To avoid code duplication, extend arch_timer_kvm_info

Re: [PATCH v10 4/9] phy: Add Tegra XUSB pad controller support

On Wed, Apr 06, 2016 at 06:13:42PM +0530, Kishon Vijay Abraham I wrote: > On Friday 04 March 2016 09:49 PM, Thierry Reding wrote: [...] > > +struct tegra124_xusb_fuse_calibration { > > + u32 hs_curr_level[3]; > > + u32 hs_iref_cap; > > + u32 hs_term_range_adj; > > + u32 hs_squelch_level; >

Re: [PATCH v5 1/9] clocksource: arm_arch_timer: Gather KVM specific information in a structure

On Mon, Apr 04, 2016 at 12:37:32PM +0100, Julien Grall wrote: > Introduce a structure which are filled up by the arch timer driver and > used by the virtual timer in KVM. > > The first member of this structure will be the timecounter. More members > will be added later. > > A stub for the new

Re: [PATCH v5 2/9] clocksource: arm_arch_timer: Extend arch_timer_kvm_info to get the virtual IRQ

On Mon, Apr 04, 2016 at 12:37:33PM +0100, Julien Grall wrote: > Currently, the firmware table is parsed by the virtual timer code in > order to retrieve the virtual timer interrupt. However, this is already > done by the arch timer driver. > > To avoid code duplication, extend arch_timer_kvm_info

Re: [PATCH v10 4/9] phy: Add Tegra XUSB pad controller support

On Wed, Apr 06, 2016 at 06:13:42PM +0530, Kishon Vijay Abraham I wrote: > On Friday 04 March 2016 09:49 PM, Thierry Reding wrote: [...] > > +struct tegra124_xusb_fuse_calibration { > > + u32 hs_curr_level[3]; > > + u32 hs_iref_cap; > > + u32 hs_term_range_adj; > > + u32 hs_squelch_level; >

Re: Bug with paravirt ops and livepatches

+++ Miroslav Benes [06/04/16 10:43 +0200]: On Wed, 6 Apr 2016, Miroslav Benes wrote: Anyway I see there are some new comments on github. I'll look at those. But I'd prefer to discuss all the relevant things (that is kpatch unspecific) here. It would make it easier. And you do (after seeing

Re: [PATCH] csiostor: Fix backwards locking in the function __csio_unreg_rnode

On 2016-04-06 01:14 PM, James Bottomley wrote: > On Wed, 2016-04-06 at 10:36 -0400, Bastien Philbert wrote: >> >> On 2016-04-06 10:24 AM, James Bottomley wrote: >>> On Wed, 2016-04-06 at 10:11 -0400, Bastien Philbert wrote: On 2016-04-06 09:38 AM, James Bottomley wrote: > On Wed,

Re: Bug with paravirt ops and livepatches

+++ Miroslav Benes [06/04/16 10:43 +0200]: On Wed, 6 Apr 2016, Miroslav Benes wrote: Anyway I see there are some new comments on github. I'll look at those. But I'd prefer to discuss all the relevant things (that is kpatch unspecific) here. It would make it easier. And you do (after seeing

Re: [PATCH] csiostor: Fix backwards locking in the function __csio_unreg_rnode

On 2016-04-06 01:14 PM, James Bottomley wrote: > On Wed, 2016-04-06 at 10:36 -0400, Bastien Philbert wrote: >> >> On 2016-04-06 10:24 AM, James Bottomley wrote: >>> On Wed, 2016-04-06 at 10:11 -0400, Bastien Philbert wrote: On 2016-04-06 09:38 AM, James Bottomley wrote: > On Wed,

Re: [PATCH v5 6/9] irqchip/gic-v3: Parse and export virtual GIC information

On Mon, Apr 04, 2016 at 12:37:37PM +0100, Julien Grall wrote: > Fill up the recently introduced gic_kvm_info with the hardware > information used for virtualization. > > Signed-off-by: Julien Grall > Cc: Thomas Gleixner > Cc: Jason Cooper

Re: [PATCH] MAINTAINERS: add entry for QEMU

On Tue, Apr 05, 2016 at 11:31:27AM +0300, Michael S. Tsirkin wrote: > Gabriel merged support for QEMU FW CFG interface, but there's apparently > no official maintainer. It's also possible that this will grow more > interfaces in future. I'll happily co-maintain it and handle pull > requests

Re: [PATCH v5 6/9] irqchip/gic-v3: Parse and export virtual GIC information

On Mon, Apr 04, 2016 at 12:37:37PM +0100, Julien Grall wrote: > Fill up the recently introduced gic_kvm_info with the hardware > information used for virtualization. > > Signed-off-by: Julien Grall > Cc: Thomas Gleixner > Cc: Jason Cooper > Cc: Marc Zyngier > > --- > Changes in v5: >

Re: [PATCH] MAINTAINERS: add entry for QEMU

On Tue, Apr 05, 2016 at 11:31:27AM +0300, Michael S. Tsirkin wrote: > Gabriel merged support for QEMU FW CFG interface, but there's apparently > no official maintainer. It's also possible that this will grow more > interfaces in future. I'll happily co-maintain it and handle pull > requests

Applied "regulator: s2mps11: Use module_platform_driver() instead subsys initcall" to the regulator tree

The patch regulator: s2mps11: Use module_platform_driver() instead subsys initcall has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually

Applied "regulator: max77686: Use module_platform_driver() instead subsys initcall" to the regulator tree

The patch regulator: max77686: Use module_platform_driver() instead subsys initcall has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually

Applied "regulator: s2mps11: Use module_platform_driver() instead subsys initcall" to the regulator tree

The patch regulator: s2mps11: Use module_platform_driver() instead subsys initcall has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually

Applied "regulator: max77686: Use module_platform_driver() instead subsys initcall" to the regulator tree

The patch regulator: max77686: Use module_platform_driver() instead subsys initcall has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually

Applied "regulator: twl: Fix a typo in twl4030_send_pb_msg" to the regulator tree

The patch regulator: twl: Fix a typo in twl4030_send_pb_msg has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours)

Applied "regulator: twl: Fix a typo in twl4030_send_pb_msg" to the regulator tree

The patch regulator: twl: Fix a typo in twl4030_send_pb_msg has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours)

[PATCH] HID: simplify implement() a bit

The 'size' variable is not really needed, and we can also shift constant in the loop body when masking off existing bits. Also we do not have to us 64 bit calculations if we take an extra branch. Suggested-by: Doug Anderson Signed-off-by: Dmitry Torokhov

[PATCH] HID: simplify implement() a bit

The 'size' variable is not really needed, and we can also shift constant in the loop body when masking off existing bits. Also we do not have to us 64 bit calculations if we take an extra branch. Suggested-by: Doug Anderson Signed-off-by: Dmitry Torokhov --- drivers/hid/hid-core.c | 33

Re: [PATCH] ASoC: mediatek: Add second I2S on mt8173-rt5650 machine driver

On Wed, Apr 06, 2016 at 09:58:25PM +0800, PC Liao wrote: > On Sun, 2016-04-03 at 01:04 +0800, Mark Brown wrote: > > Any driver that can identify an individual DAI within a device by using > > sound-dai references, even simple-card does this. > Thanks for suggestion. > This machine driver is

Re: [PATCH] ASoC: mediatek: Add second I2S on mt8173-rt5650 machine driver

On Wed, Apr 06, 2016 at 09:58:25PM +0800, PC Liao wrote: > On Sun, 2016-04-03 at 01:04 +0800, Mark Brown wrote: > > Any driver that can identify an individual DAI within a device by using > > sound-dai references, even simple-card does this. > Thanks for suggestion. > This machine driver is

Re: [PATCH] qemu_fw_cfg: don't leak kobj on init error

On Sun, Apr 03, 2016 at 03:23:19PM +0300, Michael S. Tsirkin wrote: > If platform_driver_register fails, we should > cleanup fw_cfg_top_ko before exiting. > > Signed-off-by: Michael S. Tsirkin Acked-by: Gabriel Somlo Thanks, --Gabriel > --- >

Re: [PATCH] qemu_fw_cfg: don't leak kobj on init error

On Sun, Apr 03, 2016 at 03:23:19PM +0300, Michael S. Tsirkin wrote: > If platform_driver_register fails, we should > cleanup fw_cfg_top_ko before exiting. > > Signed-off-by: Michael S. Tsirkin Acked-by: Gabriel Somlo Thanks, --Gabriel > --- > drivers/firmware/qemu_fw_cfg.c | 8 +++- > 1

Re: [PATCH net] net: sched: do not requeue a NULL skb

On Wed, Apr 6, 2016 at 6:10 AM, Lars Persson wrote: > A failure in validate_xmit_skb_list() triggered an unconditional call > to dev_requeue_skb with skb=NULL. This slowly grows the queue > discipline's qlen count until all traffic through the queue stops. > Sounds

Re: [PATCH net] net: sched: do not requeue a NULL skb

On Wed, Apr 6, 2016 at 6:10 AM, Lars Persson wrote: > A failure in validate_xmit_skb_list() triggered an unconditional call > to dev_requeue_skb with skb=NULL. This slowly grows the queue > discipline's qlen count until all traffic through the queue stops. > Sounds reasonable. > Fixes:

Re: [PATCH] csiostor: Fix backwards locking in the function __csio_unreg_rnode

On Wed, 2016-04-06 at 10:36 -0400, Bastien Philbert wrote: > > On 2016-04-06 10:24 AM, James Bottomley wrote: > > On Wed, 2016-04-06 at 10:11 -0400, Bastien Philbert wrote: > > > > > > On 2016-04-06 09:38 AM, James Bottomley wrote: > > > > On Wed, 2016-04-06 at 09:21 -0400, Bastien Philbert

Re: [PATCH] csiostor: Fix backwards locking in the function __csio_unreg_rnode

On Wed, 2016-04-06 at 10:36 -0400, Bastien Philbert wrote: > > On 2016-04-06 10:24 AM, James Bottomley wrote: > > On Wed, 2016-04-06 at 10:11 -0400, Bastien Philbert wrote: > > > > > > On 2016-04-06 09:38 AM, James Bottomley wrote: > > > > On Wed, 2016-04-06 at 09:21 -0400, Bastien Philbert

Re: [PATCH next 1/2] PCI: keystone: add pci error irq handler

On 03/22/2016 06:23 PM, kbuild test robot wrote: > Hi Murali, > > [auto build test ERROR on next-20160322] > > url: > https://github.com/0day-ci/linux/commits/Murali-Karicheri/PCI-keystone-add-pci-error-irq-handler/20160323-035516 > config: arm-multi_v7_defconfig (attached as .config) >

Re: [PATCH next 1/2] PCI: keystone: add pci error irq handler

On 03/22/2016 06:23 PM, kbuild test robot wrote: > Hi Murali, > > [auto build test ERROR on next-20160322] > > url: > https://github.com/0day-ci/linux/commits/Murali-Karicheri/PCI-keystone-add-pci-error-irq-handler/20160323-035516 > config: arm-multi_v7_defconfig (attached as .config) >

Re: [PATCH v10 3/9] dt-bindings: phy: tegra-xusb-padctl: Add Tegra210 support

On Tue, Apr 05, 2016 at 03:10:16PM -0600, Stephen Warren wrote: > On 04/05/2016 08:44 AM, Thierry Reding wrote: > > On Wed, Mar 16, 2016 at 11:59:44AM -0600, Stephen Warren wrote: > > > On 03/04/2016 09:19 AM, Thierry Reding wrote: > > > > From: Thierry Reding > > > > > > > >

Re: [PATCH v10 3/9] dt-bindings: phy: tegra-xusb-padctl: Add Tegra210 support

On Tue, Apr 05, 2016 at 03:10:16PM -0600, Stephen Warren wrote: > On 04/05/2016 08:44 AM, Thierry Reding wrote: > > On Wed, Mar 16, 2016 at 11:59:44AM -0600, Stephen Warren wrote: > > > On 03/04/2016 09:19 AM, Thierry Reding wrote: > > > > From: Thierry Reding > > > > > > > > Extend the binding

Re: [PATCH] IMA: Use the system trusted keyrings instead of .ima_mok (update)

On Wed, 2016-04-06 at 17:24 +0100, David Howells wrote: > Looking in digsig.c, I see: > > #ifdef CONFIG_INTEGRITY_TRUSTED_KEYRING > static bool init_keyring __initdata = true; > #else > static bool init_keyring __initdata; > #endif > > Since this doesn't ever appear

Re: [PATCH] IMA: Use the system trusted keyrings instead of .ima_mok (update)

On Wed, 2016-04-06 at 17:24 +0100, David Howells wrote: > Looking in digsig.c, I see: > > #ifdef CONFIG_INTEGRITY_TRUSTED_KEYRING > static bool init_keyring __initdata = true; > #else > static bool init_keyring __initdata; > #endif > > Since this doesn't ever appear

Re: [PATCH] btrfs:Change BUG_ON to new error path in __clear_extent_bit

On 2016-04-06 12:10 PM, Filipe Manana wrote: > On Wed, Apr 6, 2016 at 4:56 PM, Bastien Philbert > wrote: >> This remove the unnessary BUG_ON if the allocation with >> alloc_extent_state_atomic fails due to this function >> failure not being unrecoverable. Instead we

Re: [PATCH] btrfs:Change BUG_ON to new error path in __clear_extent_bit

On 2016-04-06 12:10 PM, Filipe Manana wrote: > On Wed, Apr 6, 2016 at 4:56 PM, Bastien Philbert > wrote: >> This remove the unnessary BUG_ON if the allocation with >> alloc_extent_state_atomic fails due to this function >> failure not being unrecoverable. Instead we now change >> this BUG_ON

RE: [PATCH] sched/cpuacct: Check for NULL when using task_pt_regs()

> -Original Message- > From: Srikar Dronamraju [mailto:sri...@linux.vnet.ibm.com] > Sent: Wednesday, April 06, 2016 9:27 PM > To: Anton Blanchard > Cc: Peter Zijlstra ; Ingo Molnar ; > t...@linutronix.de; efa...@gmx.de;

RE: [PATCH] sched/cpuacct: Check for NULL when using task_pt_regs()

> -Original Message- > From: Srikar Dronamraju [mailto:sri...@linux.vnet.ibm.com] > Sent: Wednesday, April 06, 2016 9:27 PM > To: Anton Blanchard > Cc: Peter Zijlstra ; Ingo Molnar ; > t...@linutronix.de; efa...@gmx.de; hte...@gmail.com; > linux-kernel@vger.kernel.org; t...@kernel.org;

Re: [PATCH v5 4/9] irqchip/gic-v2: Parse and export virtual GIC information

On Mon, Apr 04, 2016 at 12:37:35PM +0100, Julien Grall wrote: > For now, the firmware tables are parsed 2 times: once in the GIC > drivers, the other timer when initializing the vGIC. It means code > duplication and make more tedious to add the support for another > firmware table (like ACPI). >

Re: [PATCH v5 4/9] irqchip/gic-v2: Parse and export virtual GIC information

On Mon, Apr 04, 2016 at 12:37:35PM +0100, Julien Grall wrote: > For now, the firmware tables are parsed 2 times: once in the GIC > drivers, the other timer when initializing the vGIC. It means code > duplication and make more tedious to add the support for another > firmware table (like ACPI). >

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

On Wed, Apr 06, 2016 at 09:15:26AM +0800, Peter Chen wrote: > > > No, this comment is common one, but only for SW detection. Eg, when > > > the PMIC tells you it is a SDP, you can't notify to charger IC about > > > 500mA at once, you need to do it after host allows you to do it. > > Note that

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

On Wed, Apr 06, 2016 at 09:15:26AM +0800, Peter Chen wrote: > > > No, this comment is common one, but only for SW detection. Eg, when > > > the PMIC tells you it is a SDP, you can't notify to charger IC about > > > 500mA at once, you need to do it after host allows you to do it. > > Note that

Re: [PATCH 1/2] thermal: generic-adc: Add DT binding for ADC based thermal sensor driver

Hi Eduardo, Thanks for review. On Wednesday 06 April 2016 09:31 PM, Eduardo Valentin wrote: On Wed, Apr 06, 2016 at 03:33:05PM +0530, Laxman Dewangan wrote: +- step-temperature: The temperature steps for the reading ADC +value in millicelsius. How about

Re: [PATCH 1/2] thermal: generic-adc: Add DT binding for ADC based thermal sensor driver

Hi Eduardo, Thanks for review. On Wednesday 06 April 2016 09:31 PM, Eduardo Valentin wrote: On Wed, Apr 06, 2016 at 03:33:05PM +0530, Laxman Dewangan wrote: +- step-temperature: The temperature steps for the reading ADC +value in millicelsius. How about

Re: [PATCH] perf/x86/intel/pt: Use boot_cpu_has() because it's there

On Wed, Apr 06, 2016 at 05:35:07PM +0300, Alexander Shishkin wrote: > At the moment, initialization path is using test_cpu_cap(_cpu_data), > to detect PT, which is just open coding boot_cpu_has(). Use the latter > instead. > > Signed-off-by: Alexander Shishkin

Re: [PATCH] perf/x86/intel/pt: Use boot_cpu_has() because it's there

On Wed, Apr 06, 2016 at 05:35:07PM +0300, Alexander Shishkin wrote: > At the moment, initialization path is using test_cpu_cap(_cpu_data), > to detect PT, which is just open coding boot_cpu_has(). Use the latter > instead. > > Signed-off-by: Alexander Shishkin > --- > arch/x86/events/intel/pt.c

<    4   5   6   7   8   9   10   11   12   13   >