From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: dt64 for v4.14 (#4)
Date: Fri, 1 Sep 2017 16:45:12 -0700 [thread overview]
Message-ID: <20170901234512.GC15825@localhost> (raw)
In-Reply-To: <87k21l4c27.fsf@free-electrons.com>
On Wed, Aug 30, 2017 at 11:52:48AM +0200, Gregory CLEMENT wrote:
> Hi,
>
> Here is the forth (and ultimate) pull request for dt64 for mvebu for v4.14.
>
> I really hope it is not too late.
>
> These patches were initially part of the netdev series but were
> removed from these series to avoid conflict in the device
> tree. Unfortunately this moved was done during the holiday time so
> it didn't happen smoothly. I will do better for the next release.
>
> They really worth to be added because all the driver part were already
> there but as pointed by Thomas otherwise the driver changes are
> somewhat useless.
Yep, makes sense to pick up. Merged now, thanks.
-Olof
prev parent reply other threads:[~2017-09-01 23:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 9:52 [GIT PULL] ARM: mvebu: dt64 for v4.14 (#4) Gregory CLEMENT
2017-09-01 23:45 ` Olof Johansson [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=20170901234512.GC15825@localhost \
--to=olof@lixom.net \
--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).