[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAN8TOE9+RR_cBLTzZCYVbf0T0a_5sBWxrj11ZdJTQ7GJ4yMi0g@mail.gmail.com>
Date: Mon, 20 Feb 2012 14:06:49 -0800
From: Brian Norris <computersforpeace@...il.com>
To: Tejun Heo <tj@...nel.org>
Cc: Jeff Garzik <jgarzik@...ox.com>, linux-ide@...r.kernel.org,
Linux Kernel <linux-kernel@...r.kernel.org>,
Kevin Cernekee <cernekee@...il.com>,
Lin Ming <ming.m.lin@...el.com>,
Norbert Preining <preining@...ic.at>,
"Srivatsa S . Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>,
Valdis Kletnieks <valdis.kletnieks@...edu>,
"Rafael J . Wysocki" <rjw@...k.pl>
Subject: Re: [PATCH 1/3] ahci: add AHCI_HFLAG_STRICT_SPEC host flag
On Mon, Feb 20, 2012 at 1:23 PM, Tejun Heo <tj@...nel.org> wrote:
> On Mon, Feb 20, 2012 at 01:16:27PM -0800, Brian Norris wrote:
>> On Mon, Feb 20, 2012 at 12:51 PM, Tejun Heo <tj@...nel.org> wrote:
>> > Overall the patchset looks good but
>> >
>> > On Mon, Feb 20, 2012 at 12:09:21PM -0800, Brian Norris wrote:
>> >> + AHCI_HFLAG_STRICT_SPEC = (1 << 15), /* strict AHCI spec */
>> >
>> > can you please use something more specific? e.g. something like
>> > SKIP_ENGINE_ON_PORT_START and then explain what the flag is about in
>> > the comment?
>>
>> So you want AHCI_HFLAG_SKIP_ENGINE_ON_PORT_START? That seems
>> excessively long... how about AHCI_HFLAG_DELAY_ENGINE? (since it
>> pushes the start engine call back to the error-handling stage)
>
> Ooh, yeah, that seems better. I'm fine with any name which ties it to
> engine behavior on port start.
OK. I'll wait a bit for other comments, then send a v2 series with
AHCI_HFLAG_DELAY_ENGINE.
Brian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists