public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: patch: packet-0.0.2k
Date: Wed, 9 May 2001 13:55:53 +0200	[thread overview]
Message-ID: <20010509135553.R521@suse.de> (raw)

Hi,

Put up the final packet-0.0.2k patch, against 2.4.4 and 2.4.5-pre1.
A more complete changelog, since packet-0.0.2j:

        - Fix b_count bh bug, forgot to release buffers
        - Fix lock_buffer buf
        - Remove pkt_gather_data rerun to print buggy buffer list, that
          bug has been fixed.
        - Changed proc layout to /proc/driver/pktcdvd/pktcdvdX, one file
          per writer. Also compiles without proc fs support now.
        - Set quiet bit on write cache settings, drive may not support
          it
        - Remove PACKET_WAKEUP ioctl (buggy too, noticed by jgarzik)
        - Merge with 2.4.5-pre1
        - Added recovery mode
        - (with above) Added relocate_blocks super operation
        - Missing break in PACKET_GET_STATS ioctl
        - invalidate_device changes
        - Always piggy buffers to maintain b_end_io consistency
        - Change several BUG's to complain and abort nicely
        - Remove __dump_rq from ll_rw_blk and SCSI
        - Updated INSTALL and FAQ
        - Added kernel UDF diff
        - Fixup end_request handling
        - Put unplug back in
        - Rewrite kernel thread setup/exit
        - Set device RO on BLKROSET

*.kernel.org/pub/linux/kernel/people/axboe/packet/

The sourceforge packages are going up as I write this, so should be
there very soon. Note that a UDF patch is now included against the
kernel UDF, so you don't have to use cvs udf for a stable setup.

Background -- this is a module that allows transparent writing to CD-RW
(CD-R will follow) discs, so you can use it as a big floppy basically.

-- 
Jens Axboe


                 reply	other threads:[~2001-05-09 11:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20010509135553.R521@suse.de \
    --to=axboe@suse.de \
    --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