From: Joe Perches <joe@perches.com>
To: Daniel Borkmann <dborkman@redhat.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
linux-sctp@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 1/2] lib: vsprintf: add IPv4/v6 generic %p[Ii]S[pfs] format specifier
Date: Fri, 28 Jun 2013 08:44:49 -0700 [thread overview]
Message-ID: <1372434289.29380.6.camel@joe-AO722> (raw)
In-Reply-To: <1372421131-1672-2-git-send-email-dborkman@redhat.com>
On Fri, 2013-06-28 at 14:05 +0200, Daniel Borkmann wrote:
> In order to avoid making code that deals with printing both, IPv4 and
> IPv6 addresses, unnecessary complicated as for example ...
Thanks Daniel, seems sensible. Just trivial comments...
[]
> diff --git a/lib/vsprintf.c b/lib/vsprintf.c
[]
Should any other include other than net/addrconf be needed?
> +char *ip6_addr_string_sa(char *buf, char *end, const struct sockaddr_in6 *sa,
> + struct printf_spec spec, const char *fmt)
> +{
[]
> + char fmt6[2] = { fmt[0], '6'};
This looks odd to me. why not use a bool compressed
flag and identify this before the isalpha loop and not
have fmt6 at all?
> + u8 off = 0;
> +
> + fmt++;
> + while (isalpha(*++fmt)) {
> + switch (*fmt) {
> + case 'p':
> + have_p = true;
> + break;
> + case 'f':
> + have_f = true;
> + break;
> + case 's':
> + have_s = true;
> + break;
> + case 'c':
> + have_c = true;
> + break;
> + }
> + }
next prev parent reply other threads:[~2013-06-28 15:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 12:05 [PATCH net-next v3 0/2] Rework SCTP debugging framework Daniel Borkmann
2013-06-28 12:05 ` [PATCH net-next v3 1/2] lib: vsprintf: add IPv4/v6 generic %p[Ii]S[pfs] format specifier Daniel Borkmann
2013-06-28 15:44 ` Joe Perches [this message]
2013-06-28 15:53 ` Daniel Borkmann
2013-06-28 16:04 ` Joe Perches
2013-06-28 16:13 ` Daniel Borkmann
2013-06-28 16:06 ` Daniel Borkmann
2013-06-28 16:30 ` Joe Perches
2013-06-28 12:05 ` [PATCH net-next v3 2/2] net: sctp: rework debugging framework to use pr_debug and friends Daniel Borkmann
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=1372434289.29380.6.camel@joe-AO722 \
--to=joe@perches.com \
--cc=davem@davemloft.net \
--cc=dborkman@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@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).