From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Len Brown <lenb@kernel.org>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
sfi-devel@simplefirmware.org
Subject: Re: linux-next: Tree for June 19
Date: Sat, 20 Jun 2009 15:04:33 +1000 [thread overview]
Message-ID: <20090620150433.4e038676.sfr@canb.auug.org.au> (raw)
In-Reply-To: <alpine.LFD.2.00.0906200012200.4325@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1193 bytes --]
Hi Len,
On Sat, 20 Jun 2009 00:16:49 -0400 (EDT) Len Brown <lenb@kernel.org> wrote:
>
> Please add the Simple Firmware Interface "sfi-test" branch to linux-next:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-sfi-2.6.git sfi-test
Is this 2.6.31 or 32 material?
> A description of the project is on the SFI home page: http://simplefirmware.org/
>
> Note: like ACPI's test branch, this branch will be occasionally re-based
> as the patches in it evolve.
That's fine.
Should I put just you as the contact, or add the mailing list as well?
What I tell everyone: all patches/commits in the tree/series must
have been:
posted to a relevant mailing list
reviewed
unit tested
destined for the next merge window (or the current release)
*before* they are included. The linux-next tree is for integration
testing and to lower the impact of conflicts between subsystems in the
next merge window.
Basically, this should be just what you would send to Linus (or ask him
to fetch). It is allowed to be rebased if you deem it necessary.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-06-20 5:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 7:26 Stephen Rothwell
2009-06-19 13:44 ` Nico -telmich- Schottelius
2009-06-19 17:38 ` [PATCH -next] dm: dm-log-userspace depends on NET Randy Dunlap
2009-06-19 18:31 ` [dm-devel] " Jonathan Brassow
2009-06-19 18:24 ` [PATCH -next] dm: fix dm-log-userspace printk format Randy Dunlap
2009-06-19 18:32 ` [dm-devel] " Jonathan Brassow
2009-06-20 4:16 ` linux-next: Tree for June 19 Len Brown
2009-06-20 5:04 ` Stephen Rothwell [this message]
2009-06-20 5:12 ` Stephen Rothwell
2009-06-20 18:27 ` Len Brown
2009-06-21 15:54 ` Stephen Rothwell
2009-06-29 5:25 ` Stephen Rothwell
2009-06-29 7:14 ` Ingo Molnar
2009-06-29 7:30 ` Stephen Rothwell
2009-06-23 6:34 ` Len Brown
2009-06-23 8:54 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2008-06-19 8:05 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=20090620150433.4e038676.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfi-devel@simplefirmware.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
all inboxes | Powered by JetHome®