From: Jeff Garzik <jeff@garzik.org>
To: Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] use ATA_TAG_INTERNAL in ata_tag_internal()
Date: Fri, 04 Apr 2008 03:56:03 -0400 [thread overview]
Message-ID: <47F5DF13.1040301@garzik.org> (raw)
In-Reply-To: <20080228214313.70129569.yoichi_yuasa@tripeaks.co.jp>
Yoichi Yuasa wrote:
> It should be ATA_TAG_INTERNAL.
>
> Signed-off-by: Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp>
>
> diff -pruN -X /home/yuasa/Memo/dontdiff linux-orig/include/linux/libata.h linux/include/linux/libata.h
> --- linux-orig/include/linux/libata.h 2008-02-28 13:29:13.659279943 +0900
> +++ linux/include/linux/libata.h 2008-02-28 13:29:48.221249519 +0900
> @@ -1123,7 +1123,7 @@ static inline unsigned int ata_tag_valid
>
> static inline unsigned int ata_tag_internal(unsigned int tag)
> {
> - return tag == ATA_MAX_QUEUE - 1;
> + return tag == ATA_TAG_INTERNAL;
> }
applied
prev parent reply other threads:[~2008-04-04 7:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 12:43 [PATCH] use ATA_TAG_INTERNAL in ata_tag_internal() Yoichi Yuasa
2008-03-06 8:36 ` Tejun Heo
2008-04-04 7:56 ` 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=47F5DF13.1040301@garzik.org \
--to=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=yoichi_yuasa@tripeaks.co.jp \
/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).