From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Ingo Oeser <ioe-lkml@rameria.de>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata queue updated
Date: Mon, 30 Jan 2006 10:01:27 -0500 [thread overview]
Message-ID: <43DE2A47.2030607@pobox.com> (raw)
In-Reply-To: <43DDBA71.6040402@gmail.com>
Tejun Heo wrote:
> Ingo Oeser wrote:
>
>> Hi Jeff,
>>
>>
>> On Saturday 28 January 2006 19:25, Jeff Garzik wrote:
>>
>>> Testing and merge point in Tejun's flood of patches :) The patch
>>> below is against current linux-2.6.git.
>>
>>
>> These "function(unsigned int *classes)" style functions in
>> "libata-core.c" worry me somewhat. Esp. that sometimes you have one
>> class,
>> sometimes two.
>> This looks like a bug waiting to happen for me.
>>
>> Could we somehow get a
>> struct ata_classes {
>> unsigned int master;
>> unsigned int slave;
>> }
>>
>> here (or similiar), before this is in used everywhere?
>>
>> Usage would be function(struct ata_classes *classes) then.
>>
>
> Hello,
>
> I object. Using array is intentional. Slave aware controllers (PATA /
> ata_piix) will use [0..1], most SATA controllers will use only [0], and
> PM aware ones will use [0..15]. The intention was requiring low level
> drivers of only what they know and normalize them in the core layer.
Yep, that's fine.
We don't need to be writing code for the case where somebody doesn't
know the C language.
Jeff
prev parent reply other threads:[~2006-01-30 15:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-28 18:25 [PATCH] libata queue updated 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 15:01 ` Jeff Garzik [this message]
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=43DE2A47.2030607@pobox.com \
--to=jgarzik@pobox.com \
--cc=htejun@gmail.com \
--cc=ioe-lkml@rameria.de \
--cc=linux-ide@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).