From: Kevin Hilman <khilman@kernel.org>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
<arm@kernel.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Boris BREZILLON <boris.brezillon@free-electrons.com>,
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
Linus Walleij <linus.walleij@linaro.org>,
Ludovic Desroches <ludovic.desroches@atmel.com>
Subject: Re: [GIT PULL] at91: fixes for 3.19 #1
Date: Mon, 15 Dec 2014 14:20:10 -0800 [thread overview]
Message-ID: <7hmw6oh7xh.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1418377615-15122-1-git-send-email-nicolas.ferre@atmel.com> (Nicolas Ferre's message of "Fri, 12 Dec 2014 10:46:55 +0100")
Nicolas Ferre <nicolas.ferre@atmel.com> writes:
> Arnd, Olof, Kevin,
>
> I'm sending today a "fixes" branch which somehow continues the cleanup with
> only code removal. I was waiting for the arm-soc *and* pinctrl material to
> reach Linus T.'s tree before sending this pull-request. In fact this sequence
> was needed for the gpio header removal. The little patch about #include
> deletion just follows an earlier merge conflict in arm-soc tree: I was also
> waiting for this moment before sending the definitive fix, just to be sure.
>
> Otherwise, all is pretty straightforward.
>
> Oh, one more thing: it is based on the current Linus' git tree, I can obviously
> rebase everything on top of 3.19-rc1 once it is released if you prefer.
Yes, waiting a bit and basing on v3.19-rc1 is preferred since none of
this seems like urgent fixes needed for stuff introduced during the
merge window.
Thanks,
Kevin
next prev parent reply other threads:[~2014-12-15 22:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 9:46 [GIT PULL] at91: fixes for 3.19 #1 Nicolas Ferre
2014-12-15 22:20 ` Kevin Hilman [this message]
2014-12-16 10:16 ` Nicolas Ferre
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=7hmw6oh7xh.fsf@deeprootsystems.com \
--to=khilman@kernel.org \
--cc=alexandre.belloni@free-electrons.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=boris.brezillon@free-electrons.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@atmel.com \
--cc=nicolas.ferre@atmel.com \
--cc=olof@lixom.net \
--cc=plagnioj@jcrosoft.com \
/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