From: Jakub Kicinski <kuba@kernel.org>
To: Shannon Nelson <shannon.nelson@amd.com>
Cc: <andrew+netdev@lunn.ch>, <brett.creeley@amd.com>,
<davem@davemloft.net>, <edumazet@google.com>, <pabeni@redhat.com>,
<michal.swiatkowski@linux.intel.com>, <horms@kernel.org>,
<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>
Subject: Re: [PATCH v2 net 2/5] pds_core: remove extra name description
Date: Mon, 14 Apr 2025 17:36:10 -0700 [thread overview]
Message-ID: <20250414173610.5dc3be9d@kernel.org> (raw)
In-Reply-To: <20250411003209.44053-3-shannon.nelson@amd.com>
On Thu, 10 Apr 2025 17:32:06 -0700 Shannon Nelson wrote:
> Fix the kernel-doc complaint
> include/linux/pds/pds_adminq.h:481: warning: Excess struct member 'name' description in 'pds_core_lif_getattr_comp'
>
> Fixes: 45d76f492938 ("pds_core: set up device and adminq")
How is this a bug fix? The warnings are only generated on W=1 builds.
Please be more considerate of folks maintaining stable trees. There's
no need to waste their time with patches like this.
--
pw-bot: cr
next prev parent reply other threads:[~2025-04-15 0:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 0:32 [PATCH v2 net 0/5] pds_core: updates and fixes Shannon Nelson
2025-04-11 0:32 ` [PATCH v2 net 1/5] pds_core: Prevent possible adminq overflow/stuck condition Shannon Nelson
2025-04-11 18:59 ` Simon Horman
2025-04-11 0:32 ` [PATCH v2 net 2/5] pds_core: remove extra name description Shannon Nelson
2025-04-15 0:36 ` Jakub Kicinski [this message]
2025-04-15 23:15 ` Nelson, Shannon
2025-04-11 0:32 ` [PATCH v2 net 3/5] pds_core: handle unsupported PDS_CORE_CMD_FW_CONTROL result Shannon Nelson
2025-04-11 19:00 ` Simon Horman
2025-04-11 0:32 ` [PATCH v2 net 4/5] pds_core: Remove unnecessary check in pds_client_adminq_cmd() Shannon Nelson
2025-04-11 0:32 ` [PATCH v2 net 5/5] pds_core: make wait_context part of q_info Shannon Nelson
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=20250414173610.5dc3be9d@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=brett.creeley@amd.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.swiatkowski@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shannon.nelson@amd.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.