From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <tj@kernel.org>
Cc: Anssi Hannula <anssi.hannula@iki.fi>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Mark Lord <kernel@teksavvy.com>
Subject: Re: [PATCH #upstream] ahci: add HFLAG_YES_FBS and apply it to 88SE9128
Date: Tue, 18 Jan 2011 20:07:37 -0500 [thread overview]
Message-ID: <4D363959.6090203@garzik.org> (raw)
In-Reply-To: <4CFFCAE3.1090106@kernel.org>
On 12/08/2010 01:13 PM, Tejun Heo wrote:
> Hello,
>
> On 12/08/2010 07:09 PM, Jeff Garzik wrote:
>>> I'm not completely comfortable with going ahead with the patch tho.
>>> It probably is okay but it's still a shot in the dark. Is there
>>> anyone with marvell contact?
>>
>> I have docs for most Marvell models, but not this one; and no
>> contacts... Presumably it is some variant of their existing Marvell
>> AHCI line of chips, but beyond that, you and I are both just
>> guessing.
>
> Eh, well, in that case as it's a fix one way or the other,
>
> Acked-by: Tejun Heo<tj@kernel.org>
It's ugly, and maybe it will go away in the future. But I don't think
it will harm existing installations to add the additional class match,
so I'm applying it.
Jeff
next prev parent reply other threads:[~2011-01-19 1:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-24 14:53 [PATCH #upstream] ahci: add HFLAG_YES_FBS and apply it to 88SE9128 Tejun Heo
2010-08-17 21:54 ` Jeff Garzik
2010-11-30 2:04 ` Anssi Hannula
2010-11-30 13:31 ` Tejun Heo
2010-11-30 20:10 ` Anssi Hannula
2010-12-07 19:45 ` Anssi Hannula
2010-12-08 11:10 ` Tejun Heo
2010-12-08 18:09 ` Jeff Garzik
2010-12-08 18:13 ` Tejun Heo
2011-01-07 19:22 ` Anssi Hannula
2011-01-19 1:07 ` Jeff Garzik [this message]
2010-12-20 3:24 ` Anssi Hannula
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=4D363959.6090203@garzik.org \
--to=jeff@garzik.org \
--cc=anssi.hannula@iki.fi \
--cc=kernel@teksavvy.com \
--cc=linux-ide@vger.kernel.org \
--cc=tj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.