From: Jens Axboe <jens.axboe@oracle.com>
To: "Miller, Mike (OS Dev)" <Mike.Miller@hp.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"scameron@beardog.cca.cpqcorp.net"
<scameron@beardog.cca.cpqcorp.net>
Subject: Re: [PATCH 6/6] cciss: fix bug if scsi tape support is disabled
Date: Thu, 7 Aug 2008 20:28:50 +0200 [thread overview]
Message-ID: <20080807182849.GC20055@kernel.dk> (raw)
In-Reply-To: <0F5B06BAB751E047AB5C87D1F77A778826B3F6BEF4@GVW0547EXC.americas.hpqcorp.net>
On Thu, Aug 07 2008, Miller, Mike (OS Dev) wrote:
> Jens wrote:
>
> > > > > uptodate more frequently :-)
> > > >
> > >
> > > I still can't find my latest patches in any tree. Jens?
> >
> > It's in for-next, for-akpm, and for-linus. It'll be going
> > upstream for this release, 2.6.27.
>
> Thanks, I'm just a bit impatient I guess. When a patch makes into
> for-* how long would it take to get to Linus' git tree?
Oh that depends entirely on what else it's queued with, but for
something going into the current branch, usually 2 weeks at the most.
--
Jens Axboe
next prev parent reply other threads:[~2008-08-07 18:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 21:18 [PATCH 6/6] cciss: fix bug if scsi tape support is disabled Mike Miller
2008-08-04 9:56 ` Jens Axboe
2008-08-05 22:30 ` Andrew Morton
2008-08-06 3:08 ` Stephen Rothwell
2008-08-06 10:33 ` Jens Axboe
2008-08-06 23:43 ` Stephen Rothwell
2008-08-07 15:29 ` Miller, Mike (OS Dev)
2008-08-07 17:20 ` Jens Axboe
2008-08-07 18:25 ` Miller, Mike (OS Dev)
2008-08-07 18:28 ` Jens Axboe [this message]
2008-08-06 10:32 ` 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=20080807182849.GC20055@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=Mike.Miller@hp.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=scameron@beardog.cca.cpqcorp.net \
--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