linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org
Subject: Re: IBFT and SWIOTLB tree.
Date: Mon, 1 Mar 2010 13:26:42 -0500	[thread overview]
Message-ID: <20100301182642.GA31926@phenom.dumpdata.com> (raw)
In-Reply-To: <20100301172554.92574f5d.sfr@canb.auug.org.au>

On Mon, Mar 01, 2010 at 05:25:54PM +1100, Stephen Rothwell wrote:
> 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.

Excellent.
> 
> > > > 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.

Ok. I am still a bit new at this so I wasn't sure about the inclusion
criteria. Please defer that git tree (swiotlb-2.6) until I get it moving upstream.

      reply	other threads:[~2010-03-01 18:51 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
2010-03-01 18:26       ` Konrad Rzeszutek Wilk [this message]

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=20100301182642.GA31926@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --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).