From: Tejun Heo <htejun@gmail.com>
To: Frans de Boer <frans@fransdb.nl>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: SATA_SIL
Date: Fri, 02 Nov 2007 19:49:59 +0900 [thread overview]
Message-ID: <472B00D7.4090708@gmail.com> (raw)
In-Reply-To: <1193999025.32531.7.camel@ws1.fransdb.nl>
Frans de Boer wrote:
> Both sil and sil24 are not the same compared to the stock 2.6.22.9
> kernel.
And you're seeing problem on which?
>>> Do you still like to recieve my report as suggested by you?
>> Yeah, it should just work. Thanks.
>>
> Uh, your reacte on which part? The part of just wait for the 2.6.24
> release or that you recieve the boot.msg and hwinfo output?
It was... Yes, please report the bug && those drives should just work.
Thanks.
--
tejun
next prev parent reply other threads:[~2007-11-02 10:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-30 21:56 SATA_SIL Frans de Boer
2007-10-30 22:20 ` SATA_SIL Alan Cox
2007-10-30 22:58 ` SATA_SIL Greg Freemyer
2007-10-31 23:40 ` SATA_SIL Tejun Heo
[not found] ` <1193955948.17609.31.camel@ws1.fransdb.nl>
2007-11-02 1:11 ` SATA_SIL Tejun Heo
2007-11-02 10:23 ` SATA_SIL Frans de Boer
2007-11-02 10:49 ` Tejun Heo [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-30 0:18 sata_sil Harold Lee
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=472B00D7.4090708@gmail.com \
--to=htejun@gmail.com \
--cc=frans@fransdb.nl \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).