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/3] ARM: shmobile: SCU cleanup and consolidation
Date: Mon, 8 Feb 2016 16:04:34 +0100	[thread overview]
Message-ID: <CAMuHMdUn7=AAehQqG5ezc4wkKjytOoVz7U9HT_HvPLVj+Na7Vg@mail.gmail.com> (raw)
In-Reply-To: <20160202140550.GB4304@verge.net.au>

Hi Simon,

On Tue, Feb 2, 2016 at 3:05 PM, Simon Horman <horms@verge.net.au> wrote:
> On Thu, Jan 28, 2016 at 04:13:29PM +0100, Geert Uytterhoeven wrote:
>> This patch series contains cleanups and consolidations of the SCU code
>> for shmobile SoCs with Cortex-A9 CPU cores.
>>
>> This has been tested on emev2/kzm9d, r8a7779/marzen, and sh73a0/kzm9g.
>>
>> Thanks!
>
> Thanks, I have queued these up.

Except for the third patch?

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

  reply	other threads:[~2016-02-08 15:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-28 15:13 [PATCH 0/3] ARM: shmobile: SCU cleanup and consolidation Geert Uytterhoeven
2016-01-28 15:13 ` [PATCH 1/3] ARM: shmobile: Typo s/MIPDR/MPIDR/ Geert Uytterhoeven
2016-01-28 15:13 ` [PATCH 2/3] ARM: shmobile: r8a7779: Remove remainings of removed SCU boot setup code Geert Uytterhoeven
2016-01-28 15:13 ` [PATCH 3/3] ARM: shmobile: Consolidate SCU mapping code Geert Uytterhoeven
2016-02-02 14:05 ` [PATCH 0/3] ARM: shmobile: SCU cleanup and consolidation Simon Horman
2016-02-08 15:04   ` Geert Uytterhoeven [this message]
2016-02-09 19:07     ` 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='CAMuHMdUn7=AAehQqG5ezc4wkKjytOoVz7U9HT_HvPLVj+Na7Vg@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.