From: Stephen Rothwell <sfr@canb.auug.org.au>
To: linux-next@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: linux-next: Tree for Feb 27
Date: Wed, 27 Feb 2008 17:03:00 +1100 [thread overview]
Message-ID: <20080227170300.25c50fe3.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 903 bytes --]
Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
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
allmodconfig for both powerpc and x86_64.
There was only one minor merge problem and one build problem.
We are up to 35 trees, more are welcome (even if they are currently
empty).
Status of my local build tests is at
http://kisskb.ellerman.id.au/kisskb/branch/9/.
Also, the linux-next tree is being build/boot tested by the guys at
test.kernel.org. Thanks to them.
This release has one already known build problem: CONFIG_NFS_FS && !
CONFIG_NFS_V4 will fail to build.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2008-02-27 6:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 6:03 Stephen Rothwell [this message]
2008-02-27 6:09 ` linux-next: Tree for Feb 27 Stephen Rothwell
2008-02-27 7:00 ` Andrew Morton
2008-02-27 14:06 ` Stephen Rothwell
2008-02-27 14:43 ` Paul Moore
2008-02-27 15:31 ` Stephen Rothwell
2008-02-27 16:06 ` Paul Moore
2008-02-27 17:30 ` Jeff Garzik
2008-02-27 22:54 ` Stephen Rothwell
2008-02-27 19:55 ` Theodore Tso
2008-02-27 23:06 ` Stephen Rothwell
2012-02-27 7:20 Stephen Rothwell
2013-02-27 2:44 Stephen Rothwell
2014-02-27 6:03 Stephen Rothwell
2015-02-27 4:49 Stephen Rothwell
2017-02-27 3:34 Stephen Rothwell
2018-02-27 4:03 Stephen Rothwell
2019-02-27 6:44 Stephen Rothwell
2020-02-27 4:22 Stephen Rothwell
2023-02-27 1:18 Stephen Rothwell
2024-02-27 6:04 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=20080227170300.25c50fe3.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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).