From: Linus Walleij <linus.ml.walleij@gmail•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org
Subject: Re: linux-next: Tree for June 23
Date: Thu, 23 Jun 2011 12:25:07 +0200 [thread overview]
Message-ID: <BANLkTimZFS+dm1D6Dfb79gw1-3DXMBHb4A@mail.gmail.com> (raw)
In-Reply-To: <20110623155431.6bfe3b40.sfr@canb.auug.org.au>
2011/6/23 Stephen Rothwell <sfr@canb•auug.org.au>:
> Status of my local build tests will be at
> http://kisskb.ellerman.id.au/linux-next . If maintainers want to give
> advice about cross compilers/configs that work, we are always open to add
> more builds.
For the ARM compiler I added a vexpress_defconfig a while back.
This is the latest generation of clunky ARM reference design and
typically the target for much ARM-internal Linux work these days.
It'd be good if it was included in kisskb!
Thanks,
Linus Walleij
next prev parent reply other threads:[~2011-06-23 10:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 5:54 linux-next: Tree for June 23 Stephen Rothwell
2011-06-23 10:25 ` Linus Walleij [this message]
2011-06-23 10:54 ` Stephen Rothwell
2011-06-23 16:14 ` linux-next: Tree for June 23 (net) Randy Dunlap
2011-06-23 17:17 ` Randy Dunlap
2011-06-23 18:13 ` Mike Frysinger
2011-06-24 4:21 ` David Miller
2011-06-24 15:38 ` Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2010-06-23 5:45 linux-next: Tree for June 23 Stephen Rothwell
2009-06-23 5:33 Stephen Rothwell
2009-06-23 6:07 ` Stephen Rothwell
2008-06-23 8:25 Stephen Rothwell
2008-06-23 10:23 ` Vegard Nossum
2008-06-23 10:26 ` Vegard Nossum
2008-06-23 11:02 ` Vegard Nossum
2008-06-23 12:26 ` Vegard Nossum
2008-06-23 17:26 ` Vegard Nossum
2008-06-23 17:43 ` Vegard Nossum
2008-06-23 18:56 ` Pekka J Enberg
2008-06-23 19:21 ` Christoph Lameter
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=BANLkTimZFS+dm1D6Dfb79gw1-3DXMBHb4A@mail.gmail.com \
--to=linus.ml.walleij@gmail$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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