public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/3] Keystone SOC driver updates for 4.4
Date: Thu, 08 Oct 2015 21:29:42 +0200	[thread overview]
Message-ID: <5000605.4VJZfFh1uH@wuerfel> (raw)
In-Reply-To: <5616C1F5.6050201@oracle.com>

On Thursday 08 October 2015 12:20:21 santosh.shilimkar at oracle.com wrote:
> On 10/8/15 11:50 AM, Arnd Bergmann wrote:
> > On Thursday 08 October 2015 09:25:14 santosh.shilimkar at oracle.com wrote:
> >> On 10/8/15 8:41 AM, Arnd Bergmann wrote:
> >>> On Tuesday 06 October 2015 10:19:18 Santosh Shilimkar wrote:
> >>>> Couple of patches for ARM Keystone SOC drivers
> >>>>           - irq affinity bug fix
> >>>>           - display the firmware name
> >>>>
> >>>> ----------------------------------------------------------------
> >>>> Murali Karicheri (2):
> >>>>         soc: ti: reset irq affinity before freeing irq
> >>>>         soc: ti: display firmware file name as part of boot log
> >>>>
> >>>>    .../bindings/soc/ti/keystone-navigator-qmss.txt      | 20 +++++++++++++++++++-
> >>>>    drivers/soc/ti/knav_qmss_acc.c                       |  4 ++++
> >>>>    drivers/soc/ti/knav_qmss_queue.c                     |  3 +++
> >>>>    3 files changed, 26 insertions(+), 1 deletion(-)
> >>>
> >>> The new text you add to the binding document doesn't really seem to
> >>> belong in there, so I'm not pulling this until we've discussed how
> >>> this should be better handled.
> >>>
> >> OK. Can you please pick the affinity fix alone?
> >
> > Sure. Actually this looks like it should go into 4.3, possibly stable.
> > Can you confirm which kernels need it?
> >
> Upcoming 4.4 is just fine.

Ok, applied to next/fixes-non-critical.

	Arnd

  reply	other threads:[~2015-10-08 19:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-06 17:19 [GIT PULL 1/3] Keystone SOC driver updates for 4.4 Santosh Shilimkar
2015-10-06 17:19 ` [GIT PULL 2/3] Keystone config " Santosh Shilimkar
2015-10-08 15:34   ` Arnd Bergmann
2015-10-06 17:19 ` [GIT PULL 3/3] Kestone DTS " Santosh Shilimkar
2015-10-08 15:31   ` Arnd Bergmann
2015-10-08 15:41 ` [GIT PULL 1/3] Keystone SOC driver " Arnd Bergmann
2015-10-08 16:25   ` santosh.shilimkar at oracle.com
2015-10-08 18:50     ` Arnd Bergmann
2015-10-08 19:20       ` santosh.shilimkar at oracle.com
2015-10-08 19:29         ` Arnd Bergmann [this message]
2015-10-08 20:35           ` santosh shilimkar
2015-10-08 16:47   ` Murali Karicheri
2015-10-08 19:16     ` Arnd Bergmann
2015-10-09 14:48       ` Karicheri, Muralidharan
2015-10-09 15:09       ` Karicheri, Muralidharan
2015-10-09 15:21         ` Arnd Bergmann
2015-10-09 15:32           ` santosh shilimkar
2015-10-09 18:54           ` Karicheri, Muralidharan
2015-10-12 15:06             ` Murali Karicheri
2015-10-12 19:56               ` Murali Karicheri

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5000605.4VJZfFh1uH@wuerfel \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox