From: Joe Perches <joe@perches.com>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: David Miller <davem@davemloft.net>,
Johannes Berg <johannes@sipsolutions.net>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 3/5] net/ipv4, net/ipv6: use %#p6, %p6 format strings
Date: Mon, 27 Oct 2008 22:47:56 -0700 [thread overview]
Message-ID: <1225172877.5269.139.camel@localhost> (raw)
In-Reply-To: <1225172104.5526.28.camel@brick>
On Mon, 2008-10-27 at 22:35 -0700, Harvey Harrison wrote:
> I thought about this, and it will work if the one place that passes
> NIP6_FMT into sscanf gets changed at the same time. Otherwise,
> doing it in-place is probably safer.
Maybe sscanf should be updated to support these new %p<foo> types.
next prev parent reply other threads:[~2008-10-28 5:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 4:05 [RFC PATCH 3/5] net/ipv4, net/ipv6: use %#p6, %p6 format strings Harvey Harrison
2008-10-28 5:05 ` Joe Perches
2008-10-28 5:35 ` Harvey Harrison
2008-10-28 5:47 ` Joe Perches [this message]
2008-10-28 8:26 ` Johannes Berg
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=1225172877.5269.139.camel@localhost \
--to=joe@perches.com \
--cc=davem@davemloft.net \
--cc=harvey.harrison@gmail.com \
--cc=johannes@sipsolutions.net \
--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