From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux-Next <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: linux-next: Tree for May 30
Date: Tue, 4 Jun 2013 18:04:40 +1000 [thread overview]
Message-ID: <20130604180440.852c851802ce2e83c014d2ef@canb.auug.org.au> (raw)
In-Reply-To: <51AC579B.8040902@atmel.com>
[-- Attachment #1: Type: text/plain, Size: 321 bytes --]
Hi Nicolas,
On Mon, 3 Jun 2013 10:45:15 +0200 Nicolas Ferre <nicolas.ferre@atmel.com> wrote:
>
> Is it possible for you to move the building to the replacement defconfigs:
> at91sam9260_9g20_defconfig
> at91sam9261_9g10_defconfig
Done.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-06-04 8:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 6:33 linux-next: Tree for May 30 Stephen Rothwell
2013-05-30 8:07 ` Geert Uytterhoeven
2013-06-03 6:36 ` Stephen Rothwell
2013-06-03 8:45 ` Nicolas Ferre
2013-06-04 8:04 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-30 5:29 Stephen Rothwell
2019-05-30 6:21 Stephen Rothwell
2018-05-30 11:45 Stephen Rothwell
2017-05-30 5:16 Stephen Rothwell
2016-05-30 3:22 Stephen Rothwell
2016-05-30 14:04 ` Sudip Mukherjee
2014-05-30 7:34 Stephen Rothwell
2011-05-30 3:35 Stephen Rothwell
2008-05-30 8:19 Stephen Rothwell
2008-06-01 10:33 ` Thomas Meyer
2008-06-01 15:07 ` Ingo Molnar
2008-06-02 17:40 ` Thomas Meyer
2008-06-02 18:57 ` Ingo Molnar
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=20130604180440.852c851802ce2e83c014d2ef@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=geert@linux-m68k.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=nicolas.ferre@atmel.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;
as well as URLs for NNTP newsgroup(s).