From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>, Joe Perches <joe@perches.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux@rasmusvillemoes.dk, LKML <linux-kernel@vger.kernel.org>,
dborkman@redhat.com
Subject: Re: [PATCH] vsprintf: flowinfo in IPv6 is optional too
Date: Wed, 03 Feb 2016 23:13:20 +0200 [thread overview]
Message-ID: <1454534000.31169.64.camel@linux.intel.com> (raw)
In-Reply-To: <CAHmME9qHgQN2aDNi+R5HqmP0ehtAL8wdEJQvy78m3raaWruMRQ@mail.gmail.com>
On Wed, 2016-02-03 at 22:09 +0100, Jason A. Donenfeld wrote:
> On Wed, Feb 3, 2016 at 6:56 PM, Joe Perches <joe@perches.com> wrote:
> > Why does this matter at all?
>
> Because I want to printk a sockaddr_in6, and have the most complete
> yet valid and standard representation I can. Displaying a /0 when
> there is no flow is confusing, ugly, and unhelpful, not to mention it
> doesn't accurately reflect what's happening. A flowlabel of zero
> means
> no flowlabel.
So, where do you want to put your result? dmesg? User-space application
via sysfs?
Seems like here is discussion debug vs. release version of printed data
in the kernel.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2016-02-03 21:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 10:41 [PATCH] vsprintf: do not append unset Scope ID to IPv6 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 [this message]
2016-02-03 21:13 ` 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
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=1454534000.31169.64.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Jason@zx2c4.com \
--cc=akpm@linux-foundation.org \
--cc=dborkman@redhat.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;
as well as URLs for NNTP newsgroup(s).