From: David Miller <davem@davemloft.net>
To: lrichard@redhat.com
Cc: netdev@vger.kernel.org, nicolas.dichtel@6wind.com
Subject: Re: [PATCHi next] veth: advertise peer link relationship for both devices
Date: Sat, 11 Jun 2016 19:30:19 -0700 (PDT) [thread overview]
Message-ID: <20160611.193019.365613971876579784.davem@davemloft.net> (raw)
In-Reply-To: <489378018.52267492.1465697053847.JavaMail.zimbra@redhat.com>
From: Lance Richardson <lrichard@redhat.com>
Date: Sat, 11 Jun 2016 22:04:13 -0400 (EDT)
> I'll confess to not being super-happy with it myself, which is why I've
> been sitting on this patch for some time now. A hard NAK will help justify
> a "will not fix" to the reporter of this issue.
Since userspace can learn everything is needs to using the existing
notifications, there is no reason for this change, NACK.
prev parent reply other threads:[~2016-06-12 2:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 16:32 [PATCHi next] veth: advertise peer link relationship for both devices Lance Richardson
2016-06-11 22:43 ` David Miller
2016-06-12 2:04 ` Lance Richardson
2016-06-12 2:30 ` David Miller [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=20160611.193019.365613971876579784.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=lrichard@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
/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).