From: Christoph Hellwig <hch@infradead.org>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Luben Tuikov <luben_tuikov@adaptec.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [ANNOUNCE] Adaptec SAS/SATA device driver [27/27]
Date: Thu, 17 Feb 2005 20:36:42 +0000 [thread overview]
Message-ID: <20050217203642.GA9030@infradead.org> (raw)
In-Reply-To: <4214FF23.2070505@tls.msk.ru>
On Thu, Feb 17, 2005 at 11:31:31PM +0300, Michael Tokarev wrote:
> Luben Tuikov wrote:
> >The readme file.
> >
> >diff -Nru a/drivers/scsi/adp94xx/readme.txt
> []
> >+= README for =
> >+= Red Hat Linux Advanced Server 2.1 =
> >+= Red Hat Enterprise Linux 3.0 =
> >+= SuSE Linux Enterprise Server 8 / UnitedLinux 1.0 =
> >+= SuSE Linux Enterprise Server 9 =
>
> Hmm... will it work with a distribution not listed above? ;)
> Sorry can't resist...
Even if it does this README doesn't belong into the kernel tree.
prev parent reply other threads:[~2005-02-17 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-17 17:38 [ANNOUNCE] Adaptec SAS/SATA device driver [27/27] Luben Tuikov
2005-02-17 20:31 ` Michael Tokarev
2005-02-17 20:36 ` Christoph Hellwig [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=20050217203642.GA9030@infradead.org \
--to=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=luben_tuikov@adaptec.com \
--cc=mjt@tls.msk.ru \
/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