LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
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 28
Date: Thu, 28 Feb 2008 17:39:55 +1100 [thread overview]
Message-ID: <20080228173955.8dad1d5e.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 995 bytes --]
[Resend due to cut and paste error on address :-(]
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.
We are up to 38 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/. We have added a 64bit
s390 compiler to our list. If maintainers want to give advise about
cross compilers/configs that work, we are always open to add more builds.
Also, the linux-next tree is being build/boot tested by the guys at
test.kernel.org. Thanks to them.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2008-02-28 6:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 6:39 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-28 1:27 Stephen Rothwell
2022-02-28 15:34 Stephen Rothwell
2020-02-28 4:42 Stephen Rothwell
2019-02-28 8:19 Stephen Rothwell
2018-02-28 3:59 Stephen Rothwell
2017-02-28 3:01 Stephen Rothwell
2014-02-28 6:46 Stephen Rothwell
2013-02-28 2:27 Stephen Rothwell
2012-02-28 6:33 Stephen Rothwell
2008-02-28 6:35 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=20080228173955.8dad1d5e.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--subject='Re: linux-next: Tree for Feb 28' \
/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
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).