linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: geert@linux-m68k.org (Geert Uytterhoeven)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/3] arm64: dts: renesas: r8a7795: move scif node into alphabetical order
Date: Wed, 3 Jan 2018 15:02:56 +0100	[thread overview]
Message-ID: <CAMuHMdWUdF5OOjkCOzWO38Ems9NLXmmcpf-txhNF3ZU47itCfQ@mail.gmail.com> (raw)
In-Reply-To: <20180103124105.1999-2-horms+renesas@verge.net.au>

On Wed, Jan 3, 2018 at 1:41 PM, Simon Horman <horms+renesas@verge.net.au> wrote:
> Move scif node so that sub-nodes of the root node are in
> alphabetical order.
>
> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>

Reviewed-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

  reply	other threads:[~2018-01-03 14:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-03 12:41 [PATCH v3 0/3] arm64: dts: r8a779[56]: Add OPPs table for cpu devices Simon Horman
2018-01-03 12:41 ` [PATCH v3 1/3] arm64: dts: renesas: r8a7795: move scif node into alphabetical order Simon Horman
2018-01-03 14:02   ` Geert Uytterhoeven [this message]
2018-01-03 12:41 ` [PATCH v3 2/3] arm64: dts: renesas: r8a7795: Add OPPs table for cpu devices Simon Horman
2018-01-03 14:06   ` Geert Uytterhoeven
2018-01-03 12:41 ` [PATCH v3 3/3] arm64: dts: renesas: r8a7796: " Simon Horman
2018-01-03 14:07   ` Geert Uytterhoeven
2018-01-03 17:38 ` [PATCH v3 0/3] arm64: dts: r8a779[56]: " Niklas Söderlund
2018-01-04 16:49   ` 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=CAMuHMdWUdF5OOjkCOzWO38Ems9NLXmmcpf-txhNF3ZU47itCfQ@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 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).