From: Vinicius Costa Gomes <vinicius.gomes@intel.com>
To: Victor Nogueira <victor@mojatatu.com>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, jhs@mojatatu.com, xiyou.wangcong@gmail.com,
jiri@resnulli.us, stephen@networkplumber.org
Cc: netdev@vger.kernel.org, kernel@mojatatu.com
Subject: Re: [PATCH net-next 0/3] net: sched: Fill in missing MODULE_DESCRIPTIONs for net/sched
Date: Fri, 27 Oct 2023 12:42:00 -0700 [thread overview]
Message-ID: <87fs1vrgxj.fsf@intel.com> (raw)
In-Reply-To: <20231027155045.46291-1-victor@mojatatu.com>
Victor Nogueira <victor@mojatatu.com> writes:
> W=1 builds now warn if module is built without a MODULE_DESCRIPTION().
>
> Fill in the missing MODULE_DESCRIPTIONs for net/sched
>
> Victor Nogueira (3):
> net: sched: Fill in MODULE_DESCRIPTION for act_gate
The most optional of comments: missing "missing", just for consistency
with the rest of the series. Totally fine to ignore.
Reviewed-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
Cheers,
--
Vinicius
next prev parent reply other threads:[~2023-10-27 19:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 15:50 [PATCH net-next 0/3] net: sched: Fill in missing MODULE_DESCRIPTIONs for net/sched Victor Nogueira
2023-10-27 15:50 ` [PATCH net-next 1/3] net: sched: Fill in MODULE_DESCRIPTION for act_gate Victor Nogueira
2023-10-27 15:50 ` [PATCH net-next 2/3] net: sched: Fill in missing MODULE_DESCRIPTION for classifiers Victor Nogueira
2023-10-27 15:50 ` [PATCH net-next 3/3] net: sched: Fill in missing MODULE_DESCRIPTION for qdiscs Victor Nogueira
2023-10-27 19:42 ` Vinicius Costa Gomes [this message]
2023-11-02 5:10 ` [PATCH net-next 0/3] net: sched: Fill in missing MODULE_DESCRIPTIONs for net/sched 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=87fs1vrgxj.fsf@intel.com \
--to=vinicius.gomes@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kernel@mojatatu.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stephen@networkplumber.org \
--cc=victor@mojatatu.com \
--cc=xiyou.wangcong@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).