From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <tj@kernel.org>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
David Milburn <dmilburn@redhat.com>
Subject: Re: [PATCH UPDATED #upstream] ahci: misc cleanups for EM stuff
Date: Wed, 20 May 2009 16:12:05 -0400 [thread overview]
Message-ID: <4A146415.8020903@garzik.org> (raw)
In-Reply-To: <4A08D795.70102@kernel.org>
Tejun Heo wrote:
> Make the following EM related cleanups.
>
> * Use msleep(1) instead of udelay(100) and reduce retry count to 5.
>
> * s/MAX_SLOTS/EM_MAX_SLOTS/, s/MAX_RETRY/EM_MAX_RETRY/
>
> * Make EM constants enums as suggested by Jeff.
>
> Signed-off-by: Tejun Heo <tj@kernel.org>
> Acked-by: David Milburn <dmilburn@redhat.com>
> ---
> drivers/ata/ahci.c | 18 ++++++++++--------
> 1 file changed, 10 insertions(+), 8 deletions(-)
applied
prev parent reply other threads:[~2009-05-20 20:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 23:42 [PATCH #upstream] ahci: misc cleanups for EM stuff Tejun Heo
2009-04-28 14:40 ` David Milburn
2009-05-11 18:13 ` Jeff Garzik
2009-05-12 1:57 ` [PATCH UPDATED " Tejun Heo
2009-05-20 20:12 ` 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=4A146415.8020903@garzik.org \
--to=jeff@garzik.org \
--cc=dmilburn@redhat.com \
--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 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).