mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eyal Lebedinsky <eyal@eyal.emu.id.au>
To: Bartlomiej Zolnierkiewicz <dake@staszic.waw.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] ide-patch for 2.2.18(pre)
Date: Sun, 29 Oct 2000 11:43:21 +1100	[thread overview]
Message-ID: <39FB72A9.DB3E66BB@eyal.emu.id.au> (raw)
In-Reply-To: <Pine.LNX.4.21.0010280032200.9401-100000@tricky>

Bartlomiej Zolnierkiewicz wrote:
> 
> I have ported ide-patch to 2.2.18-17 and I'm now backporting
> 2.4.0 changes. New VIA, SLC, OSB4 drivers and MANY other things
> are already there.I hope that final 2.2.18-ide-patch will have
> IDE functionality equal to this in 2.4.0-test10...
> 
> Here is a snapshot (it's not thoroughly audited and tested):
>         http://republika.pl/bkz/ide.2.2.18-17.all.20001027.patch.bz2
> 
> And please cut that bullshit about ide-patch 2.2.x being unmantained.
> I don't use 2.2.x kernels anymore so I don't do ide-patches for pre
> kernels. But there will be patches for stable 2.2.x. (Although it's
> a real pain - I hate doing backporting instead of new stuff).

Can you say something about how well it patches (and behaves) with
the corresponding RAID patch, e.g.

http://www.kernel.org/pub/linux/kernel/people/mingo/raid-patches/raid-2.2.18-A2

--
Eyal Lebedinsky		(eyal@eyal.emu.id.au)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      parent reply	other threads:[~2000-10-29  0:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-27 22:41 Bartlomiej Zolnierkiewicz
2000-10-27 23:50 ` Andre Hedrick
2000-10-30  6:37   ` lamont
2000-10-29  0:12 ` Adrian Bunk
2000-11-17 17:14   ` Jamie Fifield
2000-10-29  0:43 ` Eyal Lebedinsky [this message]

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=39FB72A9.DB3E66BB@eyal.emu.id.au \
    --to=eyal@eyal.emu.id.au \
    --cc=dake@staszic.waw.pl \
    --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

all inboxes | Powered by JetHome®