From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] at91: defconfig for 3.19 #1
Date: Thu, 4 Dec 2014 17:33:05 +0100 [thread overview]
Message-ID: <54808CC1.2010502@atmel.com> (raw)
In-Reply-To: <3905790.gg6cCb9BU6@wuerfel>
Le 04/12/2014 17:28, Arnd Bergmann a ?crit :
> On Tuesday 02 December 2014 17:28:31 Nicolas Ferre wrote:
>>
>> The following changes since commit 0df1f2487d2f0d04703f142813d53615d62a1da4:
>>
>> Linux 3.18-rc3 (2014-11-02 15:01:51 -0800)
>>
>> are available in the git repository at:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/nferre/linux-at91.git tags/at91-defconfig
>>
>> for you to fetch changes up to 4cd275f762a21cf21768e327873ba2883c839281:
>>
>> ARM: at91/defconfig: add DM9000 to at91_dt (2014-12-01 16:30:00 +0100)
>>
>> ----------------------------------------------------------------
>> First batch of defconfigs for AT91 / 3.19:
>> - use NEON for all C-A5, neon code handles the !NEON case
>> - add new XDMA driver
>> - add some useful drivers as we only have a single defconfig for all
>> AT91SAM9/RM9200
>
> I just noticed that this is based on -rc3, while the next/defconfig branch
> so far is based on -rc1. If you don't mind, could you rebase your
> branch on -rc1 as well and send it again so I can avoid the backmerge?
Sure, I do it right now.
Stay tuned ;-)
Bye,
--
Nicolas Ferre
next prev parent reply other threads:[~2014-12-04 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 16:28 [GIT PULL] at91: defconfig for 3.19 #1 Nicolas Ferre
2014-12-04 16:28 ` Arnd Bergmann
2014-12-04 16:33 ` Nicolas Ferre [this message]
2014-12-04 16:38 ` [GIT PULL] at91: defconfig for 3.19 #1 (bis) Nicolas Ferre
2014-12-04 18:10 ` Arnd Bergmann
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=54808CC1.2010502@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 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).