From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Konrad Rzeszutek Wilk <konrad.wilk@ORACLE•COM>
Cc: linux-next@vger•kernel.org
Subject: Re: IBFT and SWIOTLB tree.
Date: Mon, 1 Mar 2010 17:25:54 +1100 [thread overview]
Message-ID: <20100301172554.92574f5d.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20100224150034.GB20890@phenom.dumpdata.com>
[-- Attachment #1: Type: text/plain, Size: 2975 bytes --]
Hi Konrad,
On Wed, 24 Feb 2010 10:00:34 -0500 Konrad Rzeszutek Wilk <konrad.wilk@ORACLE•COM> wrote:
>
> On Wed, Feb 24, 2010 at 07:39:31PM +1100, Stephen Rothwell wrote:
> >
> > I would need a bit a background for these trees since you are not listed
> > as a maintainer in the MAINTAINERS file.
>
> Hmm, weird. IBFT is the patch set for the drivers/firmware/iscsi_ibft.c
> which was developed by me.
And I see you have added a MAINTAINERS entry and Linus has merged the two
patches. I will add this tree tomorrow. Please don't add any 2.6.35
material until after 2.6.34-rc1 is released. 2.6.34 material and fixes
are OK.
> > > git://git.kernel.org/pub/scm/linux/kernel/git/konrad/swiotlb-2.6.git
>
> That one is the re-work of the SWIOTLB IOMMU code. Not a maintainer, but
> I want to make sure that the patches don't stomp/break other code.
Is this intended for 3.6.34? I can't add that tree yet, as it has a
series of patches in it that have no Signed-off-by lines. This material
should also get fairly wide review and I would expect to see some
Acked-by lines before the patches were ready for inclusion.
> > The master branch of both these trees is empty relative to Linus' tree ...
>
> Let me fix that. I had the HEAD point to the right branch, but didn't
> think of updating the refs/heads/master file.
Since you didn't tell me what branch to use, I assumed the master branch.
Thanks for adding your subsystem tree as a participant of linux-next. As
you may know, this is not a judgment of your code. The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window.
You will need to ensure that the patches/commits in your tree/series have
been:
* submitted under GPL v2 (or later) and include the Contributor's
Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux 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
Legal Stuff:
By participating in linux-next, your subsystem tree contributions are
public and will be included in the linux-next trees. You may be sent
e-mail messages indicating errors or other issues when the
patches/commits from your subsystem tree are merged and tested in
linux-next. These messages may also be cross-posted to the linux-next
mailing list, the linux-kernel mailing list, etc. The linux-next tree
project and IBM (my employer) make no warranties regarding the linux-next
project, the testing procedures, the results, the e-mails, etc. If you
don't agree to these ground rules, let me know and I'll remove your tree
from participation in linux-next.
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-03-01 6:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 16:00 IBFT and SWIOTLB tree Konrad Rzeszutek Wilk
2010-02-24 8:39 ` Stephen Rothwell
2010-02-24 15:00 ` Konrad Rzeszutek Wilk
2010-03-01 6:25 ` Stephen Rothwell [this message]
2010-03-01 18:26 ` Konrad Rzeszutek Wilk
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=20100301172554.92574f5d.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=konrad.wilk@ORACLE$(echo .)COM \
--cc=linux-next@vger$(echo .)kernel.org \
/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