From: Shawn Guo <shawnguo@kernel.org>
To: Olof Johansson <olof@lixom.net>
Cc: Stephen Boyd <sboyd@kernel.org>,
arm@kernel.org, linux-imx@nxp.com, kernel@pengutronix.de,
Fabio Estevam <fabio.estevam@nxp.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] i.MX8MQ device tree support for 4.21
Date: Wed, 2 Jan 2019 08:39:52 +0800 [thread overview]
Message-ID: <20190102003951.GA12098@dragon> (raw)
In-Reply-To: <20181231210841.sg3vqzs6dujvnaz3@localhost>
On Mon, Dec 31, 2018 at 01:08:41PM -0800, Olof Johansson wrote:
> On Mon, Dec 17, 2018 at 09:30:37PM +0800, Shawn Guo wrote:
> > Hi,
> >
> > It's the initial device tree support for the first ARM64 i.MX processor,
> > which has been floating around for a couple of release cycles. Due to
> > the last minute discussion on fine-grind SoC specific option, it comes
> > late. But we appreciate that you consider to pull it for 4.21, as we
> > have more development lined up based on this initial support. Thanks.
> >
> > Note: the pull request is based on tag imx-dt64-4.21 (already pulled)
> > with one stable commit from clk tree merged in to resolve dependency on
> > i.MX8MQ clock ID.
>
> I've queued this up as a next/late branch, and will try to send it in before
> end of the merge window. It's been a quiet merge window so far, but there are
> no hard guarantees that we'll get it merged.
Noted. Thanks, Olof.
Shawn
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-01-02 0:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 13:30 [GIT PULL] i.MX8MQ device tree support for 4.21 Shawn Guo
2018-12-31 21:08 ` Olof Johansson
2019-01-02 0:39 ` Shawn Guo [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=20190102003951.GA12098@dragon \
--to=shawnguo@kernel.org \
--cc=arm@kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=olof@lixom.net \
--cc=sboyd@kernel.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).