All of lore.kernel.org
 help / color / mirror / Atom feed
From: Elias Oltmanns <eo@nebensachen.de>
To: Tejun Heo <tj@kernel.org>
Cc: Jeff Garzik <jeff@garzik.org>,
	IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: [PATCH #upstream-fixes 2/4] libata: beef up iterators
Date: Mon, 27 Oct 2008 12:58:19 +0100	[thread overview]
Message-ID: <874p2ytfl0.fsf@denkblock.local> (raw)
In-Reply-To: <49059531.8030903@kernel.org> (Tejun Heo's message of "Mon, 27 Oct 2008 19:17:21 +0900")

Tejun Heo <tj@kernel.org> wrote:
> Elias Oltmanns wrote:
>> Tejun Heo <tj@kernel.org> wrote:
>
>>> Hello,
>>>
>>> Elias Oltmanns wrote:
>>>>> -		ata_port_for_each_link(link, ap) {
>>>>> -			ata_link_for_each_dev(dev, link)
>>>>> +		ata_for_each_link(link, ap, EDGE) {
>>>>> +			ata_for_each_dev(dev, link, ALL)
>>>> Where did these short forms (EDGE, ALL) spring from? Does this code even
>>>> compile?
>>> +#define ata_for_each_link(link, ap, mode) \
>>> +	for ((link) = ata_link_next(NULL, (ap), ATA_LITER_##mode); (link); \
>>> +	     (link) = ata_link_next((link), (ap), ATA_LITER_##mode))
>>> +
>>> +#define ata_for_each_dev(dev, link, mode) \
>>> +	for ((dev) = ata_dev_next(NULL, (link), ATA_DITER_##mode); (dev); \
>>> +	     (dev) = ata_dev_next((dev), (link), ATA_DITER_##mode))
>> 
>> Sorry, I should have been more explicit. I was referring to EDGE and ALL
>> as opposed to ATA_LITER_EDGE and ATA_DITER_ALL. Unless I've missed
>> something, the former aren't defined anywhere in your patch.
>
> I seriously can't be more explicit.  Please take a shower and read my
> reply again, especially, the "ATA_[LD]ITER_##mode" part.  :-)

Oh dear, I really need to drop that idea that a macro does what I think
it does. Sorry for the noise.

Regards,

Elias

  reply	other threads:[~2008-10-27 11:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-26  6:50 [PATCH #upstream-fixes 1/4] libata: fix device iteration bugs Tejun Heo
2008-10-26  6:51 ` [PATCH #upstream-fixes 2/4] libata: beef up iterators Tejun Heo
2008-10-26  6:51   ` [PATCH #upstream-fixes 3/4] libata: when restoring SControl during detach do the PMP links first Tejun Heo
2008-10-26  6:52     ` [PATCH #upstream-fixes 4/4] libata: perform port detach in EH Tejun Heo
2008-10-28  4:02       ` Jeff Garzik
2008-10-26 14:31   ` [PATCH #upstream-fixes 2/4] libata: beef up iterators Elias Oltmanns
2008-10-27  9:06     ` Tejun Heo
2008-10-27  9:39       ` Elias Oltmanns
2008-10-27 10:17         ` Tejun Heo
2008-10-27 11:58           ` Elias Oltmanns [this message]
2008-10-28  4:01   ` Jeff Garzik
2008-10-30  1:25     ` Mark Lord
2008-10-30  1:58       ` Jeff Garzik
2008-10-26 10:47 ` [PATCH #upstream-fixes 1/4] libata: fix device iteration bugs Sergei Shtylyov
2008-10-27  9:07   ` Tejun Heo
2008-10-27 10:59     ` [PATCH #upstream-fixes 1/4 UPDATED] " Tejun Heo
2008-10-28  3: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=874p2ytfl0.fsf@denkblock.local \
    --to=eo@nebensachen.de \
    --cc=jeff@garzik.org \
    --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.