From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 3/4] arm64: nxp: device tree changes for 4.6
Date: Mon, 7 Mar 2016 10:33:49 +0700 [thread overview]
Message-ID: <20160307033348.GC5051@x250> (raw)
In-Reply-To: <3449603.z2vlrkXDmL@wuerfel>
On Wed, Mar 02, 2016 at 11:09:59PM +0100, Arnd Bergmann wrote:
> On Tuesday 01 March 2016 23:00:02 Shawn Guo wrote:
> > This is the first time I help to collect NXP/Freescale arm64 dts
> > patches. I used to ignore such patches, because they do not belong
> > to i.MX family. But since people keep sending me patches, I decided
> > to help accelerate the process for getting these patches land on
> > mainline.
>
> Much appreciated!
>
> > I should probably start naming my branches and tags like nxp/* from the
> > next cycle.
>
> I don't care much either way, unless you also want to start picking
> up the patches for the lpc18xx and lpc32xx SoC families that currently
> have other maintainers.
Okay. I will keep the current naming schema.
> I've pulled the patches into next/dt64, thanks!
Thanks.
Shawn
next prev parent reply other threads:[~2016-03-07 3:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 15:00 [GIT PULL 1/4] ARM: imx: soc updates for 4.6 Shawn Guo
2016-03-01 15:00 ` [GIT PULL 2/4] ARM: imx: device tree changes " Shawn Guo
2016-03-02 20:26 ` Arnd Bergmann
2016-03-07 3:32 ` Shawn Guo
2016-03-01 15:00 ` [GIT PULL 3/4] arm64: nxp: " Shawn Guo
2016-03-02 22:09 ` Arnd Bergmann
2016-03-07 3:33 ` Shawn Guo [this message]
2016-03-01 15:00 ` [GIT PULL 4/4] ARM: imx: defconfig updates " Shawn Guo
2016-03-02 22:18 ` Arnd Bergmann
2016-03-02 22:32 ` [GIT PULL 1/4] ARM: imx: soc " Arnd Bergmann
2016-03-07 3:29 ` Shawn Guo
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=20160307033348.GC5051@x250 \
--to=shawnguo@kernel.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).