From: Bodo Eggert <7eggert@gmx.de>
To: Vegard Nossum <vegard.nossum@gmail.com>,
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] FAT: Fix printk format strings.
Date: Thu, 11 Oct 2007 12:58:09 +0200 [thread overview]
Message-ID: <E1Ifvk1-0000o5-VO@be1.lrz> (raw)
In-Reply-To: 9d2nm-1SV-11@gated-at.bofh.it
Vegard Nossum <vegard.nossum@gmail.com> wrote:
> This makes sure printk format strings contain no more than a single
> line.
> printk(KERN_WARNING
> - "FAT: Did not find valid FSINFO signature.\n"
> + "FAT: Did not find valid FSINFO signature.\n");
> + printk(KERN_WARNING
> " Found signature1 0x%08x signature2 0x%08x"
> " (sector = %lu)\n",
What about something like
"Fat32: Invalid FSINFO signatures 0x%08x, 0x%08x; expected 0x%08x, 0x%08\n" ?
or
"Fat32: Invalid FSINFO signatures 0x%08x, 0x%08x\n" ?
--
bus error. passengers dumped.
Friß, Spammer: GYwky2@xvGdf6v.7eggert.dyndns.org
fD8g@tfnrkqq.7eggert.dyndns.org VpcWe@h5ib4vef.7eggert.dyndns.org
next parent reply other threads:[~2007-10-11 10:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9d2nm-1SV-11@gated-at.bofh.it>
2007-10-11 10:58 ` Bodo Eggert [this message]
2007-10-11 17:28 ` [PATCH] FAT: Fix printk format strings OGAWA Hirofumi
2007-10-11 9:17 Vegard Nossum
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=E1Ifvk1-0000o5-VO@be1.lrz \
--to=7eggert@gmx.de \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=vegard.nossum@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox