From: Eddy Tao <taoyuan_eddy@hotmail.com>
To: Simon Horman <simon.horman@corigine.com>
Cc: netdev@vger.kernel.org, Pravin B Shelar <pshelar@ovn.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
dev@openvswitch.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v7 1/1] net:openvswitch:reduce cpu_used_mask memory
Date: Sat, 4 Feb 2023 22:47:06 +0800 [thread overview]
Message-ID: <OS3P286MB2295A2F3A8B58054ECD87D8CF5D49@OS3P286MB2295.JPNP286.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <Y95ddddYhqkR7b1o@corigine.com>
Hi, Simon:
Thank you for the time on the review.
and i looked into net folder and get various results
'net:', 'net: gre:', 'net: bridge:', 'net: thunderx', 'net: sock', 'net:
genetlink', and there is also examples as you suggested like 'devlink:'
similarly, in other folders i see similar inconsistency, mm folder is an
example.
I turned below links and did not find item regarding to the prefix
definition
Link: https://docs.kernel.org/process/maintainer-netdev.html
Link:
https://docs.kernel.org/process/submitting-patches.html#submittingpatches
Going through the git log in file net/openvswitch/flow.c, the 'net:
openvswitch: ' prefix were used in previous commits.
I think the fix contained 'net' keep the prefix from name collision and
better keeps it consistent with its neighbors in the same file
And yes, there should be a blank space after the colon, i miss it, will
update the revision, after we nail down the wording of the prefix.
Thanks
eddy
On 2023/2/4 21:28, Simon Horman wrote:
> nit: I think the correct prefix for the patch subject is 'openvswitch:'
> And there should be a space after the prefix.
>
> [PATCH net-next v8 1/1] openvswitch: reduce cpu_used_mask
prev parent reply other threads:[~2023-02-04 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 15:42 Eddy Tao
2023-02-04 13:28 ` Simon Horman
2023-02-04 14:47 ` Eddy Tao [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=OS3P286MB2295A2F3A8B58054ECD87D8CF5D49@OS3P286MB2295.JPNP286.PROD.OUTLOOK.COM \
--to=taoyuan_eddy@hotmail.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pshelar@ovn.org \
--cc=simon.horman@corigine.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
all inboxes | Powered by JetHome®