From: Pat LaVarre <p.lavarre@ieee.org>
To: Jens Axboe <axboe@suse.de>
Cc: linux-scsi@vger.kernel.org, John McKell <McKellj@iomega.com>
Subject: Re: CDC_RAM for lk 2.4, PATCH proposed
Date: 03 Jun 2004 12:30:20 -0600 [thread overview]
Message-ID: <1086287419.11685.4.camel@patibmrh9> (raw)
In-Reply-To: <1085153286.6103.24.camel@patibmrh9>
Jens A:
> > http://marc.theaimsgroup.com/?l=linux-scsi&m=108509426227562
> > > diff -Nurp linux-2.4.27-pre3/... linux-2.4.27-pre3-pel/...
> >
> > [snip]
> >
> > Patch looks fine to me,
> > I'll send it to Marcelo for inclusion. Thanks!
>
> Wonderful news, thank you both, consequently now with more hope I look
> forward to writing kernel patches exclusively for 2.6.
Today 2004-6-3 I see no mention of the 5-21 CDC_RAM for lk 2.4 patch
near such strings as "Marcelo" and "Axboe" in:
http://www.kernel.org/pub/linux/kernel/v2.4/testing/patch-2.4.27.log
I will think go on naively believing that is the right place to poll
until someone tells me different (or we all start working 2.4.28).
Pat LaVarre
next prev parent reply other threads:[~2004-06-03 18:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-15 16:52 CDC_RAM for lk 2.4, PATCH proposed Pat LaVarre
2004-04-16 12:09 ` Jens Axboe
2004-04-23 22:25 ` John McKell
2004-04-28 1:46 ` Pat LaVarre
2004-04-28 14:48 ` Pat LaVarre
[not found] ` <1084897080.3746.38.camel@patibmrh9>
2004-05-19 8:15 ` Jens Axboe
2004-05-19 15:45 ` Pat LaVarre
2004-05-20 8:06 ` Jens Axboe
2004-05-20 22:01 ` Pat LaVarre
2004-05-20 23:51 ` Pat LaVarre
2004-05-21 6:53 ` Jens Axboe
2004-05-21 15:28 ` Pat LaVarre
2004-06-03 18:30 ` Pat LaVarre [this message]
2004-06-03 18:32 ` Jens Axboe
2004-06-04 14:53 ` Marcelo Tosatti
2004-06-04 15:18 ` Pat LaVarre
2004-06-04 15:24 ` Jens Axboe
2004-06-04 15:27 ` Pat LaVarre
2004-06-04 15:36 ` Jens Axboe
2004-06-18 21:42 ` Pat LaVarre
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=1086287419.11685.4.camel@patibmrh9 \
--to=p.lavarre@ieee.org \
--cc=McKellj@iomega.com \
--cc=axboe@suse.de \
--cc=linux-scsi@vger.kernel.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