From: Jens Axboe <axboe@suse.de>
To: Andrew Ebling <aebling@tao-group.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CDRW packet writing status
Date: Wed, 16 Jan 2002 10:05:40 +0100 [thread overview]
Message-ID: <20020116100540.J3805@suse.de> (raw)
In-Reply-To: <1011171090.389.19.camel@spinel>
In-Reply-To: <1011171090.389.19.camel@spinel>
On Wed, Jan 16 2002, Andrew Ebling wrote:
> Hi Jens, (and fellow kernel hackers)
>
> Please can you advise of the current status of CDRW packet writing
> status?
>
> The latest version I can find is 0.0.2o-pre1, against 2.4.7.
>
> Is there any possibility of bringing it up to date with 2.4.x in the
> near future?
>
> If no new release is imminent, I _may_ have a go at bringing the patch
> up to date, but this will depend on how much has changed in affected
> areas. (i.e. I'll probably succeed if just trivial changes are
> involved.)
If you follow the packet-writing list, you'll see that Peter Osterlund
has been regularly updating the patch and adding fixes. There are
patches for 2.4.18-latest.
--
Jens Axboe
parent reply other threads:[~2002-01-16 9:06 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1011171090.389.19.camel@spinel>]
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=20020116100540.J3805@suse.de \
--to=axboe@suse.de \
--cc=aebling@tao-group.com \
--cc=linux-kernel@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