All of lore.kernel.org
 help / color / mirror / Atom feed
From: geert@linux-m68k.org (Geert Uytterhoeven)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: shmobile: r8a779[34]: use GIC_* defines
Date: Mon, 18 Jan 2016 13:01:18 +0100	[thread overview]
Message-ID: <CAMuHMdUQtdkUwzy+++zohL3Nj=eivGGM+3OMdLmyBNTrcinQ3Q@mail.gmail.com> (raw)
In-Reply-To: <1453094324-22404-1-git-send-email-horms+renesas@verge.net.au>

On Mon, Jan 18, 2016 at 6:18 AM, Simon Horman
<horms+renesas@verge.net.au> wrote:
> this short series uses GIC_* defines in the r8a779[34] device trees as
> appropriate.
>
> This is a follow-up for similar work for the rua779[01] SoCs.
> I plan to post follow up patches to update the device trees for
> other Renesas SoCs depending on the success of this series.

Acked-by: Geert Uytterhoeven <geert+renesas@glider.be>

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  parent reply	other threads:[~2016-01-18 12:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-18  5:18 [PATCH 0/2] ARM: shmobile: r8a779[34]: use GIC_* defines Simon Horman
2016-01-18  5:18 ` [PATCH 1/2] ARM: dts: r8a7793: use GIC_*defines Simon Horman
2016-01-18  5:18 ` [PATCH 2/2] ARM: dts: r8a7794: " Simon Horman
2016-01-18  5:18   ` Simon Horman
2016-01-28  8:21   ` Geert Uytterhoeven
2016-01-29  0:34     ` Simon Horman
2016-01-29  8:34       ` Geert Uytterhoeven
2016-02-02 10:22         ` Simon Horman
2016-01-18 12:01 ` Geert Uytterhoeven [this message]
2016-01-21  2:55   ` [PATCH 0/2] ARM: shmobile: r8a779[34]: use GIC_* defines 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='CAMuHMdUQtdkUwzy+++zohL3Nj=eivGGM+3OMdLmyBNTrcinQ3Q@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.