From: Paolo Abeni <pabeni@redhat.com>
To: Wan Jiabing <wanjiabing@vivo.com>,
Mat Martineau <mathew.j.martineau@linux.intel.com>,
Matthieu Baerts <matthieu.baerts@tessares.net>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, mptcp@lists.linux.dev,
linux-kernel@vger.kernel.org
Cc: kael_w@yeah.net
Subject: Re: [PATCH] [v3] mptcp: Fix duplicated argument in protocol.h
Date: Wed, 01 Sep 2021 10:13:45 +0200 [thread overview]
Message-ID: <0b030119a755fb246a617f3ab30c7664d4f95323.camel@redhat.com> (raw)
In-Reply-To: <20210901031932.7734-1-wanjiabing@vivo.com>
Hello,
On Wed, 2021-09-01 at 11:19 +0800, Wan Jiabing wrote:
> Fix the following coccicheck warning:
> ./net/mptcp/protocol.h:36:50-73: duplicated argument to & or |
>
> The OPTION_MPTCP_MPJ_SYNACK here is duplicate.
> Here should be OPTION_MPTCP_MPJ_ACK.
>
> Fixes: 74c7dfbee3e18 ("mptcp: consolidate in_opt sub-options fields in a bitmask")
> Signed-off-by: Wan Jiabing <wanjiabing@vivo.com>
Not sure what happen to my previous reply, most probably PEBKAC, sorry.
WRT this patch, note that the dup is harmless, as in the input path we
always use the mask and not the individual bit - vice versa in the
output path. Still the cleanup is worthy and patch LGTM.
Acked-by: Paolo Abeni <pabeni@redhat.com>
next prev parent reply other threads:[~2021-09-01 8:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 3:19 [PATCH] [v3] mptcp: Fix duplicated argument in protocol.h Wan Jiabing
2021-09-01 7:59 ` Paolo Abeni
2021-09-01 7:59 ` Paolo Abeni
2021-09-01 8:13 ` Paolo Abeni [this message]
2021-09-01 8:13 ` Paolo Abeni
2021-09-01 8:27 ` Matthieu Baerts
2021-09-01 12:00 ` patchwork-bot+netdevbpf
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=0b030119a755fb246a617f3ab30c7664d4f95323.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=kael_w@yeah.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathew.j.martineau@linux.intel.com \
--cc=matthieu.baerts@tessares.net \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=wanjiabing@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.