From: David Miller <davem@davemloft.net>
To: mrv@mojatatu.com
Cc: jhs@mojatatu.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 1/1] veth: tweak creation of veth device
Date: Thu, 12 Oct 2017 10:19:54 -0700 (PDT) [thread overview]
Message-ID: <20171012.101954.1416857673514626860.davem@davemloft.net> (raw)
In-Reply-To: <85tvz4wbtq.fsf@mojatatu.com>
From: Roman Mashak <mrv@mojatatu.com>
Date: Thu, 12 Oct 2017 12:49:37 -0400
> IMO, neither of these solutions seem reasonable.
I think the current behavior is reasonable. The user is given tools,
one of which does dynamic allocation of names, and the user must simply
take that into consideration.
prev parent reply other threads:[~2017-10-12 17:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 20:08 [PATCH net-next 1/1] veth: tweak creation of veth device Roman Mashak
2017-10-11 22:17 ` David Miller
2017-10-12 16:49 ` Roman Mashak
2017-10-12 17:19 ` 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=20171012.101954.1416857673514626860.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=mrv@mojatatu.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).