From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: s/ap->id/ap->print_id/g
Date: Tue, 20 Feb 2007 11:39:46 -0500 [thread overview]
Message-ID: <45DB2452.9070603@garzik.org> (raw)
In-Reply-To: <20070220160651.GS1625@htj.dyndns.org>
Tejun Heo wrote:
> ata_port has two different id fields - id and port_no. id is
> system-wide 1-based unique id for the port while port_no is 0-based
> host-wide port number. The former is primarily used to identify the
> ATA port to the user in printk messages while the latter is used in
> various places in libata core and LLDs to index the port inside the
> host.
>
> The two fields feel quite similar and sometimes ap->id is used in
> place of ap->port_no, which is very difficult to spot. This patch
> renames ap->id to ap->print_id to reduce the possibility of such bugs.
>
> Some printk messages are adjusted such that id string (ata%u[.%u])
> isn't printed twice and/or to use ata_*_printk() instead of hardcoded
> id format.
>
> Signed-off-by: Tejun Heo <htejun@gmail.com>
applied
prev parent reply other threads:[~2007-02-20 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 16:06 [PATCH] libata: s/ap->id/ap->print_id/g Tejun Heo
2007-02-20 16:39 ` 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=45DB2452.9070603@garzik.org \
--to=jeff@garzik.org \
--cc=htejun@gmail.com \
--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).