From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <htejun@gmail.com>
Cc: "Eric D. Mudama" <edmudama@gmail.com>, linux-ide@vger.kernel.org
Subject: Re: [PATCH 1/1] libata: rearrange dmesg info to add full ATA revision
Date: Wed, 31 Jan 2007 04:16:25 -0500 [thread overview]
Message-ID: <45C05E69.8060208@garzik.org> (raw)
In-Reply-To: <45C020F7.7000305@gmail.com>
Tejun Heo wrote:
> [The previous replay mysteriously didn't include Eric in To:, sorry,
> quoting whole message here.]
>
> Tejun Heo wrote:
>> Hello, Eric.
>>
>> Eric D. Mudama wrote:
>>> Per Jeff's suggestion, this patch rearranges the info printed for ATA
>>> drives into dmesg to add the full ATA firmware revision and model
>>> information, while keeping the output to 2 lines.
>>>
>>> Signed-off-by: Eric D. Mudama <edmudama@gmail.com>
>> The patch is formatted and applies perfectly. I'm glad to see this
>> change. Just a few nits below.
>>
>>> char revbuf[7]; /* XYZ-99\0 */
>>> + char fwrevbuf[9];
>>> + char modelbuf[41];
>> Please use ATA_ID_FW_REV_LEN + 1 and ATA_ID_PROD_LEN + 1.
>
> This depends on to which version this patch applies. For
> #upstream-fixes (2.6.20-rc6), you have to use raw numbers as you did.
> For #upstream, there are above two constants to use. I think this patch
> is good for 2.6.20 as it's safe && will help us analyzing bug reports
> for 2.6.20. So, ignore this part of the comment.
We have time to revise. I only want to commit true bug fixes at this
point, to 2.6.20.
Jeff
next prev parent reply other threads:[~2007-01-31 9:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 2:10 [PATCH 1/1] libata: rearrange dmesg info to add full ATA revision Eric D. Mudama
2007-01-31 3:57 ` Tejun Heo
2007-01-31 4:54 ` Tejun Heo
2007-01-31 9:16 ` Jeff Garzik [this message]
2007-01-31 6:00 ` Eric D. Mudama
2007-01-31 15:23 ` Jeff Garzik
2007-02-07 0:42 ` Jeff Garzik
2007-02-07 2:31 ` Eric D. Mudama
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=45C05E69.8060208@garzik.org \
--to=jeff@garzik.org \
--cc=edmudama@gmail.com \
--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 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.