From: Daniel Borkmann <daniel@iogearbox.net>
To: Joe Perches <joe@perches.com>, "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux@rasmusvillemoes.dk, andriy.shevchenko@linux.intel.com,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] vsprintf: do not append unset Scope ID to IPv6
Date: Wed, 03 Feb 2016 23:09:16 +0100 [thread overview]
Message-ID: <56B27A8C.3040302@iogearbox.net> (raw)
In-Reply-To: <1454536072.7291.133.camel@perches.com>
On 02/03/2016 10:47 PM, Joe Perches wrote:
> On Wed, 2016-02-03 at 22:14 +0100, Jason A. Donenfeld wrote:
>> The idea here is to be able to printk a sockaddr_in6, and have it show
>> something that looks like what the user would naturally pass to
>> getaddrinfo(3), which is entirely complete.
>>
>> However, I could be convinced that this kind of behavior belongs in
>> it's own flag. Maybe I'll cook up a flag for that instead.
>
> I think that'd be best.
Agreed.
> Maybe using something like %pISG for this that
> would optionally show these flow and scope values
> only when non-zero.
>
> Something like:
Looks good to me, having this as a single generic option seems
even cleaner.
Thanks!
next prev parent reply other threads:[~2016-02-03 22:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 10:41 Jason A. Donenfeld
2016-02-03 12:13 ` [PATCH] vsprintf: flowinfo in IPv6 is optional too Jason A. Donenfeld
2016-02-03 17:56 ` IRe: " Joe Perches
2016-02-03 21:09 ` Jason A. Donenfeld
2016-02-03 21:13 ` Andy Shevchenko
2016-02-03 21:13 ` IRe: " Daniel Borkmann
2016-02-03 21:15 ` Jason A. Donenfeld
2016-02-03 21:07 ` [PATCH] vsprintf: do not append unset Scope ID to IPv6 Daniel Borkmann
2016-02-03 21:14 ` Jason A. Donenfeld
2016-02-03 21:47 ` Joe Perches
2016-02-03 22:09 ` Daniel Borkmann [this message]
2016-02-03 22:42 ` Jason A. Donenfeld
2016-02-03 22:53 ` [PATCH] vsprintf: automatic parameters for %pIS via 'a' Jason A. Donenfeld
2016-02-03 23:05 ` Joe Perches
2016-02-03 23:25 ` Jason A. Donenfeld
2016-02-03 23:29 ` [PATCH v2] " Jason A. Donenfeld
2016-02-03 23:37 ` Joe Perches
2016-02-04 0:59 ` [PATCH v3] " Jason A. Donenfeld
2016-02-05 0:06 ` [PATCH v2] " Rasmus Villemoes
2016-02-05 13:06 ` Jason A. Donenfeld
2016-02-05 13:37 ` [PATCH] " Jason A. Donenfeld
2016-02-05 13:39 ` [PATCH v4] " Jason A. Donenfeld
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=56B27A8C.3040302@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=Jason@zx2c4.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
/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
Powered by JetHome