public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Huang Ying <ying.huang@intel.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	Len Brown <lenb@kernel.org>
Subject: Re: [PATCH] ACPI, APEI, Print resource errors in conventional format
Date: Tue, 30 Aug 2011 08:41:38 +0800	[thread overview]
Message-ID: <4E5C31C2.90607@intel.com> (raw)
In-Reply-To: <CAErSpo5tKqKtUKmcq1S81YABXunFY5VW81iWDYsv9v5HeLAVGg@mail.gmail.com>

On 08/29/2011 10:08 PM, Bjorn Helgaas wrote:
> On Sun, Aug 28, 2011 at 6:49 PM, Huang Ying <ying.huang@intel.com> wrote:
>> On 08/27/2011 01:10 AM, Bjorn Helgaas wrote:
>>> Use the normal %pR-like format for MMIO and I/O port ranges.
>>>
>>> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
>>> ---
>>>  drivers/acpi/apei/apei-base.c |    8 ++++----
>>>  1 files changed, 4 insertions(+), 4 deletions(-)
>>>
>>> diff --git a/drivers/acpi/apei/apei-base.c b/drivers/acpi/apei/apei-base.c
>>> index 8041248..8bd5f1a 100644
>>> --- a/drivers/acpi/apei/apei-base.c
>>> +++ b/drivers/acpi/apei/apei-base.c
>>> @@ -460,9 +460,9 @@ int apei_resources_request(struct apei_resources *resources,
>>>                                      desc);
>>>               if (!r) {
>>>                       pr_err(APEI_PFX
>>> -             "Can not request iomem region <%016llx-%016llx> for GARs.\n",
>>> +             "Can not request [mem %#010llx-%#010llx] for %s registers\n",
>>
>> Why %#010llx instead of %#016llx?
> 
> Because %#010llx is effectively what we use for %pR.  Two characters
> for "0x", then eight for the value.  IMHO, sixteen uninterrupted hex
> characters is too hard to read.

That is reasonable. Thanks.

Acked-by: Huang Ying <ying.huang@intel.com>

Best Regards,
Huang Ying

  reply	other threads:[~2011-08-30  0:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-26 17:10 [PATCH] ACPI, APEI, Print resource errors in conventional format Bjorn Helgaas
2011-08-29  0:49 ` Huang Ying
2011-08-29 14:08   ` Bjorn Helgaas
2011-08-30  0:41     ` Huang Ying [this message]
2011-08-30 16:32       ` Bjorn Helgaas

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=4E5C31C2.90607@intel.com \
    --to=ying.huang@intel.com \
    --cc=bhelgaas@google.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@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