From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Ivan Mikhaylov <ivan@de.ibm.com>,
Alistair Popple <alistair@popple.id.au>,
Matt Porter <mporter@kernel.crashing.org>
Cc: Joel Stanley <joel@ozlabs.au.ibm.com>,
linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [2/4] arch/powerpc/44x/fsp2: add device tree for fsp2 board
Date: Tue, 30 May 2017 19:11:22 +1000 (AEST) [thread overview]
Message-ID: <3wcSXC1nxwz9s74@ozlabs.org> (raw)
In-Reply-To: <20170515130754.59363-3-ivan@de.ibm.com>
On Mon, 2017-05-15 at 13:07:52 UTC, Ivan Mikhaylov wrote:
> Add a device tree for fsp2 board (476 based).
>
> Signed-off-by: Ivan Mikhaylov <ivan@de.ibm.com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/9eec6cb142bddd35268c7c59b6c81b
cheers
prev parent reply other threads:[~2017-05-30 9:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 13:07 [PATCH 2/4] arch/powerpc/44x/fsp2: add device tree for fsp2 board Ivan Mikhaylov
2017-05-30 9:11 ` Michael Ellerman [this message]
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=3wcSXC1nxwz9s74@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=alistair@popple.id.au \
--cc=ivan@de.ibm.com \
--cc=joel@ozlabs.au.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mporter@kernel.crashing.org \
--cc=paulus@samba.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).