From: Rasmus Villemoes <linux@rasmusvillemoes.dk>
To: Kashyap Desai <kashyap.desai@avagotech.com>
Cc: Sumit Saxena <sumit.saxena@avagotech.com>,
Uday Lingala <uday.lingala@avagotech.com>,
"James E.J. Bottomley" <JBottomley@parallels.com>,
"PDL,MEGARAIDLINUX" <megaraidlinux.pdl@avagotech.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Joe Perches <joe@perches.com>
Subject: Re: [PATCH] scsi: megaraid_sas: Prevent future %p disaster
Date: Tue, 12 May 2015 16:04:04 +0200 [thread overview]
Message-ID: <87iobx7uzv.fsf@rasmusvillemoes.dk> (raw)
In-Reply-To: <bb45ec6cfa94612741a2eb355d0de566@mail.gmail.com> (Kashyap Desai's message of "Tue, 10 Feb 2015 22:16:05 +0530")
On Tue, Feb 10 2015, Kashyap Desai <kashyap.desai@avagotech.com> wrote:
> Acked-by: Kashyap Desai <kashyap.desai@avagotech.com>
>
>> -----Original Message-----
>> From: Rasmus Villemoes [mailto:linux@rasmusvillemoes.dk]
>> Sent: Friday, February 06, 2015 8:04 PM
>> To: Kashyap Desai; Sumit Saxena; Uday Lingala; James E.J. Bottomley
>> Cc: Rasmus Villemoes; megaraidlinux.pdl@avagotech.com; linux-
>> scsi@vger.kernel.org; linux-kernel@vger.kernel.org
>> Subject: [PATCH] scsi: megaraid_sas: Prevent future %p disaster
>>
>> There is currently no %po format extension, so currently the letters
> "on" are
>> simply skipped and the pointer is printed as expected (while missing the
> word
>> on). However, it is probably only a matter of time before someone comes
> up
>> with a %po extension, at which point this is likely to fail
> spectacularly.
>>
>> Signed-off-by: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Any chance either this minimal fix or Joe's more thorough cleanup could
get applied? There's still no %po extension, but there's certainly a lot
of proposals for more %p extensions flying around LKML, so I still think
the "only a matter of time" holds.
Rasmus
next prev parent reply other threads:[~2015-05-12 14:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 14:33 [PATCH] scsi: megaraid_sas: Prevent future %p disaster Rasmus Villemoes
2015-02-10 16:46 ` Kashyap Desai
2015-02-10 16:55 ` Joe Perches
2015-02-10 18:38 ` Joe Perches
2015-05-12 14:04 ` Rasmus Villemoes [this message]
2015-05-12 14:52 ` Joe Perches
2015-05-12 15:01 ` Joe Perches
[not found] <OF651E5409.7FC1198E-ONC1257E49.0034C44E-C1257E49.0034D9A0@de.ibm.com>
2015-05-18 10:05 ` Ursula Braun
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=87iobx7uzv.fsf@rasmusvillemoes.dk \
--to=linux@rasmusvillemoes.dk \
--cc=JBottomley@parallels.com \
--cc=joe@perches.com \
--cc=kashyap.desai@avagotech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=megaraidlinux.pdl@avagotech.com \
--cc=sumit.saxena@avagotech.com \
--cc=uday.lingala@avagotech.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