From: Phil Sutter <phil@nwl.cc>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: David Miller <davem@davemloft.net>,
Xin Long <lucien.xin@gmail.com>,
Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH 1/3] sctp: Export struct sctp_info to userspace
Date: Mon, 1 Aug 2016 15:36:06 +0200 [thread overview]
Message-ID: <20160801133606.GB10443@orbyte.nwl.cc> (raw)
In-Reply-To: <20160731141824.30785573@xeon-e3>
Hi Stephen,
On Sun, Jul 31, 2016 at 02:18:24PM -0700, Stephen Hemminger wrote:
> On Fri, 29 Jul 2016 18:59:38 +0200
> Phil Sutter <phil@nwl.cc> wrote:
>
> > This is required to correctly interpret INET_DIAG_INFO messages exported
> > by sctp_diag module.
> >
> > Signed-off-by: Phil Sutter <phil@nwl.cc>
>
> You need to add sctp.h to include/linux/Kbuild to get it exported correctly
Thanks for the heads-up! Luckily it is in there already.
Cheers, Phil
next prev parent reply other threads:[~2016-08-01 13:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 16:59 [PATCH 0/3] sctp_diag: A bunch of fixes for upcoming 'ss' support Phil Sutter
2016-07-29 16:59 ` [PATCH 1/3] sctp: Export struct sctp_info to userspace Phil Sutter
2016-07-31 21:18 ` Stephen Hemminger
2016-08-01 13:36 ` Phil Sutter [this message]
2016-07-29 16:59 ` [PATCH 2/3] sctp_diag: export timer value only if it is active Phil Sutter
2016-07-29 20:51 ` Marcelo Ricardo Leitner
2016-07-30 13:25 ` Xin Long
2016-07-30 13:33 ` Marcelo Ricardo Leitner
2016-07-30 17:59 ` Phil Sutter
2016-07-31 15:57 ` Xin Long
2016-08-03 19:28 ` Phil Sutter
2016-08-03 19:46 ` Marcelo Ricardo Leitner
2016-08-03 20:15 ` Phil Sutter
2016-07-29 16:59 ` [PATCH 3/3] sctp_diag: Respect ss adding TCPF_CLOSE to idiag_states Phil Sutter
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=20160801133606.GB10443@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=davem@davemloft.net \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).