devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	Magnus Damm <magnus.damm@gmail.com>,
	linux-sh@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 6/6] staging: board: armadillo800eva: Use "arm,pl390"
Date: Mon, 14 Dec 2015 15:29:14 +0900	[thread overview]
Message-ID: <20151214062914.GI18143@verge.net.au> (raw)
In-Reply-To: <20151214051647.GA3140@kroah.com>

On Sun, Dec 13, 2015 at 09:16:47PM -0800, Greg Kroah-Hartman wrote:
> On Mon, Dec 14, 2015 at 02:05:26PM +0900, Simon Horman wrote:
> > On Fri, Dec 11, 2015 at 11:28:30AM -0500, Greg Kroah-Hartman wrote:
> > > On Fri, Nov 20, 2015 at 01:36:57PM +0100, Geert Uytterhoeven wrote:
> > > > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> > > > ---
> > > > Must be applied together with "ARM: shmobile: r8a7740 dtsi: Use
> > > > "arm,pl390" for GIC"!
> > > > 
> > > > Greg: Can you please provide your ack? Thanks!
> > > 
> > > Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > 
> > Thanks Greg,
> > 
> > I have taken the liberty of assuming that ack also applies to
> > patch 5/6 of this series, the other staging/board patch in
> > this series.
> 
> Oops, yes, good call, thanks for doing this.

No problem.

For the record I have queued up these patches for v4.6 as I
believe that the ARM SoC maintainers prefer not to have
driver changes depending on DT changes and the first four patches
of this series are DT changes.

  reply	other threads:[~2015-12-14  6:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-20 12:36 [PATCH 0/6] ARM: shmobile: Use "arm,pl390" for GIC where appropriate Geert Uytterhoeven
2015-11-20 12:36 ` [PATCH 1/6] ARM: shmobile: r7s72100 dtsi: Use "arm,pl390" for GIC Geert Uytterhoeven
2015-11-20 12:36 ` [PATCH 3/6] ARM: shmobile: emev2 " Geert Uytterhoeven
2015-11-20 12:36 ` [PATCH 4/6] ARM: shmobile: r8a7778 " Geert Uytterhoeven
     [not found] ` <1448023017-21816-1-git-send-email-geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>
2015-11-20 12:36   ` [PATCH 2/6] ARM: shmobile: r8a7740 " Geert Uytterhoeven
2015-11-20 12:36   ` [PATCH 5/6] staging: board: kzm9d: Use "arm,pl390" Geert Uytterhoeven
2015-11-20 12:36 ` [PATCH 6/6] staging: board: armadillo800eva: " Geert Uytterhoeven
     [not found]   ` <1448023017-21816-7-git-send-email-geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>
2015-12-11 16:28     ` Greg Kroah-Hartman
2015-12-14  5:05       ` Simon Horman
2015-12-14  5:16         ` Greg Kroah-Hartman
2015-12-14  6:29           ` Simon Horman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-12-14  7:51 Geert Uytterhoeven
2015-12-14  8:15 ` Simon Horman

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=20151214062914.GI18143@verge.net.au \
    --to=horms@verge.net.au \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).