From: David Miller <davem@davemloft.net>
To: jens.axboe@oracle.com
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
James.Bottomley@HansenPartnership.com
Subject: Re: [GIT PULL] block changes for 2.6.28
Date: Fri, 10 Oct 2008 11:51:08 -0700 (PDT) [thread overview]
Message-ID: <20081010.115108.199149570.davem@davemloft.net> (raw)
In-Reply-To: <20081010174931.GG19428@kernel.dk>
From: Jens Axboe <jens.axboe@oracle.com>
Date: Fri, 10 Oct 2008 19:49:31 +0200
> On Fri, Oct 10 2008, David Miller wrote:
> > From: Jens Axboe <jens.axboe@oracle.com>
> > Date: Fri, 10 Oct 2008 10:09:16 +0200
> >
> > > This is the bulk of the block layer changes for 2.6.28. As other git
> > > trees are based on this (like SCSI), it would be good if you could merge
> > > it sooner rather than later.
> > >
> > > Please pull from:
> > >
> > > git://git.kernel.dk/linux-2.6-block.git for-2.6.28
> >
> > Did you merge in my generic remote softirq bits or are you going
> > to do that later?
>
> I did not, I thought you would merge them youself (I acked the patchset,
> iirc). So either do that, or I can take it through the second (and
> smaller) merge of block bits. Either way, I'm fine with it for 2.6.28
> :-)
Please take it in.
In my final posting of those changes I made it clear that the way
to do this is to have any users of the infrastructure pull my GIT
tree in:
master.kernel.org:/pub/scm/linux/kernel/git/davem/softirq-2.6.git
and whoever went first into Linus's tree would get it there.
I'm not at the point where I can use this in the networking and likely
won't have such work ready for 2.6.28 so it's imperative that you do
this at this point :-)
next prev parent reply other threads:[~2008-10-10 18:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-10 8:09 Jens Axboe
2008-10-10 16:29 ` David Miller
2008-10-10 17:49 ` Jens Axboe
2008-10-10 18:51 ` David Miller [this message]
2008-10-10 20:00 ` Jens Axboe
2008-10-10 18:02 ` Linus Torvalds
2008-10-10 20:01 ` Jens Axboe
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=20081010.115108.199149570.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=James.Bottomley@HansenPartnership.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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®