Re: [PATCH v3 4/8] gpio: dt-bindings: Add documentation for Aspeed GPIO controllers

On Tue, Aug 30, 2016 at 05:24:23PM +0930, Andrew Jeffery wrote: > Signed-off-by: Andrew Jeffery > Acked-by: Joel Stanley > --- > .../devicetree/bindings/gpio/gpio-aspeed.txt | 36 > ++ > 1 file changed, 36 insertions(+) > create mode

Re: [PATCH v3 4/8] gpio: dt-bindings: Add documentation for Aspeed GPIO controllers

On Tue, Aug 30, 2016 at 05:24:23PM +0930, Andrew Jeffery wrote: > Signed-off-by: Andrew Jeffery > Acked-by: Joel Stanley > --- > .../devicetree/bindings/gpio/gpio-aspeed.txt | 36 > ++ > 1 file changed, 36 insertions(+) > create mode 100644

Re: RFC: Backport HID-logitech to 3.10?

On Fri, September 2, 2016 3:32 am, Benjamin Tissoires wrote: > On Thu, Sep 1, 2016 at 2:56 AM, Simon Wood wrote: >> After copying the HEAD 'hid-lg.[ch]' and 'hid-lg4ff.[ch]' from 4.7, >> there is a minimal patch (example attached) required to get the build >> working. > >

Re: RFC: Backport HID-logitech to 3.10?

On Fri, September 2, 2016 3:32 am, Benjamin Tissoires wrote: > On Thu, Sep 1, 2016 at 2:56 AM, Simon Wood wrote: >> After copying the HEAD 'hid-lg.[ch]' and 'hid-lg4ff.[ch]' from 4.7, >> there is a minimal patch (example attached) required to get the build >> working. > > Don't you need

Re: [PATCH v4 2/4] drm: Add API for capturing frame CRCs

Hi Tomeu, On 5 August 2016 at 11:45, Tomeu Vizoso wrote: > +#ifdef CONFIG_DEBUG_FS > + spin_lock_init(>crc.lock); > + init_waitqueue_head(>crc.wq); > + crtc->crc.source = kstrdup("auto", GFP_KERNEL); Pedantic: kstrdup() can never fail ? > +#endif >

Re: [PATCH v4 2/4] drm: Add API for capturing frame CRCs

Hi Tomeu, On 5 August 2016 at 11:45, Tomeu Vizoso wrote: > +#ifdef CONFIG_DEBUG_FS > + spin_lock_init(>crc.lock); > + init_waitqueue_head(>crc.wq); > + crtc->crc.source = kstrdup("auto", GFP_KERNEL); Pedantic: kstrdup() can never fail ? > +#endif > + > if

Re: [writeback] 8bc4ad9498: INFO: suspicious RCU usage. ]

(cc'ing Paul, hi!) Hello, On Thu, Sep 01, 2016 at 02:13:34PM -0600, Jens Axboe wrote: > On 09/01/2016 04:21 AM, kernel test robot wrote: > > [7.323356] cdrom: Uniform CD-ROM driver Revision: 3.20 > > [7.334239] > > [7.337256] === > > [7.340532] [ INFO:

Re: [writeback] 8bc4ad9498: INFO: suspicious RCU usage. ]

(cc'ing Paul, hi!) Hello, On Thu, Sep 01, 2016 at 02:13:34PM -0600, Jens Axboe wrote: > On 09/01/2016 04:21 AM, kernel test robot wrote: > > [7.323356] cdrom: Uniform CD-ROM driver Revision: 3.20 > > [7.334239] > > [7.337256] === > > [7.340532] [ INFO:

Re: [PATCH net-next 3/3] net: dsa: mv88e6xxx: make global2 code optional

On Fri, Sep 02, 2016 at 08:08:19AM -0400, Vivien Didelot wrote: > Since not every chip has a Global2 set of registers, make its support > optional, in which case the related functions will return -EOPNOTSUPP. > > This also allows to reduce the size of the mv88e6xxx driver for devices > such as

Re: [PATCH net-next 3/3] net: dsa: mv88e6xxx: make global2 code optional

On Fri, Sep 02, 2016 at 08:08:19AM -0400, Vivien Didelot wrote: > Since not every chip has a Global2 set of registers, make its support > optional, in which case the related functions will return -EOPNOTSUPP. > > This also allows to reduce the size of the mv88e6xxx driver for devices > such as

[PATCH] serial: earlycon: Extend earlycon command line option to support 64-bit addresses

earlycon implementation used "unsigned long" internally, but there are systems (ARM with LPAE) where sizeof(unsigned long) == 4 and uart is mapped beyond 4GiB address range. Switch to resource_size_t internally and replace obsoleted simple_strtoul() with kstrtoull(). Signed-off-by: Alexander

[PATCH] serial: earlycon: Extend earlycon command line option to support 64-bit addresses

earlycon implementation used "unsigned long" internally, but there are systems (ARM with LPAE) where sizeof(unsigned long) == 4 and uart is mapped beyond 4GiB address range. Switch to resource_size_t internally and replace obsoleted simple_strtoul() with kstrtoull(). Signed-off-by: Alexander

Re: [git pull] drm fixes for rc5

On Thu, Sep 1, 2016 at 10:59 PM, Dave Airlie wrote: > > I've tried using a signed tag, let's see if works. Worked fine. But your email was once again marked as spam. Google hates you, and your email habits. Linus

Re: [git pull] drm fixes for rc5

On Thu, Sep 1, 2016 at 10:59 PM, Dave Airlie wrote: > > I've tried using a signed tag, let's see if works. Worked fine. But your email was once again marked as spam. Google hates you, and your email habits. Linus

Re: [PATCH 2/5] irqtime: Remove needless IRQs disablement on kcpustat update

On 02/09/2016 16:03, Frederic Weisbecker wrote: > The callers of the functions performing irqtime kcpustat updates have > IRQS disabled, no need to disable them again. They do, but perhaps this should be annotated through some sparse magic. It's starting to be hairy, with the requirement

Re: [PATCH 2/5] irqtime: Remove needless IRQs disablement on kcpustat update

On 02/09/2016 16:03, Frederic Weisbecker wrote: > The callers of the functions performing irqtime kcpustat updates have > IRQS disabled, no need to disable them again. They do, but perhaps this should be annotated through some sparse magic. It's starting to be hairy, with the requirement

Re: [PATCH 1/2] ARM: dts: am57xx-beagle-x15: Remove pinmux configurations

On 09/02/2016 05:18 AM, Sekhar Nori wrote: On Friday 02 September 2016 02:35 PM, Nishanth Menon wrote: pinmuxing for DRA7x/AM57x family of processors need to be done in IO isolation as part of initial bootloader executed from SRAM. This is done as part of iodelay configuration sequence and is

Re: [PATCH 1/2] ARM: dts: am57xx-beagle-x15: Remove pinmux configurations

On 09/02/2016 05:18 AM, Sekhar Nori wrote: On Friday 02 September 2016 02:35 PM, Nishanth Menon wrote: pinmuxing for DRA7x/AM57x family of processors need to be done in IO isolation as part of initial bootloader executed from SRAM. This is done as part of iodelay configuration sequence and is

Re: [PATCH v3 2/4] dt-bindings: arm: Add Sierra Wireless modules bindings

On Tue, Aug 23, 2016 at 01:39:04PM +0200, Neil Armstrong wrote: > Signed-off-by: Neil Armstrong > --- > Documentation/devicetree/bindings/arm/swir.txt | 12 > 1 file changed, 12 insertions(+) > create mode 100644

Re: [PATCH v3 2/4] dt-bindings: arm: Add Sierra Wireless modules bindings

On Tue, Aug 23, 2016 at 01:39:04PM +0200, Neil Armstrong wrote: > Signed-off-by: Neil Armstrong > --- > Documentation/devicetree/bindings/arm/swir.txt | 12 > 1 file changed, 12 insertions(+) > create mode 100644 Documentation/devicetree/bindings/arm/swir.txt Acked-by: Rob Herring

[PATCH v2 2/2] crypto: qat - fix resource release omissions

In certain cases qat_uclo_parse_uof_obj used to return with an error code before releasing all resources. This patch add a jump to the appropriate label ensuring that the resources are properly released before returning. This issue was found with Hector. Signed-off-by: Quentin Lambert

[PATCH v2 2/2] crypto: qat - fix resource release omissions

In certain cases qat_uclo_parse_uof_obj used to return with an error code before releasing all resources. This patch add a jump to the appropriate label ensuring that the resources are properly released before returning. This issue was found with Hector. Signed-off-by: Quentin Lambert ---

[PATCH v2 1/2] crypto: qat - introduces a variable to handle error codes

Most error code used to jump to a label that lead to a "return -EFAULT" statement. This patch introduces a variable that stores the error code so that other error branches can use the same label to exit. Signed-off-by: Quentin Lambert ---

[PATCH v2 1/2] crypto: qat - introduces a variable to handle error codes

Most error code used to jump to a label that lead to a "return -EFAULT" statement. This patch introduces a variable that stores the error code so that other error branches can use the same label to exit. Signed-off-by: Quentin Lambert --- drivers/crypto/qat/qat_common/qat_uclo.c | 13

[PATCH v2 0/2] add omitted release in qat_common

The first patch introduces a variable to handle different error codes and be able to reuse the same clean up code. The second add an omitted release by jumping to the clean code having set the returned value to the proper error code. -changes since v1 I failed to send the first version properly

[PATCH v2 0/2] add omitted release in qat_common

The first patch introduces a variable to handle different error codes and be able to reuse the same clean up code. The second add an omitted release by jumping to the clean code having set the returned value to the proper error code. -changes since v1 I failed to send the first version properly

Re: [PATCH] x86/paravirt: Do not trace _paravirt_ident_*() functions

I just spent half a day bisecting function tracing because I tripped over this again. I thought this was merged, but I guess it was missed again. Can someone please pull this in. And mark it for stable, it goes probably as far back as 2.6.32. Thanks! -- Steve On Wed, 25 May 2016 13:47:26

Re: [PATCH] x86/paravirt: Do not trace _paravirt_ident_*() functions

I just spent half a day bisecting function tracing because I tripped over this again. I thought this was merged, but I guess it was missed again. Can someone please pull this in. And mark it for stable, it goes probably as far back as 2.6.32. Thanks! -- Steve On Wed, 25 May 2016 13:47:26

Re: [PATCH 1/2] sdhci-of-arasan: Add device tree parameter fails-without-test-cd bit

On Mon, Aug 29, 2016 at 06:20:56PM -0500, Zach Brown wrote: > The sdhci controller on xilinx zynq devices will not function unless > the CD bit is provided. http://www.xilinx.com/support/answers/61064.html > In cases where it is impossible to provide the CD bit in hardware, > setting the

Re: [PATCH 1/2] sdhci-of-arasan: Add device tree parameter fails-without-test-cd bit

On Mon, Aug 29, 2016 at 06:20:56PM -0500, Zach Brown wrote: > The sdhci controller on xilinx zynq devices will not function unless > the CD bit is provided. http://www.xilinx.com/support/answers/61064.html > In cases where it is impossible to provide the CD bit in hardware, > setting the

[PATCH 1/2] crypto: qat - introduces a variable to handle error codes

Most error code used to jump to a label that lead to a "return -EFAULT" statement. This patch introduces a variable that stores the error code so that other error branches can use the same label to exit. Signed-off-by: Quentin Lambert ---

[PATCH 1/2] crypto: qat - introduces a variable to handle error codes

Most error code used to jump to a label that lead to a "return -EFAULT" statement. This patch introduces a variable that stores the error code so that other error branches can use the same label to exit. Signed-off-by: Quentin Lambert --- drivers/crypto/qat/qat_common/qat_uclo.c | 13

[PATCH 2/2] crypto: qat - fix resource release omissions

This issue was found with Hector. Signed-off-by: Quentin Lambert --- drivers/crypto/qat/qat_common/qat_uclo.c |3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) --- a/drivers/crypto/qat/qat_common/qat_uclo.c +++ b/drivers/crypto/qat/qat_common/qat_uclo.c @@

[PATCH 2/2] crypto: qat - fix resource release omissions

This issue was found with Hector. Signed-off-by: Quentin Lambert --- drivers/crypto/qat/qat_common/qat_uclo.c |3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) --- a/drivers/crypto/qat/qat_common/qat_uclo.c +++ b/drivers/crypto/qat/qat_common/qat_uclo.c @@ -981,7 +981,8 @@ static int

[PATCH 1/2][RESEND] crypto: qat - introduces a variable to handle error codes

Most error code used to jump to a label that lead to a "return -EFAULT" statement. This patch introduces a variable that stores the error code so that other error branches can use the same label to exit. Signed-off-by: Quentin Lambert ---

[PATCH 0/2][RESEND] add omitted release in qat_common

The first patch introduces a variable to handle different error codes and be able to reuse the same clean up code. The second add an omitted release by jumping to the clean code having set the returned value to the proper error code. --- drivers/crypto/qat/qat_common/qat_uclo.c | 16

[PATCH 2/2] crypto: qat - fix resource release omissions

In certain cases qat_uclo_parse_uof_obj used to return with an error code before releasing all resources. This patch add a jump to the appropriate label ensuring that the resources are properly released before returning. This issue was found with Hector. Signed-off-by: Quentin Lambert

[PATCH 1/2][RESEND] crypto: qat - introduces a variable to handle error codes

Most error code used to jump to a label that lead to a "return -EFAULT" statement. This patch introduces a variable that stores the error code so that other error branches can use the same label to exit. Signed-off-by: Quentin Lambert --- drivers/crypto/qat/qat_common/qat_uclo.c | 13

[PATCH 0/2][RESEND] add omitted release in qat_common

The first patch introduces a variable to handle different error codes and be able to reuse the same clean up code. The second add an omitted release by jumping to the clean code having set the returned value to the proper error code. --- drivers/crypto/qat/qat_common/qat_uclo.c | 16

[PATCH 2/2] crypto: qat - fix resource release omissions

In certain cases qat_uclo_parse_uof_obj used to return with an error code before releasing all resources. This patch add a jump to the appropriate label ensuring that the resources are properly released before returning. This issue was found with Hector. Signed-off-by: Quentin Lambert ---

Re: [PATCH 6/6] Documentation: devicetree: dwc2: Deprecate g-tx-fifo-size

On Mon, Aug 29, 2016 at 01:39:03PM -0700, John Youn wrote: > This property is not needed because the periodic fifos are not > configurable. So it was incorrect to add this property in the first > place. > > Signed-off-by: John Youn > --- >

Re: [PATCH 6/6] Documentation: devicetree: dwc2: Deprecate g-tx-fifo-size

On Mon, Aug 29, 2016 at 01:39:03PM -0700, John Youn wrote: > This property is not needed because the periodic fifos are not > configurable. So it was incorrect to add this property in the first > place. > > Signed-off-by: John Youn > --- > Documentation/devicetree/bindings/usb/dwc2.txt | 5

Re: [PATCH V4] leds: trigger: Introduce an USB port trigger

On Fri, 2 Sep 2016, Jacek Anaszewski wrote: > >>> I'm pretty sure noone ever planned to have more than 1 trigger > >>> assigned to a single LED. I just realized there will be a problem with > >>> proposed solution: sysfs files conflict. ... > >> Currently we support only triggers dedicated to

Re: [PATCH V4] leds: trigger: Introduce an USB port trigger

On Fri, 2 Sep 2016, Jacek Anaszewski wrote: > >>> I'm pretty sure noone ever planned to have more than 1 trigger > >>> assigned to a single LED. I just realized there will be a problem with > >>> proposed solution: sysfs files conflict. ... > >> Currently we support only triggers dedicated to

Re: [PATCH 3/5] u64_stats: Introduce IRQs disabled helpers

On 02/09/2016 16:03, Frederic Weisbecker wrote: > static inline unsigned int u64_stats_fetch_begin(const struct u64_stats_sync > *syncp) > { > -#if BITS_PER_LONG==32 && defined(CONFIG_SMP) > - return read_seqcount_begin(>seq); > -#else > -#if BITS_PER_LONG==32 > +#if BITS_PER_LONG==32 &&

Re: [PATCH 3/5] u64_stats: Introduce IRQs disabled helpers

On 02/09/2016 16:03, Frederic Weisbecker wrote: > static inline unsigned int u64_stats_fetch_begin(const struct u64_stats_sync > *syncp) > { > -#if BITS_PER_LONG==32 && defined(CONFIG_SMP) > - return read_seqcount_begin(>seq); > -#else > -#if BITS_PER_LONG==32 > +#if BITS_PER_LONG==32 &&

Re: [PATCH 1/2] IB/hfi1: Fix a parameter of find_first_bit.

On 8/28/2016 2:06 AM, Leon Romanovsky wrote: > On Fri, Aug 26, 2016 at 03:34:48PM -0400, Doug Ledford wrote: >> On 8/26/2016 3:29 PM, Leon Romanovsky wrote: >>> On Fri, Aug 26, 2016 at 02:01:55PM -0400, Doug Ledford wrote: On 8/26/2016 9:35 AM, Doug Ledford wrote: > On 8/26/2016 12:49 AM,

Re: [PATCH 1/2] IB/hfi1: Fix a parameter of find_first_bit.

On 8/28/2016 2:06 AM, Leon Romanovsky wrote: > On Fri, Aug 26, 2016 at 03:34:48PM -0400, Doug Ledford wrote: >> On 8/26/2016 3:29 PM, Leon Romanovsky wrote: >>> On Fri, Aug 26, 2016 at 02:01:55PM -0400, Doug Ledford wrote: On 8/26/2016 9:35 AM, Doug Ledford wrote: > On 8/26/2016 12:49 AM,

[PATCH 0/2] add omitted release in qat_common

The first patch introduces a variable to handle different error codes and be able to reuse the same clean up code. The second add an omitted release by jumping to the clean code having set the returned value to the proper error code. --- drivers/crypto/qat/qat_common/qat_uclo.c | 16

[PATCH 0/2] add omitted release in qat_common

The first patch introduces a variable to handle different error codes and be able to reuse the same clean up code. The second add an omitted release by jumping to the clean code having set the returned value to the proper error code. --- drivers/crypto/qat/qat_common/qat_uclo.c | 16

Re: [PATCH 1/3] Documentation: dt: Add TI-SCI PM Domains

On Fri, Aug 19, 2016 at 06:56:51PM -0500, Nishanth Menon wrote: > From: Dave Gerlach > > Add a generic power domain implementation, TI SCI PM Domains, that > will hook into the genpd framework and allow each PD, which will be > created one per device, to be managed over the

[PATCH] iscsi-target: fix spelling mistake "Unsolicitied" -> "Unsolicited"

From: Colin Ian King Trivial fix to spelling mistakes in pr_debug message and comments Signed-off-by: Colin Ian King --- drivers/target/iscsi/iscsi_target.c | 2 +- drivers/target/iscsi/iscsi_target_login.c | 4 ++-- 2 files changed, 3

Re: [PATCH 1/3] Documentation: dt: Add TI-SCI PM Domains

On Fri, Aug 19, 2016 at 06:56:51PM -0500, Nishanth Menon wrote: > From: Dave Gerlach > > Add a generic power domain implementation, TI SCI PM Domains, that > will hook into the genpd framework and allow each PD, which will be > created one per device, to be managed over the TI-SCI protocol. > >

[PATCH] iscsi-target: fix spelling mistake "Unsolicitied" -> "Unsolicited"

From: Colin Ian King Trivial fix to spelling mistakes in pr_debug message and comments Signed-off-by: Colin Ian King --- drivers/target/iscsi/iscsi_target.c | 2 +- drivers/target/iscsi/iscsi_target_login.c | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git

[PATCH] net: lantiq_etop: Remove unused 'i' variable

Commit e7f4dc3536a4 ("mdio: Move allocation of interrupts into core") removed the only use of the 'i' variable from ltq_etop_mdio_init() but left the variable declaration behind, leading to the following compiler warning: drivers/net/ethernet/lantiq_etop.c: In function 'ltq_etop_mdio_init':

[PATCH] net: lantiq_etop: Remove unused 'i' variable

Commit e7f4dc3536a4 ("mdio: Move allocation of interrupts into core") removed the only use of the 'i' variable from ltq_etop_mdio_init() but left the variable declaration behind, leading to the following compiler warning: drivers/net/ethernet/lantiq_etop.c: In function 'ltq_etop_mdio_init':

Re: [PATCH 3/4] KVM: x86: introduce get_kvmclock_ns

On Thu, Sep 01, 2016 at 05:26:14PM +0200, Paolo Bonzini wrote: > Introduce a function that reads the exact nanoseconds value that is > provided to the guest in kvmclock. This crystallizes the notion of > kvmclock as a thin veneer over a stable TSC, that the guest will > (hopefully) convert with

Re: [PATCH 3/4] KVM: x86: introduce get_kvmclock_ns

On Thu, Sep 01, 2016 at 05:26:14PM +0200, Paolo Bonzini wrote: > Introduce a function that reads the exact nanoseconds value that is > provided to the guest in kvmclock. This crystallizes the notion of > kvmclock as a thin veneer over a stable TSC, that the guest will > (hopefully) convert with

Re: Block-level access

My access is almost purely sequential and primarily writing, so read-ahead doesn't help me. What's problematic with pread/pwrite is the lack of error channel from media errors. BSG looks very interesting. I'll look further into that today. On Thu, Sep 1, 2016 at 5:16 PM, Bart Van Assche

Re: Block-level access

My access is almost purely sequential and primarily writing, so read-ahead doesn't help me. What's problematic with pread/pwrite is the lack of error channel from media errors. BSG looks very interesting. I'll look further into that today. On Thu, Sep 1, 2016 at 5:16 PM, Bart Van Assche wrote:

[PATCH] net: ti: cpmac: Fix compiler warning due to type confusion

cpmac_start_xmit() used the max() macro on skb->len (an unsigned int) and ETH_ZLEN (a signed int literal). This led to the following compiler warning: In file included from include/linux/list.h:8:0, from include/linux/module.h:9, from

Re: [PATCH 2/2] arm64: dts: rockchip: add eMMC's power domain support for rk3399

Hi Ulf, On 2016年09月02日 18:24, Ulf Hansson wrote: On 1 September 2016 at 23:50, Doug Anderson wrote: >Hi, > >On Thu, Sep 1, 2016 at 6:45 AM, Ulf Hansson wrote: >>I was reading the discussion regarding this change and browsing the DT

[PATCH] net: ti: cpmac: Fix compiler warning due to type confusion

cpmac_start_xmit() used the max() macro on skb->len (an unsigned int) and ETH_ZLEN (a signed int literal). This led to the following compiler warning: In file included from include/linux/list.h:8:0, from include/linux/module.h:9, from

Re: [PATCH 2/2] arm64: dts: rockchip: add eMMC's power domain support for rk3399

Hi Ulf, On 2016年09月02日 18:24, Ulf Hansson wrote: On 1 September 2016 at 23:50, Doug Anderson wrote: >Hi, > >On Thu, Sep 1, 2016 at 6:45 AM, Ulf Hansson wrote: >>I was reading the discussion regarding this change and browsing the DT >>documentation around this... Can you guys explain what

Re: [PATCH] usb: dwc3: host: inherit dma configuration from parent dev

On Fri, 2 Sep 2016, Felipe Balbi wrote: > Hi, > > Russell King - ARM Linux writes: > > On Fri, Sep 02, 2016 at 12:43:39PM +0200, Arnd Bergmann wrote: > >> On Thursday, September 1, 2016 5:14:28 PM CEST Leo Li wrote: > >> > > >> > Hi Felipe and Arnd, > >> > > >> > It has

Re: [PATCH] usb: dwc3: host: inherit dma configuration from parent dev

On Fri, 2 Sep 2016, Felipe Balbi wrote: > Hi, > > Russell King - ARM Linux writes: > > On Fri, Sep 02, 2016 at 12:43:39PM +0200, Arnd Bergmann wrote: > >> On Thursday, September 1, 2016 5:14:28 PM CEST Leo Li wrote: > >> > > >> > Hi Felipe and Arnd, > >> > > >> > It has been a while since the

Re: [Question] about patch: don't use [delayed_]work_pending()

On Fri, Sep 02, 2016 at 09:50:07AM -0400, Tejun Heo wrote: > Hello, > > On Fri, Sep 02, 2016 at 09:17:04AM +0800, qiaozhou wrote: > > > > I don't know whether it's meaningful to still check pending work here, > > > > or > > > > it's not suggested to use pm_qos_update_request in this early boot

Re: [Question] about patch: don't use [delayed_]work_pending()

On Fri, Sep 02, 2016 at 09:50:07AM -0400, Tejun Heo wrote: > Hello, > > On Fri, Sep 02, 2016 at 09:17:04AM +0800, qiaozhou wrote: > > > > I don't know whether it's meaningful to still check pending work here, > > > > or > > > > it's not suggested to use pm_qos_update_request in this early boot

[PATCH] MIPS: dec: Avoid la pseudo-instruction in delay slots

When expanding the la or dla pseudo-instruction in a delay slot the GNU assembler will complain should the pseudo-instruction expand to multiple actual instructions, since only the first of them will be in the delay slot leading to the pseudo-instruction being only partially executed if the branch

Re: [PATCH v15 04/13] task_isolation: add initial support

On 9/1/2016 6:06 AM, Peter Zijlstra wrote: On Tue, Aug 30, 2016 at 11:32:16AM -0400, Chris Metcalf wrote: On 8/30/2016 3:58 AM, Peter Zijlstra wrote: What !? I really don't get this, what are you waiting for? Why is rescheduling making things better. We need to wait for the last dyntick to

[PATCH] MIPS: dec: Avoid la pseudo-instruction in delay slots

When expanding the la or dla pseudo-instruction in a delay slot the GNU assembler will complain should the pseudo-instruction expand to multiple actual instructions, since only the first of them will be in the delay slot leading to the pseudo-instruction being only partially executed if the branch

Re: [PATCH v15 04/13] task_isolation: add initial support

On 9/1/2016 6:06 AM, Peter Zijlstra wrote: On Tue, Aug 30, 2016 at 11:32:16AM -0400, Chris Metcalf wrote: On 8/30/2016 3:58 AM, Peter Zijlstra wrote: What !? I really don't get this, what are you waiting for? Why is rescheduling making things better. We need to wait for the last dyntick to

[PATCH] MIPS: netlogic: Fix assembler warning from smpboot.S

The netlogic platform can be built for either MIPS32 or MIPS64, and when built for MIPS32 (as by nlm_xlr_defconfig) the use of the dla pseudo-instruction leads to warnings such as the following from recent versions of the GNU assembler: arch/mips/netlogic/common/smpboot.S: Assembler messages:

[PATCH] MIPS: netlogic: Fix assembler warning from smpboot.S

The netlogic platform can be built for either MIPS32 or MIPS64, and when built for MIPS32 (as by nlm_xlr_defconfig) the use of the dla pseudo-instruction leads to warnings such as the following from recent versions of the GNU assembler: arch/mips/netlogic/common/smpboot.S: Assembler messages:

Re: [PATCH 1/6] irqchip: mips-gic: Add context saving for MIPS_REMOTEPROC

Hi Marc, Thanks for the review! On 02/09/16 11:54, Marc Zyngier wrote: Hi Matt, On 02/09/16 10:59, Matt Redfearn wrote: The MIPS remote processor driver allows non-Linux firmware to take control of and execute on one of the systems VPEs. If that VPE is brought back under Linux, it is

Re: [PATCH 1/6] irqchip: mips-gic: Add context saving for MIPS_REMOTEPROC

Hi Marc, Thanks for the review! On 02/09/16 11:54, Marc Zyngier wrote: Hi Matt, On 02/09/16 10:59, Matt Redfearn wrote: The MIPS remote processor driver allows non-Linux firmware to take control of and execute on one of the systems VPEs. If that VPE is brought back under Linux, it is

[PATCH] MIPS: Fix detection of unsupported highmem with cache aliases

The paging_init() function contains code which detects that highmem is in use but unsupported due to dcache aliasing. However this code was ineffective because it was being run before the caches are probed, meaning that cpu_has_dc_aliases would always evaluate to false (unless a platform overrides

[PATCH] MIPS: Fix detection of unsupported highmem with cache aliases

The paging_init() function contains code which detects that highmem is in use but unsupported due to dcache aliasing. However this code was ineffective because it was being run before the caches are probed, meaning that cpu_has_dc_aliases would always evaluate to false (unless a platform overrides

Re: [PATCH 4/4] kvm: x86: export TSC offset to user-space

On Fri, 2 Sep 2016 09:43:01 -0400 Stefan Hajnoczi wrote: > Can TSC offset changes occur at runtime? > > One example is vcpu hotplug where the tracing tool would need to fetch > the new vcpu's TSC offset after tracing has already started. > > Another example is if QEMU or

Re: [PATCH v4 1/3] nvmem: rockchip-efuse: update compatible strings for Rockchip efuse

On Mon, Aug 29, 2016 at 02:50:08AM -0700, Finley Xiao wrote: > Rk3399-efuse is organized as 32bits by 32 one-time programmable electrical > fuses. The efuse of earlier SoCs are organized as 32bits by 8 one-time > programmable electrical fuses with random access interface. > > Add different device

Re: [PATCH 4/4] kvm: x86: export TSC offset to user-space

On Fri, 2 Sep 2016 09:43:01 -0400 Stefan Hajnoczi wrote: > Can TSC offset changes occur at runtime? > > One example is vcpu hotplug where the tracing tool would need to fetch > the new vcpu's TSC offset after tracing has already started. > > Another example is if QEMU or the guest change the

Re: [PATCH v4 1/3] nvmem: rockchip-efuse: update compatible strings for Rockchip efuse

On Mon, Aug 29, 2016 at 02:50:08AM -0700, Finley Xiao wrote: > Rk3399-efuse is organized as 32bits by 32 one-time programmable electrical > fuses. The efuse of earlier SoCs are organized as 32bits by 8 one-time > programmable electrical fuses with random access interface. > > Add different device

Re: [PART2 PATCH v7 00/12] iommu/AMD: Introduce IOMMU AVIC support

Thanks All. Please let me know if you need anything else from my side. Suravee On 9/2/16 21:05, Joerg Roedel wrote: Hi Paolo, On Fri, Sep 02, 2016 at 12:46:28PM +0200, Paolo Bonzini wrote: Joerg, if there's no other issues, could you apply the first 9 patches to a branch based on 4.8-rc1 or

Re: [PART2 PATCH v7 00/12] iommu/AMD: Introduce IOMMU AVIC support

Thanks All. Please let me know if you need anything else from my side. Suravee On 9/2/16 21:05, Joerg Roedel wrote: Hi Paolo, On Fri, Sep 02, 2016 at 12:46:28PM +0200, Paolo Bonzini wrote: Joerg, if there's no other issues, could you apply the first 9 patches to a branch based on 4.8-rc1 or

Re: [PATCH 1/4] Documentation: mmc: sdhci-of-arasan: Add clk_syscon as an optional one

On Mon, Aug 29, 2016 at 04:02:56PM +0800, Shawn Lin wrote: > We introduced soc-ctl-syscon to do several things, for instance, update > baseclk or update clkmul, etc. In odrder to access this physical block, > we need to explicitly enable its clock. Currently we don't control this > clock as we

Re: [PATCH 1/4] Documentation: mmc: sdhci-of-arasan: Add clk_syscon as an optional one

On Mon, Aug 29, 2016 at 04:02:56PM +0800, Shawn Lin wrote: > We introduced soc-ctl-syscon to do several things, for instance, update > baseclk or update clkmul, etc. In odrder to access this physical block, > we need to explicitly enable its clock. Currently we don't control this > clock as we

Re: [PATCH v3 03/22] usb: ulpi: Support device discovery via device properties

Hi, On Wed, Aug 31, 2016 at 05:40:17PM -0700, Stephen Boyd wrote: > @@ -174,14 +219,37 @@ static int ulpi_register(struct device *dev, struct > ulpi *ulpi) > ulpi->id.product = ulpi_read(ulpi, ULPI_PRODUCT_ID_LOW); > ulpi->id.product |= ulpi_read(ulpi, ULPI_PRODUCT_ID_HIGH) << 8; >

Re: [PATCH] usb: dwc3: host: inherit dma configuration from parent dev

Hi, Felipe Balbi writes: > Hi, > > Russell King - ARM Linux writes: >> On Fri, Sep 02, 2016 at 12:43:39PM +0200, Arnd Bergmann wrote: >>> On Thursday, September 1, 2016 5:14:28 PM CEST Leo Li wrote: >>> > >>> > Hi Felipe and Arnd, >>> > >>> > It has

Re: [PATCH v3 03/22] usb: ulpi: Support device discovery via device properties

Hi, On Wed, Aug 31, 2016 at 05:40:17PM -0700, Stephen Boyd wrote: > @@ -174,14 +219,37 @@ static int ulpi_register(struct device *dev, struct > ulpi *ulpi) > ulpi->id.product = ulpi_read(ulpi, ULPI_PRODUCT_ID_LOW); > ulpi->id.product |= ulpi_read(ulpi, ULPI_PRODUCT_ID_HIGH) << 8; >

Re: [PATCH] usb: dwc3: host: inherit dma configuration from parent dev

Hi, Felipe Balbi writes: > Hi, > > Russell King - ARM Linux writes: >> On Fri, Sep 02, 2016 at 12:43:39PM +0200, Arnd Bergmann wrote: >>> On Thursday, September 1, 2016 5:14:28 PM CEST Leo Li wrote: >>> > >>> > Hi Felipe and Arnd, >>> > >>> > It has been a while since the last response to

Re: [PATCH 3/4] KVM: x86: introduce get_kvmclock_ns

On 02/09/2016 15:52, Roman Kagan wrote: > On Thu, Sep 01, 2016 at 05:26:14PM +0200, Paolo Bonzini wrote: >> Introduce a function that reads the exact nanoseconds value that is >> provided to the guest in kvmclock. This crystallizes the notion of >> kvmclock as a thin veneer over a stable TSC,

Re: [PATCH 3/4] KVM: x86: introduce get_kvmclock_ns

On 02/09/2016 15:52, Roman Kagan wrote: > On Thu, Sep 01, 2016 at 05:26:14PM +0200, Paolo Bonzini wrote: >> Introduce a function that reads the exact nanoseconds value that is >> provided to the guest in kvmclock. This crystallizes the notion of >> kvmclock as a thin veneer over a stable TSC,

[PATCH] ASoC: fsl_esai: fix spelling mistake "Transmition" -> "Transmission"

From: Colin Ian King Trivial fix to spelling mistakes in dev_dbg messages Signed-off-by: Colin Ian King --- sound/soc/fsl/fsl_esai.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/sound/soc/fsl/fsl_esai.c

[PATCH] ASoC: fsl_esai: fix spelling mistake "Transmition" -> "Transmission"

From: Colin Ian King Trivial fix to spelling mistakes in dev_dbg messages Signed-off-by: Colin Ian King --- sound/soc/fsl/fsl_esai.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/sound/soc/fsl/fsl_esai.c b/sound/soc/fsl/fsl_esai.c index 26a90e1..e927955 100644 ---

Re: [RFC PATCH v2 05/20] x86: Add the Secure Memory Encryption cpu feature

On Mon, Aug 22, 2016 at 05:36:22PM -0500, Tom Lendacky wrote: > Update the cpu features to include identifying and reporting on the > Secure Memory Encryption feature. > > Signed-off-by: Tom Lendacky > --- > arch/x86/include/asm/cpufeature.h|7 +-- >

Re: [RFC PATCH v2 05/20] x86: Add the Secure Memory Encryption cpu feature

On Mon, Aug 22, 2016 at 05:36:22PM -0500, Tom Lendacky wrote: > Update the cpu features to include identifying and reporting on the > Secure Memory Encryption feature. > > Signed-off-by: Tom Lendacky > --- > arch/x86/include/asm/cpufeature.h|7 +-- >

Re: [Patch v9] driver/clk/clk-si5338: Add common clock framework driver for si5338

On Fri, Aug 26, 2016 at 02:45:49PM -0700, York Sun wrote: > From: York Sun > > SI5338 is a programmable clock generator. It has 4 sets of inputs, > PLL, multisynth and dividers to make 4 outputs. This driver splits > them into multiple clocks to comply with common clock

Re: [Patch v9] driver/clk/clk-si5338: Add common clock framework driver for si5338

On Fri, Aug 26, 2016 at 02:45:49PM -0700, York Sun wrote: > From: York Sun > > SI5338 is a programmable clock generator. It has 4 sets of inputs, > PLL, multisynth and dividers to make 4 outputs. This driver splits > them into multiple clocks to comply with common clock framework. > > See

Re: [PART2 PATCH v7 00/12] iommu/AMD: Introduce IOMMU AVIC support

Hi Paolo, On Fri, Sep 02, 2016 at 12:46:28PM +0200, Paolo Bonzini wrote: > Joerg, if there's no other issues, could you apply the first 9 patches > to a branch based on 4.8-rc1 or similar, so that I can pull it into the > KVM tree? Sure, I was actually waiting for your Acked-By to put all the

Re: [PART2 PATCH v7 00/12] iommu/AMD: Introduce IOMMU AVIC support

Hi Paolo, On Fri, Sep 02, 2016 at 12:46:28PM +0200, Paolo Bonzini wrote: > Joerg, if there's no other issues, could you apply the first 9 patches > to a branch based on 4.8-rc1 or similar, so that I can pull it into the > KVM tree? Sure, I was actually waiting for your Acked-By to put all the

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