public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Henning P. Schmiedehausen" <hps@intermeta.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Bigggg Maxtor drives (fwd)
Date: Thu, 10 Jan 2002 09:50:37 +0000 (UTC)	[thread overview]
Message-ID: <a1jo5d$u60$1@forge.intermeta.de> (raw)
In-Reply-To: <3C3D0718.2060602@xmission.com> <Pine.LNX.4.10.10201092011420.5104-100000@master.linux-ide.org>

Andre Hedrick <andre@linux-ide.org> writes:

>All it will take is to have the 2.2/2.4/2.5 kernel maintainers to agree to
>the corrective patches.

So you do have 2.2 patches? Where can I get them?

	Regards
		Henning

-- 
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen       -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH     hps@intermeta.de

Am Schwabachgrund 22  Fon.: 09131 / 50654-0   info@intermeta.de
D-91054 Buckenhof     Fax.: 09131 / 50654-20   

  reply	other threads:[~2002-01-10  9:51 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-10  1:46 Bigggg Maxtor drives (fwd) Andre Hedrick
2002-01-10  3:14 ` Benjamin S Carrell
2002-01-10  4:03   ` Chris Ball
2002-01-10  4:31     ` Jim Crilly
2002-01-10 12:11       ` Rik van Riel
2002-01-10 12:15         ` Jens Axboe
2002-01-10 13:22           ` Marcel J.E. Mol
2002-01-10 14:56             ` Hans Reiser
2002-01-10 15:04               ` Jens Axboe
2002-01-10 12:23         ` Lionel Bouton
2002-01-10 12:40         ` Alan Cox
2002-01-10 12:45           ` David Weinehall
2002-01-10 13:47             ` Alan Cox
2002-01-10 18:59         ` Aaron Blew
2002-01-10 19:14           ` Jens Axboe
2002-01-10 19:14       ` Ricky Beam
2002-01-10 19:59         ` Alan Cox
2002-01-10 19:08     ` Ricky Beam
2002-01-10  4:59   ` Andre Hedrick
2002-01-10  9:50     ` Henning P. Schmiedehausen [this message]
2002-01-11 21:13     ` Rogier Wolff
2002-01-12  9:14       ` Andre Hedrick
  -- strict thread matches above, loose matches on Subject: below --
2002-01-10 10:00 Andries.Brouwer

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='a1jo5d$u60$1@forge.intermeta.de' \
    --to=hps@intermeta.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