From: Alan Cox <alan@redhat.com>
To: Lionel.Bouton@inet6.fr (Lionel Bouton)
Cc: alan@redhat.com (Alan Cox), lcchang@sis.com.tw (Lei-Chun Chang),
andre@linuxdiskcert.org (Andre Hedrick),
marcelo@conectiva.com.br (Marcelo Tosatti),
linux-kernel@vger.kernel.org (linux-kernel)
Subject: Re: SiS 5513 ATA133 support patch for 2.4.19-rc3-ac3
Date: Sun, 28 Jul 2002 19:43:54 -0400 (EDT) [thread overview]
Message-ID: <200207282343.g6SNhse21139@devserv.devel.redhat.com> (raw)
In-Reply-To: <3D448052.4070805@inet6.fr> from "Lionel Bouton" at Jul 29, 2002 01:37:54 AM
> From past experiences we need 2 weeks of availability of code in
> the AC/pre kernels before the wave of meaningful bugreports ends.
Then I think ripping out the problem idents is safest
next prev parent reply other threads:[~2002-07-28 23:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-28 23:37 SiS 5513 ATA133 support patch for 2.4.19-rc3-ac3 Lionel Bouton
2002-07-28 23:43 ` Alan Cox [this message]
2002-07-29 7:11 ` Daniela Engert
2002-07-29 8:56 ` Lionel Bouton
2002-07-29 9:15 ` Daniela Engert
2002-07-29 11:35 ` L.C. Chang
2002-07-29 19:12 ` Marcelo Tosatti
2002-07-30 16:38 ` Lionel Bouton
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=200207282343.g6SNhse21139@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=Lionel.Bouton@inet6.fr \
--cc=andre@linuxdiskcert.org \
--cc=lcchang@sis.com.tw \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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