public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: CaT <cat@zip.com.au>
To: linux-kernel@vger.kernel.org
Subject: IT8212/ITE RAID
Date: Sun, 14 Aug 2005 15:30:17 +1000	[thread overview]
Message-ID: <20050814053017.GA27824@zip.com.au> (raw)

Having an IDE card with one of these chipsets has left me with a bit of
a quandry. I've seen 2 different patch, both seemingly not going
anywhere.

1. Alan Cox's IDE driver that was included in his ac patchset, which
   seems to have died at 2.6.11ac7.
2. A brief visit from a SCSI IDE driver in Andrew Mortons mm patchset.
   It lived a brief but noted life before being taken out without any
   reason (that I spotted) in 2.6.12-rc4-mm1

Now, I'd like to upgrade my kernel to cover the security patches
releases since 11ac7 but... do I extract the ac driver or the mm driver
and try to use it? Will my data be eaten? Is there any chance of seeing
either driver in the kernel, proper?

Just wondering which way to go and stuff. :/

-- 
    "To the extent that we overreact, we proffer the terrorists the
    greatest tribute."
    	- High Court Judge Michael Kirby

             reply	other threads:[~2005-08-14  5:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-14  5:30 CaT [this message]
2005-08-14 11:08 ` IT8212/ITE RAID Daniel Drake
2005-08-14 11:47   ` CaT
2005-08-14 12:44     ` Daniel Drake
2005-08-14 13:33       ` Alan Cox
2005-08-14 15:01         ` Bartlomiej Zolnierkiewicz
2005-08-14 15:52           ` Alan Cox
2005-08-14 15:56             ` Bartlomiej Zolnierkiewicz
2005-08-14 21:13               ` Alan Cox
2005-08-14 21:20                 ` Bartlomiej Zolnierkiewicz
2005-08-22  9:28                   ` Bartlomiej Zolnierkiewicz
2005-08-22 10:33                     ` Alan Cox
2005-08-22 10:21                       ` Bartlomiej Zolnierkiewicz
2005-08-22 23:48                     ` Andre Hedrick
2005-08-14 23:59         ` CaT
2005-08-16 22:41         ` CaT
2005-08-14 21:09   ` James Tabor

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=20050814053017.GA27824@zip.com.au \
    --to=cat@zip.com.au \
    --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