From: Jens Axboe <jens.axboe@oracle.com>
To: "S, Chandrakala (STSD)" <chandrakala.s@hp.com>
Cc: Kiyoshi Ueda <k-ueda@ct.jp.nec.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-ide@vger.kernel.org, "Miller,
Mike (OS Dev)" <mike.miller@hp.com>,
grant.likely@secretlab.ca, dm-devel@redhat.com,
j-nomura@ce.jp.nec.com
Subject: Re: [PATCH 0/7] blk_end_request: full I/O completion handler
Date: Fri, 8 Feb 2008 09:51:48 +0100 [thread overview]
Message-ID: <20080208085148.GD15220@kernel.dk> (raw)
In-Reply-To: <77334B9413C72244AE1B51ADD4868D700AFD9D60@BGEEXC02.asiapacific.cpqcorp.net>
On Fri, Feb 08 2008, S, Chandrakala (STSD) wrote:
> Hi,
>
> Thanks for the information!
> We would like to know when does the 2.6.25 kernel will be available at
> kernel.org.
So would I, if I locate my crystal ball I'll be sure to let you know :-)
Seriously, given past experience, it's probably sometime in April.
>
> Thanks,
> Chandrakala
>
> -----Original Message-----
> From: Jens Axboe [mailto:jens.axboe@oracle.com]
> Sent: Tuesday, February 05, 2008 4:09 PM
> To: S, Chandrakala (STSD)
> Cc: Kiyoshi Ueda; linux-kernel@vger.kernel.org;
> linux-scsi@vger.kernel.org; linux-ide@vger.kernel.org; Miller, Mike (OS
> Dev); grant.likely@secretlab.ca; dm-devel@redhat.com;
> j-nomura@ce.jp.nec.com
> Subject: Re: [PATCH 0/7] blk_end_request: full I/O completion handler
>
> On Tue, Feb 05 2008, S, Chandrakala (STSD) wrote:
> > Hello,
> >
> > We would like to know in which kernel version these patches are
> > available.
>
> They were merged after 2.6.24 was released, so they will show up in the
> 2.6.25 kernel.
>
> --
> Jens Axboe
>
--
Jens Axboe
prev parent reply other threads:[~2008-02-08 8:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 22:39 [PATCH 0/7] blk_end_request: full I/O completion handler Kiyoshi Ueda
2007-09-03 7:45 ` Jens Axboe
2008-02-05 10:34 ` S, Chandrakala (STSD)
2008-02-05 10:38 ` Jens Axboe
2008-02-08 5:40 ` S, Chandrakala (STSD)
2008-02-08 8:51 ` Jens Axboe [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=20080208085148.GD15220@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=chandrakala.s@hp.com \
--cc=dm-devel@redhat.com \
--cc=grant.likely@secretlab.ca \
--cc=j-nomura@ce.jp.nec.com \
--cc=k-ueda@ct.jp.nec.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mike.miller@hp.com \
/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).