From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for August 4, add a new git tree please?
Date: Wed, 4 Aug 2010 18:24:39 -0400 [thread overview]
Message-ID: <20100804222439.GB2220@phenom.dumpdata.com> (raw)
In-Reply-To: <20100804222350.GA2220@phenom.dumpdata.com>
On Wed, Aug 04, 2010 at 06:23:50PM -0400, Konrad Rzeszutek Wilk wrote:
> On Wed, Aug 04, 2010 at 03:10:35PM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > As the merge window is open, please do not add 2.6.27 material to your
> > linux-next included trees until after 2.6.36-rc1.
Ugh. Resending as I didn't CC-ed LKML.
>
> I was wondering if you could add in your awesome tool this extra git
> tree:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
>
> (the head of it please)
>
> It has this patchset: http://lkml.org/lkml/2010/7/27/246
>
> that I have been carrying in
> git://git.kernel.org/pub/scm/linux/kernel/git/konrad/swiotlb-2.6.git
>
> but I realized it should probably not be in the swiotlb and was hence
> wondering if you would be OK adding in that extra git tree?
>
> Thanks
next prev parent reply other threads:[~2010-08-04 22:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 5:10 linux-next: Tree for August 4 Stephen Rothwell
2010-08-04 16:47 ` linux-next: Tree for August 4 (olpc_battery) Randy Dunlap
2010-08-09 16:39 ` Randy Dunlap
2010-08-09 17:17 ` David Woodhouse
2010-08-09 17:25 ` Anton Vorontsov
2010-08-04 17:16 ` [PATCH -next] ceph: rbd depends on BLOCK Randy Dunlap
[not found] ` <20100804222350.GA2220@phenom.dumpdata.com>
2010-08-04 22:24 ` Konrad Rzeszutek Wilk [this message]
2010-08-05 0:30 ` linux-next: Tree for August 4, add a new git tree please? Stephen Rothwell
2010-08-05 14:37 ` Konrad Rzeszutek Wilk
2010-08-05 14:41 ` 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=20100804222439.GB2220@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=linux-kernel@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.