From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: Joe Perches <joe@perches.com>, Borislav Petkov <bp@alien8.de>,
bhelgaas@google.com
Cc: LKML <linux-kernel@vger.kernel.org>, Borislav Petkov <bp@suse.de>,
Anton Vorontsov <anton@enomsg.org>,
Colin Cross <ccross@android.com>,
Kees Cook <keescook@chromium.org>,
Tony Luck <tony.luck@intel.com>, Len Brown <lenb@kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-acpi@vger.kernel.org, "Huang, Ying" <ying.huang@intel.com>
Subject: Re: [PATCH] APEI/ERST: Fix error message formatting
Date: Thu, 25 Jul 2013 16:53:20 +0530 [thread overview]
Message-ID: <51F10AA8.2050901@linux.vnet.ibm.com> (raw)
In-Reply-To: <1374686598.18818.18.camel@joe-AO722>
On 07/24/2013 10:53 PM, Joe Perches wrote:
> On Wed, 2013-07-24 at 22:43 +0530, Naveen N. Rao wrote:
>> On 2013/07/22 11:01PM, Borislav Petkov wrote:
>>> From: Borislav Petkov <bp@suse.de>
>>>
>>> [ 5.525861] ERST: Can not request iomem region <0x c7eff000-0x c7f00000> for ERST.
>>>
>>> This needs to have leading zeroes. Make it so.
>
> Why does it need leading zeros?
>
>> While looking at this, I noticed that we seem to be using varying field
>> widths in our APEI code:
>> - einj.c has two instances using %#010llx.
>> - apei-base.c uses widths of 10 (4 bytes) and 6 (2 bytes).
>>
>> Not sure if these are intentional and those fields truly aren't 64-bit
>> (as suggested by the usage of long long int).
>
> I suggest using "0x%llx" everywhere unless there's a
> compelling reason like columnar alignment for them.
I think that might be better. I see that these changes were done in
commit 46b91e37. Copying Bjorn Helgaas.
On 07/24/2013 11:40 PM, Borislav Petkov wrote:
> That's an interesting question but I think you're better fitted to
> answer it - I try to avoid the APEI spec as much as possible.
>
> :-)
>
Oh, I've hardly scratched the surface w.r.t APEI. I think I'll let the
experts comment on this :)
Thanks,
Naveen
next prev parent reply other threads:[~2013-07-25 11:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 21:01 [PATCH] APEI/ERST: Fix error message formatting Borislav Petkov
2013-07-22 21:24 ` Kees Cook
2013-07-24 17:13 ` Naveen N. Rao
2013-07-24 17:23 ` Joe Perches
2013-07-25 11:23 ` Naveen N. Rao [this message]
2013-07-25 17:32 ` Bjorn Helgaas
2013-07-29 13:58 ` Borislav Petkov
2013-07-29 14:28 ` Bjorn Helgaas
2013-07-29 14:40 ` Borislav Petkov
2013-07-29 14:50 ` Bjorn Helgaas
2013-07-29 15:22 ` Borislav Petkov
2013-07-29 15:32 ` Joe Perches
2013-07-29 16:12 ` Bjorn Helgaas
2013-07-31 9:23 ` Borislav Petkov
2013-07-31 9:57 ` Naveen N. Rao
2013-07-31 9:46 ` Naveen N. Rao
2013-07-31 18:00 ` Bjorn Helgaas
2013-08-01 10:10 ` Naveen N. Rao
2013-07-24 18:10 ` Borislav Petkov
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=51F10AA8.2050901@linux.vnet.ibm.com \
--to=naveen.n.rao@linux.vnet.ibm.com \
--cc=anton@enomsg.org \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=ccross@android.com \
--cc=joe@perches.com \
--cc=keescook@chromium.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=tony.luck@intel.com \
--cc=ying.huang@intel.com \
/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.