From: Kevin Corry <kevcorry@us.ibm.com>
To: root@chaos.analogic.com, Riley Williams <Riley@Williams.Name>
Cc: viro@parcelfarce.linux.theplanet.co.uk,
Bodo Rzany <bodo@rzany.de>,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: is there small mistake in lib/vsprintf.c of kernel 2.4.20 ?
Date: Fri, 2 May 2003 13:23:50 -0500 [thread overview]
Message-ID: <200305021323.50125.kevcorry@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0305021305250.9707@chaos>
On Friday 02 May 2003 12:15, Richard B. Johnson wrote:
> Kevin Corry <kevcorry@us.ibm.com>, submitted a patch which breaks
> already working code in an aparent attempt to fix the leading
> "0x" problem.
It is not a patch to fix the leading "0x" problem. It is a patch to fix
scanning of hex numbers which do *not* start with "0x". Hex numbers starting
with "0x" will already scan correctly. Like I said before, try scanning "fe"
as a hex number, and watch scanf return an error. Like I also said before,
this same patch has been in 2.5 for quite a while, so I fail to see why it
shouldn't also be applied to 2.4, unless we are specifically trying to
maintain different behavior for scanf between the two kernel versions.
--
Kevin Corry
kevcorry@us.ibm.com
http://evms.sourceforge.net/
next prev parent reply other threads:[~2003-05-02 18:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BKEGKPICNAKILKJKMHCAKEBLCKAA.Riley@Williams.Name>
2003-05-02 17:15 ` Richard B. Johnson
2003-05-02 18:23 ` Kevin Corry [this message]
2003-05-02 9:06 Bodo Rzany
2003-05-02 9:08 ` viro
2003-05-02 9:42 ` Bodo Rzany
2003-05-02 9:50 ` viro
2003-05-02 15:03 ` Kevin Corry
2003-05-02 15:27 ` Richard B. Johnson
2003-05-02 16:52 ` Jonathan Lundell
2003-05-02 17:20 ` Richard B. Johnson
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=200305021323.50125.kevcorry@us.ibm.com \
--to=kevcorry@us.ibm.com \
--cc=Riley@Williams.Name \
--cc=bodo@rzany.de \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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
all inboxes | Powered by JetHome®