From: Simon Horman <simon.horman@netronome.com>
To: Wang Qing <wangqing@vivo.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Jozsef Kadlecsik <kadlec@netfilter.org>,
Florian Westphal <fw@strlen.de>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net/netfilter: fix a typo for nf_conntrack_proto_dccp.c
Date: Wed, 9 Sep 2020 18:34:08 +0200 [thread overview]
Message-ID: <20200909163407.GB28336@netronome.com> (raw)
In-Reply-To: <1599653567-27147-1-git-send-email-wangqing@vivo.com>
Hi Wang,
On Wed, Sep 09, 2020 at 08:12:44PM +0800, Wang Qing wrote:
> Change the comment typo: "direcly" -> "directly".
>
> Signed-off-by: Wang Qing <wangqing@vivo.com>
git log tells me that the correct prefix for this patch
is "netfilter: conntrack:" rather than "net/netfilter:"
Probably this patch is targeted at nf-next and should include nf-next
in the subject like this: [PATCH nf-next] ...
> ---
> net/netfilter/nf_conntrack_proto_dccp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/netfilter/nf_conntrack_proto_dccp.c b/net/netfilter/nf_conntrack_proto_dccp.c
> index b3f4a33..d9bb0ce
> --- a/net/netfilter/nf_conntrack_proto_dccp.c
> +++ b/net/netfilter/nf_conntrack_proto_dccp.c
> @@ -340,7 +340,7 @@ dccp_state_table[CT_DCCP_ROLE_MAX + 1][DCCP_PKT_SYNCACK + 1][CT_DCCP_MAX + 1] =
> * sNO -> sIV No connection
> * sRQ -> sIV No connection
> * sRS -> sIV No connection
> - * sPO -> sOP -> sCG Move direcly to CLOSING
> + * sPO -> sOP -> sCG Move directly to CLOSING
> * sOP -> sCG Move to CLOSING
> * sCR -> sIV Close after CloseReq is invalid
> * sCG -> sCG Retransmit
> --
> 2.7.4
>
prev parent reply other threads:[~2020-09-09 16:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 12:12 [PATCH] net/netfilter: fix a typo for nf_conntrack_proto_dccp.c Wang Qing
2020-09-09 16:34 ` Simon Horman [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=20200909163407.GB28336@netronome.com \
--to=simon.horman@netronome.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=wangqing@vivo.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).