From: Harvey Harrison <harvey.harrison@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: oh crap... (re: %p6)
Date: Wed, 29 Oct 2008 10:24:42 -0700 [thread overview]
Message-ID: <1225301082.5688.24.camel@brick> (raw)
In-Reply-To: <1225294760.5269.301.camel@localhost>
On Wed, 2008-10-29 at 08:39 -0700, Joe Perches wrote:
> On Wed, 2008-10-29 at 07:55 -0700, Harvey Harrison wrote:
> > On Wed, 2008-10-29 at 01:54 -0700, David Miller wrote:
> > > I think we'll need to revert all of this or find some fix soon. GCC
> > > warns about %p with a '#' flag modifier it seems :-(
> > >
> > > net/ipv6/ip6_flowlabel.c: In function 'ip6fl_seq_show':
> > > net/ipv6/ip6_flowlabel.c:707: warning: '#' flag used with '%p' printf format
> >
> > The easiest would be to pick a separate modifier for the raw case. Or
> > revert the removal of NIP6_SEQFMT, I'll shoot you a patch shortly,
> > any preference in what modifier should be used?
>
> I'd prefer something visual that represents "no colon".
>
> Maybe %p6-:
Putting a modifier after the format specifier seems a little strange to me. But
I'm not sure if I can think of something that's too much better, currently I
was thinking of:
%pI6, %pi6
%pI6 would act just like %p6
%pi6 would act just like %#p6
Eventually %pI4 could be added as well. Which would print out the dot-separated
format.
Either that or add a %px<bytes> that prints out raw hex for the number
of <bytes>, so %p6 would stay and %#p6 would become %px16. While this
is a bit uglier, it could be useful to others elsewhere in-kernel,
perhaps limited to 16 bytes or so.
Dave, I'll wait for your $0.02 before sending in a patch, but I have
both of the above implemented.
Harvey
next prev parent reply other threads:[~2008-10-29 17:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 8:54 oh crap... (re: %p6) David Miller
2008-10-29 14:55 ` Harvey Harrison
2008-10-29 15:39 ` Joe Perches
2008-10-29 17:24 ` Harvey Harrison [this message]
2008-10-29 18:16 ` Joe Perches
2008-10-29 18:21 ` Harvey Harrison
2008-10-29 18:32 ` oh crap David Miller
2008-10-29 18:31 ` David Miller
2008-10-29 19:13 ` Joe Perches
2008-10-29 18:28 ` David Miller
2008-10-29 18:31 ` Harvey Harrison
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=1225301082.5688.24.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=davem@davemloft.net \
--cc=joe@perches.com \
--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).