linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: akpm@osdl.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata/pata_it821x: Improve handling of poorly compatible emulations
Date: Tue, 30 Oct 2007 09:39:16 -0400	[thread overview]
Message-ID: <47273404.40802@garzik.org> (raw)
In-Reply-To: <20071030133350.687a5360@the-village.bc.nu>

Alan Cox wrote:
>>> The other IT821x change is a bit ugly, we slightly abuse the cable type
>>> hook to fiddle with the identify data for the devices. We could add a new
>>> hook for this but as we have only one offender and no more seeming likely
>>> it seems better to keep libata-core clean.
>>>
>>> Please let this sit in -mm briefly, just in case the relaxed checking
>>> breaks some other emulated interface.
>>>
>>> Signed-off-by: Alan Cox <alan@redhat.com>
>> Two questions:
>>
>> 1) should I queue for 2.6.24-rc?
> 
> Can we leave it once cycle in -mm and aim for 2.6.25-rc. There is a tiny
> possibility we will find someone who finds slave returning 0 produces a
> ghost drive or decode problem. Probably paranoia.

into #for-testing it goes


>> 2) why is ->dev_config() insufficient?
> 
> It is called (I think correctly) after we have performed identify
> dependant actions including HPA sizing.

hmmmm.  It certainly seems like we should have a hook that permits 
touching up dev->id[] before we go through all the actions based on 
IDENTIFY DEVICE results.

It sounds like such a hook would be more appropriate here...  can you 
think of any other situation or driver that could make use of a 
pre-dev-config hook?

	Jeff



  reply	other threads:[~2007-10-30 13:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-25 13:21 [PATCH] libata/pata_it821x: Improve handling of poorly compatible emulations Alan Cox
2007-10-25 20:11 ` Andrew Morton
2007-10-25 22:34   ` Alan Cox
2007-10-30 13:27 ` Jeff Garzik
2007-10-30 13:33   ` Alan Cox
2007-10-30 13:39     ` Jeff Garzik [this message]
2007-10-30 13:43       ` Alan Cox
2007-10-30 13:57 ` Jeff Garzik

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=47273404.40802@garzik.org \
    --to=jeff@garzik.org \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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).