From: Pavan Kumar Linga <pavan.kumar.linga@intel.com>
To: netdev@vger.kernel.org, kuba@kernel.org
Cc: 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,
Pavan Kumar Linga <pavan.kumar.linga@intel.com>
Subject: [PATCH net-next 0/2] Fix invalid kernel-doc warnings
Date: Fri, 11 Aug 2023 17:25:47 -0700 [thread overview]
Message-ID: <20230812002549.36286-1-pavan.kumar.linga@intel.com> (raw)
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.
---
Pavan Kumar Linga (2):
scripts: kernel-doc: parse DEFINE_DMA_UNMAP_[ADDR|LEN]
scripts: kernel-doc: fix macro handling in enums
scripts/kernel-doc | 5 +++++
1 file changed, 5 insertions(+)
--
2.38.1
next reply other threads:[~2023-08-12 0:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 0:25 Pavan Kumar Linga [this message]
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 ` [PATCH net-next 0/2] Fix invalid kernel-doc warnings Jakub Kicinski
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=20230812002549.36286-1-pavan.kumar.linga@intel.com \
--to=pavan.kumar.linga@intel.com \
--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=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=madhu.chittim@intel.com \
--cc=netdev@vger.kernel.org \
--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 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.