From: Jakub Kicinski <kuba@kernel.org>
To: Hao Lan <lanhao@huawei.com>
Cc: <lipeng321@huawei.com>, <shenjian15@huawei.com>,
<linyunsheng@huawei.com>, <liuyonglong@huawei.com>,
<chenhao418@huawei.com>, <wangjie125@huawei.com>,
<huangguangbin2@huawei.com>, <yisen.zhuang@huawei.com>,
<salil.mehta@huawei.com>, <davem@davemloft.net>,
<edumazet@google.com>, <pabeni@redhat.com>,
<netdev@vger.kernel.org>, <xiaojiantao1@h-partners.com>
Subject: Re: [PATCH net-next 0/2] net: hns3: Cleanup for static warnings.
Date: Mon, 14 Nov 2022 18:59:26 -0800 [thread overview]
Message-ID: <20221114185926.23148f9e@kernel.org> (raw)
In-Reply-To: <20221112081749.56229-1-lanhao@huawei.com>
On Sat, 12 Nov 2022 16:17:47 +0800 Hao Lan wrote:
> Most static warnings are mainly about:
> Patch #1: fix hns3 driver header file not self-contained issue.
> Patch #2: add complete parentheses for some macros.
You need to say what static checker was used.
I think it's documented in the "researcher guidelines" doc.
In case patch 2 was based on a warning from checkpatch please
drop it from the series, we don't take checkpatch-based cleanups.
next prev parent reply other threads:[~2022-11-15 3:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-12 8:17 [PATCH net-next 0/2] net: hns3: Cleanup for static warnings Hao Lan
2022-11-12 8:17 ` [PATCH net-next 1/2] net: hns3: fix hns3 driver header file not self-contained issue Hao Lan
2022-11-12 8:17 ` [PATCH net-next 2/2] net: hns3: add complete parentheses for some macros Hao Lan
2022-11-15 2:59 ` Jakub Kicinski [this message]
2022-11-15 13:29 ` [PATCH net-next 0/2] net: hns3: Cleanup for static warnings Hao Lan
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=20221114185926.23148f9e@kernel.org \
--to=kuba@kernel.org \
--cc=chenhao418@huawei.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=huangguangbin2@huawei.com \
--cc=lanhao@huawei.com \
--cc=linyunsheng@huawei.com \
--cc=lipeng321@huawei.com \
--cc=liuyonglong@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=salil.mehta@huawei.com \
--cc=shenjian15@huawei.com \
--cc=wangjie125@huawei.com \
--cc=xiaojiantao1@h-partners.com \
--cc=yisen.zhuang@huawei.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.