From: David Miller <davem@davemloft.net>
To: adobriyan@gmail.com
Cc: netdev@vger.kernel.org, gaofeng@cn.fujitsu.com
Subject: Re: [PATCH] net: proc: revert proc_net_fops_create/proc_net_remove removal
Date: Fri, 08 Mar 2013 12:46:38 -0500 (EST) [thread overview]
Message-ID: <20130308.124638.857825798968866326.davem@davemloft.net> (raw)
In-Reply-To: <20130308135635.GA1078@p183.telecom.by>
From: Alexey Dobriyan <adobriyan@gmail.com>
Date: Fri, 8 Mar 2013 16:56:35 +0300
> Revert the following patches:
I'm not going back and forth again on this, you guys need to fight it
out.
I personally thought the removal was fine, and the extra interfaces
were just clutter. Justifying it just to hide init_net.proc_net is
a scarecrow at best.
prev parent reply other threads:[~2013-03-08 17:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 13:56 [PATCH] net: proc: revert proc_net_fops_create/proc_net_remove removal Alexey Dobriyan
2013-03-08 17:46 ` 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=20130308.124638.857825798968866326.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=adobriyan@gmail.com \
--cc=gaofeng@cn.fujitsu.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).