From: Chuck Ebbert <cebbert@redhat.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-ide@vger.kernel.org
Subject: Re: [PATCH #upstream 1/2] libata: relocate forcing PIO0 on reset
Date: Tue, 30 Oct 2007 17:25:26 -0400 [thread overview]
Message-ID: <4727A146.7080701@redhat.com> (raw)
In-Reply-To: <20071029074109.GO11853@htj.dyndns.org>
On 10/29/2007 03:41 AM, Tejun Heo wrote:
> retry:
> + ata_link_for_each_dev(dev, &ap->link) {
How do I backport these loops to 2.6.23?
I see something like this in the old code:
for (i=0; i < ATA_MAX_DEVICES; i++) {
dev = &ap->device[i];
if (!ata_dev_enabled(dev))
continue;
do_something(dev);
}
next prev parent reply other threads:[~2007-10-30 21:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 7:41 [PATCH #upstream 1/2] libata: relocate forcing PIO0 on reset Tejun Heo
2007-10-29 7:45 ` [PATCH #upstream 2/2] libata: no need to speed down if already at PIO0 Tejun Heo
2007-10-29 8:35 ` Alan Cox
2007-10-29 10:22 ` [PATCH #upstream 1/2] libata: relocate forcing PIO0 on reset Jeff Garzik
2007-10-30 21:25 ` Chuck Ebbert [this message]
2007-10-31 0:13 ` Tejun Heo
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=4727A146.7080701@redhat.com \
--to=cebbert@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--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).