From: Olof Johansson <olof@lixom.net>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
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>,
Ludovic Desroches <ludovic.desroches@atmel.com>
Subject: Re: [GIT PULL] at91: cleanup/soc for 3.20 #4 (bis)
Date: Fri, 6 Feb 2015 00:00:05 -0800 [thread overview]
Message-ID: <20150206080005.GA23582@quad.lixom.net> (raw)
In-Reply-To: <1422905274-9303-1-git-send-email-nicolas.ferre@atmel.com>
On Mon, Feb 02, 2015 at 08:27:54PM +0100, Nicolas Ferre wrote:
> Arnd, Olof, Kevin,
>
> As advised by Olof, here is a second attempt with this pull-request but this
> time with the at91-3.19-fixes branch as a base. Here is how I did it:
> - took v3.19-rc4
> - merged my at91-3.19-fixes branch that is now in Linus' tree
> - merged my at91-cleanup3 tag that you already have in your "soc" branch. These
> patches obviously depend on this tag.
> - stacked the contend of this cleanup/soc pull-request.
Yep -- only tweak is that next time you could either start with your cleanup3
tag and just merge fixes, or start with fixes and merge cleanup3 -- no need to
do an explicit merge of fixes on top of mainline.
Anyway, that's just a very minor detail. I've merged this now, thanks for
respinning!
-Olof
prev parent reply other threads:[~2015-02-06 8:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 11:51 [GIT PULL] at91: cleanup/soc for 3.20 #4 Nicolas Ferre
2015-01-29 22:02 ` Olof Johansson
2015-01-29 22:08 ` Olof Johansson
2015-01-29 23:01 ` Alexandre Belloni
2015-01-29 23:06 ` Olof Johansson
2015-02-02 19:27 ` [GIT PULL] at91: cleanup/soc for 3.20 #4 (bis) Nicolas Ferre
2015-02-06 8:00 ` 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=20150206080005.GA23582@quad.lixom.net \
--to=olof@lixom.net \
--cc=alexandre.belloni@free-electrons.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=boris.brezillon@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@atmel.com \
--cc=nicolas.ferre@atmel.com \
--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