From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] at91: fixes for 3.19 #1
Date: Tue, 16 Dec 2014 11:16:36 +0100 [thread overview]
Message-ID: <54900684.6040802@atmel.com> (raw)
In-Reply-To: <7hmw6oh7xh.fsf@deeprootsystems.com>
Le 15/12/2014 23:20, Kevin Hilman a ?crit :
> 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.
Absolutely, I'll do this.
Bye,
--
Nicolas Ferre
WARNING: multiple messages have this Message-ID (diff)
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Kevin Hilman <khilman@kernel.org>
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: Tue, 16 Dec 2014 11:16:36 +0100 [thread overview]
Message-ID: <54900684.6040802@atmel.com> (raw)
In-Reply-To: <7hmw6oh7xh.fsf@deeprootsystems.com>
Le 15/12/2014 23:20, Kevin Hilman a écrit :
> 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.
Absolutely, I'll do this.
Bye,
--
Nicolas Ferre
next prev parent reply other threads:[~2014-12-16 10:16 UTC|newest]
Thread overview: 6+ 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-12 9:46 ` Nicolas Ferre
2014-12-15 22:20 ` Kevin Hilman
2014-12-15 22:20 ` Kevin Hilman
2014-12-16 10:16 ` Nicolas Ferre [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=54900684.6040802@atmel.com \
--to=nicolas.ferre@atmel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.