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: Wed, 24 Feb 2010 10:00:34 -0500 [thread overview]
Message-ID: <20100224150034.GB20890@phenom.dumpdata.com> (raw)
In-Reply-To: <20100224193931.89bb7e87.sfr@canb.auug.org.au>
On Wed, Feb 24, 2010 at 07:39:31PM +1100, Stephen Rothwell wrote:
> Hi Konrad,
>
> On Tue, 23 Feb 2010 11:00:34 -0500 Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> >
> > I was wondering if it would be possible to include these two trees in
> > the automatic merge/build process:
>
> 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.
>
> > git://git.kernel.org/pub/scm/linux/kernel/git/konrad/ibft-2.6.git
> >
> > and
> > 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.
>
> 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.
next prev parent reply other threads:[~2010-02-24 15:29 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 [this message]
2010-03-01 6:25 ` Stephen Rothwell
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=20100224150034.GB20890@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.