From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for May 8
Date: Thu, 8 May 2008 20:49:05 -0500 [thread overview]
Message-ID: <20080508204905.159a4d34@vader.jdub.homelinux.org> (raw)
In-Reply-To: <20080508142514.6990f80e.sfr@canb.auug.org.au>
On Thu, 8 May 2008 14:25:14 +1000
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> You can see which trees have been included by looking in the Next/Trees
> file in the source. There are also quilt-import.log and merge.log files
> in the Next directory. Between each merge, the tree was built with
> a ppc64_defconfig for powerpc and an allmodconfig for x86_64. After the
> final fixups, it is also built with powerpc allnoconfig,
> 44x/ebony_defconfig and allyesconfig.
If you're agreeable, we should switch it from 44x/ebony_defconfig to
ppc44x_defconfig. That will build more configurations as a result of
being a multi-board config.
josh
next prev parent reply other threads:[~2008-05-09 1:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 4:25 linux-next: Tree for May 8 Stephen Rothwell
2008-05-09 1:49 ` Josh Boyer [this message]
2008-05-09 6:06 ` Stephen Rothwell
2009-05-08 8:02 Stephen Rothwell
2012-05-08 8:15 Stephen Rothwell
2013-05-08 4:01 Stephen Rothwell
2014-05-08 6:11 Stephen Rothwell
2015-05-08 5:34 Stephen Rothwell
2017-05-08 4:48 Stephen Rothwell
2018-05-08 5:22 Stephen Rothwell
2019-05-08 7:34 Stephen Rothwell
2020-05-08 11:15 Stephen Rothwell
2023-05-08 4:27 Stephen Rothwell
2023-05-08 10:06 ` Stephen Rothwell
2024-05-08 7:29 Stephen Rothwell
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=20080508204905.159a4d34@vader.jdub.homelinux.org \
--to=jwboyer@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).