From: Jens Axboe <axboe@suse.de>
To: John McKell <mckellj@iomega.com>
Cc: Pat LaVarre <LAVARRE@iomega.com>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH]:Amended:Allow random write for PDT 5 profile 2 Removable Disk
Date: Mon, 8 Mar 2004 20:20:11 +0100 [thread overview]
Message-ID: <20040308192011.GG23525@suse.de> (raw)
In-Reply-To: <1078769250.7104.15.camel@lintest.iomegacorp.com>
On Mon, Mar 08 2004, John McKell wrote:
> Jens,
>
> All of this discussion has left me a bit confused:
>
> On Sunday, March 7, 2004, Jens Axboe wrote:
> > On Sat, Mar 06 2004, Pat LaVarre wrote:
> > > > queued it for 2.6.4-pre
> > >
> > > Absent from 2.6.4-rc2, I think.
> >
> > Will most likely have to wait for 2.6.5-pre/rc
>
> What is the best indicator that I can use to monitor and know when a given
> patch is to be inserted into the kernel? I monitor kernel.org at least
> once a day, if not more, but I hope that there would be something a bit
> more informative. If checking kernel.org frequently is the only way, then
> I can deal with that.
You can check changes between last "released" (not 2.6.4, but also
2.6.4-pre2 for instance) kernel here:
http://www.kernel.org/pub/linux/kernel/v2.5/testing/cset/
that will show you what's queued for next sub-release.
--
Jens Axboe
next prev parent reply other threads:[~2004-03-08 19:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-08 18:07 [PATCH]:Amended:Allow random write for PDT 5 profile 2 Removable Disk John McKell
2004-03-08 19:20 ` Jens Axboe [this message]
2004-03-08 20:01 ` [PATCH]:Amended:Allow random write for PDT 5 profile 2 Removabl e Disk Pat LaVarre
-- strict thread matches above, loose matches on Subject: below --
2004-03-15 23:16 [PATCH]:Amended:Allow random write for PDT 5 profile 2 Removable Disk John McKell
2004-03-16 8:43 ` Jens Axboe
2004-03-06 17:16 Pat LaVarre
2004-03-07 11:45 ` Jens Axboe
2004-02-12 19:00 John McKell
2004-02-13 16:07 ` 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=20040308192011.GG23525@suse.de \
--to=axboe@suse.de \
--cc=LAVARRE@iomega.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mckellj@iomega.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