All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: linux-ide@vger.kernel.org
Subject: [PATCH] 2.5.34 IDE
Date: Wed, 11 Sep 2002 10:01:07 +0200	[thread overview]
Message-ID: <20020911080107.GA6444@suse.de> (raw)

----- Forwarded message from Jens Axboe <axboe@suse.de> -----

From: Jens Axboe <axboe@suse.de>
Date: Wed, 11 Sep 2002 10:00:36 +0200
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH] 2.5.34 IDE

Hi,

I've updated 2.5 IDE code to match what is currently in 2.4.20-pre5-ac4,
since is much nicer and better structured. There have also been some
cleanups along the way, all of which have been passed back to Alan for
the 2.4 tree.

If you feel adventorous, please try:

*.kernel.org:/pub/linux/kernel/people/axboe/patches/v2.5/2.5.34/ide-2.5.34-4.gz

Note that the patch is _huge_ because it moves files around! I've also
got this in a bk tree with proper file moving etc (and patch split in a
million pieces), but that's mainly for Linus to pull (ie its on
master right now, and I'm not inclined to move it). If someone wants to
see it though, I can probably put it somewhere public.

If you apply against 2.5.34-BK (instead of 2.5.34 virgin), note that
some parts are already in. In that case, remove the parts of the diff
that update:

arch/i386/pci/common.c
arch/i386/pci/i386.c
arch/i386/pci/pci.h
arch/i386/pci/visws.c
drivers/pci/pci.c
include/linux/blkdev.h
include/linux/hdreg.h
include/linux/pci.h
include/linux/pci_ids.h

-- 
Jens Axboe


----- End forwarded message -----

-- 
Jens Axboe


             reply	other threads:[~2002-09-11  8:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-11  8:01 Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-09-11  8:00 [PATCH] 2.5.34 IDE 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=20020911080107.GA6444@suse.de \
    --to=axboe@suse.de \
    --cc=linux-ide@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.