From: David Miller <davem@davemloft.net>
To: colona@arista.com
Cc: eric.dumazet@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] tcp: add mode parameter to tcp_proc_register
Date: Fri, 23 Jun 2017 00:27:58 -0400 (EDT) [thread overview]
Message-ID: <20170623.002758.1129050083018969879.davem@davemloft.net> (raw)
In-Reply-To: <20170623014028.28257-1-colona@arista.com>
From: Ivan Delalande <colona@arista.com>
Date: Thu, 22 Jun 2017 18:40:27 -0700
> This will be used to create a proc file that regular users cannot read.
>
> Signed-off-by: Ivan Delalande <colona@arista.com>
/proc is deprecated.
Export this information via inet_diag.
prev parent reply other threads:[~2017-06-23 4:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 1:40 [PATCH 1/2] tcp: add mode parameter to tcp_proc_register Ivan Delalande
2017-06-23 1:40 ` [PATCH 2/2] tcp: md5: export all configured signature keys in /proc/net Ivan Delalande
2017-06-25 1:38 ` kbuild test robot
2017-06-23 4:27 ` 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=20170623.002758.1129050083018969879.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=colona@arista.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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).