From: Phil Sutter <phil@nwl.cc>
To: Xin Long <lucien.xin@gmail.com>
Cc: network dev <netdev@vger.kernel.org>,
linux-sctp@vger.kernel.org,
Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
Vlad Yasevich <vyasevich@gmail.com>,
daniel@iogearbox.net, davem@davemloft.net,
eric.dumazet@gmail.com
Subject: Re: [PATCHv3 net-next 1/6] sctp: add sctp_info dump api for sctp_diag
Date: Thu, 14 Apr 2016 11:13:18 +0200 [thread overview]
Message-ID: <20160414091318.GC3715@orbyte.nwl.cc> (raw)
In-Reply-To: <cd6bf9c2696f125a74491e1f82b77a30bb1005dd.1460618169.git.lucien.xin@gmail.com>
Hi Xin Long,
On Thu, Apr 14, 2016 at 03:35:30PM +0800, Xin Long wrote:
> sctp_diag will dump some important details of sctp's assoc or ep, we use
> sctp_info to describe them, sctp_get_sctp_info to get them, and export
> it to sctp_diag.ko.
>
> v2->v3:
> - we will not use list_for_each_safe in sctp_get_sctp_info, cause
> all the callers of it will use lock_sock.
>
> - fix the holes in struct sctp_info with __reserved* field.
> because sctp_diag is a new feature, and sctp_info is just for now,
> it may be changed in the future.
>
> Signed-off-by: Xin Long <lucien.xin@gmail.com>
You're mixing commit message and changelog here (and in the following
patches, too). In order to not make the changelog part of the commit
message, you should separate it with three dashes, just like
git-format-patch does with the diff stat. So please reformat the patches
to meet this pattern:
------------------8<--------------------
Commit message here
Signed-off-by
---
Changelog here
---
diff stat added by Git
diff --git a/foo/bar.c b/foo/bar.c
...
------------------8<--------------------
If you think some of the changelog's info should be preserved, better
integrate it into the message itself.
Cheers, Phil
next prev parent reply other threads:[~2016-04-14 9:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 7:35 [PATCHv3 net-next 0/6] sctp: support sctp_diag in kernel Xin Long
2016-04-14 7:35 ` [PATCHv3 net-next 1/6] sctp: add sctp_info dump api for sctp_diag Xin Long
2016-04-14 7:35 ` [PATCHv3 net-next 2/6] sctp: export some apis or variables for sctp_diag and reuse some for proc Xin Long
2016-04-14 7:35 ` [PATCHv3 net-next 3/6] sctp: export some functions for sctp_diag in inet_diag Xin Long
2016-04-14 7:35 ` [PATCHv3 net-next 4/6] sctp: add the sctp_diag.c file Xin Long
2016-04-14 7:35 ` [PATCHv3 net-next 5/6] sctp: merge the seq_start/next/exits in remaddrs and assocs Xin Long
2016-04-14 7:35 ` [PATCHv3 net-next 6/6] sctp: fix some rhashtable functions using in sctp proc/diag Xin Long
2016-04-14 12:41 ` [PATCHv3 net-next 4/6] sctp: add the sctp_diag.c file Jakub Sitnicki
2016-04-14 9:13 ` Phil Sutter [this message]
2016-04-15 21:28 ` [PATCHv3 net-next 1/6] sctp: add sctp_info dump api for sctp_diag David Miller
2016-04-18 10:18 ` Phil Sutter
2016-04-15 21:30 ` [PATCHv3 net-next 0/6] sctp: support sctp_diag in kernel David Miller
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=20160414091318.GC3715@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=vyasevich@gmail.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).