From: Rene Herman <rene.herman@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH] lib/iomap.c:bad_io_access() -- print 0x hex prefix
Date: Sat, 15 Sep 2007 19:49:24 +0200 [thread overview]
Message-ID: <46EC1B24.1010600@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 61 bytes --]
Hi Andrew.
Trivial -- be explicit about printing hex.
Rene
[-- Attachment #2: bad_io_access-hex.diff --]
[-- Type: text/plain, Size: 404 bytes --]
diff --git a/lib/iomap.c b/lib/iomap.c
index a57d262..5dfcbde 100644
--- a/lib/iomap.c
+++ b/lib/iomap.c
@@ -40,7 +40,7 @@ static void bad_io_access(unsigned long port, const char *access)
static int count = 10;
if (count) {
count--;
- printk(KERN_ERR "Bad IO access at port %lx (%s)\n", port, access);
+ printk(KERN_ERR "Bad IO access at port %#lx (%s)\n", port, access);
WARN_ON(1);
}
}
reply other threads:[~2007-09-15 17:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=46EC1B24.1010600@gmail.com \
--to=rene.herman@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@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).