From: Simon Horman <horms@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: R SUNDAR <prosunofficial@gmail.com>,
jmaloy@redhat.com, ying.xue@windriver.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Removed inputq,namedq field description to prevent kernel doc warnings.
Date: Mon, 4 Mar 2024 17:32:50 +0000 [thread overview]
Message-ID: <20240304173250.GM403078@kernel.org> (raw)
In-Reply-To: <120c265e-dde5-454e-8e0b-72a1361912b6@infradead.org>
On Sun, Mar 03, 2024 at 08:41:56AM -0800, Randy Dunlap wrote:
> Hi,
>
> On 3/3/24 06:39, R SUNDAR wrote:
> > /net/tipc/node.c:150: warning: Excess struct member 'inputq' description in 'tipc_node'
> > /net/tipc/node.c:150: warning: Excess struct member 'namedq' description in 'tipc_node'
> >
> > Signed-off-by: R SUNDAR <prosunofficial@gmail.com>
>
> This is already fixed in linux-next and net-next, as was another one of your
> patches.
> I suggest that you focus more on the -next trees for such patch targets.
Yes, agreed. A similar patch was accepted in January.
Link: https://git.kernel.org/netdev/net-next/c/5ca1a5153a28
--
pw-bot: not-applicable
prev parent reply other threads:[~2024-03-04 17:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-03 14:39 [PATCH] Removed inputq,namedq field description to prevent kernel doc warnings R SUNDAR
2024-03-03 16:41 ` Randy Dunlap
2024-03-04 17:32 ` Simon Horman [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=20240304173250.GM403078@kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jmaloy@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=prosunofficial@gmail.com \
--cc=rdunlap@infradead.org \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=ying.xue@windriver.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).