From: Ingo Oeser <ioe-lkml@rameria.de>
To: linux-kernel@vger.kernel.org
Cc: Tejun <htejun@gmail.com>
Subject: Re: [PATCH] libata queue updated
Date: Tue, 31 Jan 2006 03:33:56 +0100 [thread overview]
Message-ID: <200601310333.57518.ioe-lkml@rameria.de> (raw)
In-Reply-To: <43DEA978.8000706@gmail.com>
Hi Tejun,
On Tuesday 31 January 2006 01:04, Tejun wrote:
> Ingo Oeser wrote:
> > What about putting the information directly into "ap->device[INDEX].class"
> > in the sole caller (ata_drive_probe_reset) so far?
> >
>
> Not altering ->class directly in lldd driver is one major point of this
> whole patchset such that higher level driving logic has a say on whether
> a device is online or not, not the low level driver. Primarily this is
> useful for sharing low-level codes with hot plugging / EH but it's also
> possible to retry some of the operations during probing in limited cases.
Ok, with this argument, I finally get it. Now I know why you do it this
way. You let the lld driver suggest a class for it's devices and verify
these suggestions by high level code.
The only way to get to this classification data is by resetting the ATA
device.
It might be technically possible to set ->class directly and
fix it up in high level logic, as needed.
Your explicit design decision was NOT to do this but to put this
suggestions from low level driver into a temporary on stack structure
from the higher level API.
And since the maintainer is happy already, I couldn't care less.
Thanks for your patience :-)
Regards
Ingo Oeser
next prev parent reply other threads:[~2006-01-31 2:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-28 18:25 Jeff Garzik
2006-01-29 16:11 ` Ingo Oeser
2006-01-30 7:04 ` Tejun Heo
2006-01-30 8:36 ` Ingo Oeser
2006-01-30 8:44 ` Tejun Heo
2006-01-30 19:02 ` Ingo Oeser
2006-01-31 0:04 ` Tejun
2006-01-31 2:33 ` Ingo Oeser [this message]
2006-01-31 2:41 ` Tejun
2006-01-30 15:01 ` 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=200601310333.57518.ioe-lkml@rameria.de \
--to=ioe-lkml@rameria.de \
--cc=htejun@gmail.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®