From: Harvey Harrison <harvey.harrison@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: David Miller <davem@davemloft.net>,
linux-netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH 1/4] printk: add %I4, %I6, %i4, %i6 format specifiers
Date: Thu, 30 Oct 2008 16:59:59 -0700 [thread overview]
Message-ID: <1225411199.5574.3.camel@brick> (raw)
In-Reply-To: <1225398538.1288.9.camel@localhost>
On Thu, 2008-10-30 at 13:28 -0700, Joe Perches wrote:
> On Wed, 2008-10-29 at 11:35 -0700, Harvey Harrison wrote:
> > return ip6_addr_string(buf, end, ptr, field_width, precision, flags);
> > + case 'i':
> > + flags |= SPECIAL;
> > + /* Fallthrough */
> > + case 'I':
> > + if (fmt[1] == '6')
> > + return ip6_addr_string(buf, end, ptr, field_width, precision, flags);
> > + if (fmt[1] == '4')
> > + return ip4_addr_string(buf, end, ptr, field_width, precision, flags);
> > + flags &= ~SPECIAL;
> > + break;
> > }
> > flags |= SMALL;
> > if (field_width == -1) {
>
> Hi Harvey.
>
> I was thinking about extending %p<foo> to support
> struct task_struct * and noticed this code isn't
> really correct.
>
> SPECIAL should be cleared from flags only when *fmt
> is 'i' not 'I' and SPECIAL wasn't previously set.
>
SPECIAL is set when # is used with the p modifier...which warns as we've
already seen. So the only way to set special in the %p case is to use
i. Instead of having an if() I just unconditionally clear it (perhaps
unnecessarily). Mind you, we only get here if you pass in %p[iI][not 4 or 6]
Cheers,
Harvey
prev parent reply other threads:[~2008-10-31 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 18:35 [PATCH 1/4] printk: add %I4, %I6, %i4, %i6 format specifiers Harvey Harrison
2008-10-29 20:04 ` David Miller
2008-10-30 20:28 ` Joe Perches
2008-10-30 23:59 ` Harvey Harrison [this message]
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=1225411199.5574.3.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.