From: Jakub Kicinski <kuba@kernel.org>
To: Pavan Kumar Linga <pavan.kumar.linga@intel.com>
Cc: netdev@vger.kernel.org, linux-doc@vger.kernel.org,
corbet@lwn.net, emil.s.tantilov@intel.com,
joshua.a.hay@intel.com, sridhar.samudrala@intel.com,
alan.brady@intel.com, madhu.chittim@intel.com,
jesse.brandeburg@intel.com, anthony.l.nguyen@intel.com,
willemb@google.com, decot@google.com
Subject: Re: [PATCH net-next 0/2] Fix invalid kernel-doc warnings
Date: Fri, 11 Aug 2023 18:07:55 -0700 [thread overview]
Message-ID: <20230811180755.14efaf73@kernel.org> (raw)
In-Reply-To: <20230812002549.36286-1-pavan.kumar.linga@intel.com>
On Fri, 11 Aug 2023 17:25:47 -0700 Pavan Kumar Linga wrote:
> kernel-doc reports invalid warnings on IDPF driver patch series [1]
> that is submitted for review. This patch series fixes those warnings.
>
> [1]: https://lore.kernel.org/netdev/20230808003416.3805142-1-anthony.l.nguyen@intel.com/
> ---
> These fixes are needed for the IDPF driver patch series to have
> a clean CI. So targeting the series to net-next instead of
> linux-docs.
Neat, thanks for these.
Jon, no strong preference on the tree here. I'll confirm these resolve
the issues in Pavan's driver when applying it, there's no hard
requirement for the kdoc patches to be in net-next at that point.
prev parent reply other threads:[~2023-08-12 1:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 0:25 [PATCH net-next 0/2] Fix invalid kernel-doc warnings Pavan Kumar Linga
2023-08-12 0:25 ` [PATCH net-next 1/2] scripts: kernel-doc: parse DEFINE_DMA_UNMAP_[ADDR|LEN] Pavan Kumar Linga
2023-08-12 4:47 ` Randy Dunlap
2023-08-14 17:18 ` Linga, Pavan Kumar
2023-08-12 0:25 ` [PATCH net-next 2/2] scripts: kernel-doc: fix macro handling in enums Pavan Kumar Linga
2023-08-12 1:07 ` Jakub Kicinski [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=20230811180755.14efaf73@kernel.org \
--to=kuba@kernel.org \
--cc=alan.brady@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=corbet@lwn.net \
--cc=decot@google.com \
--cc=emil.s.tantilov@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=joshua.a.hay@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=madhu.chittim@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pavan.kumar.linga@intel.com \
--cc=sridhar.samudrala@intel.com \
--cc=willemb@google.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).