From: David Miller <davem@davemloft.net>
To: zhangshengju@cmss.chinamobile.com
Cc: netdev@vger.kernel.org, ezegomez@amazon.com
Subject: Re: [net-next] dummy: declare dummy devices as enumerated devices
Date: Mon, 18 Sep 2017 11:29:42 -0700 (PDT) [thread overview]
Message-ID: <20170918.112942.292129633205088909.davem@davemloft.net> (raw)
In-Reply-To: <1505179965-12117-1-git-send-email-zhangshengju@cmss.chinamobile.com>
From: Zhang Shengju <zhangshengju@cmss.chinamobile.com>
Date: Tue, 12 Sep 2017 09:32:45 +0800
> Dummy device name is enumerated by the kernel, let user space be aware
> of the naming scheme used by dummy devices:
> (visible in /sys/class/net/<iface>/name_assign_type).
>
> Signed-off-by: Zhang Shengju <zhangshengju@cmss.chinamobile.com>
Applied.
prev parent reply other threads:[~2017-09-18 18:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 1:32 [net-next] dummy: declare dummy devices as enumerated devices Zhang Shengju
2017-09-18 18:29 ` 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=20170918.112942.292129633205088909.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ezegomez@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=zhangshengju@cmss.chinamobile.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).