From: Jakub Kicinski <kuba@kernel.org>
To: Ronald Wahl <rwahl@gmx.de>
Cc: Ronald Wahl <ronald.wahl@raritan.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Ben Dooks <ben.dooks@codethink.co.uk>,
Tristram Ha <Tristram.Ha@microchip.com>,
netdev@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net v2] net: ks8851: Fix TX stall caused by TX buffer overrun
Date: Tue, 12 Dec 2023 16:14:48 -0800 [thread overview]
Message-ID: <20231212161448.3ae3cb91@kernel.org> (raw)
In-Reply-To: <20231212191632.197656-1-rwahl@gmx.de>
On Tue, 12 Dec 2023 20:16:32 +0100 Ronald Wahl wrote:
> struct work_struct rxctrl_work;
>
> struct sk_buff_head txq;
> + unsigned int queued_len;
This new field is missing a kdoc
--
pw-bot: cr
next prev parent reply other threads:[~2023-12-13 0:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 19:16 [PATCH net v2] net: ks8851: Fix TX stall caused by TX buffer overrun Ronald Wahl
2023-12-13 0:14 ` Jakub Kicinski [this message]
2023-12-13 16:29 ` Simon Horman
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=20231212161448.3ae3cb91@kernel.org \
--to=kuba@kernel.org \
--cc=Tristram.Ha@microchip.com \
--cc=ben.dooks@codethink.co.uk \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ronald.wahl@raritan.com \
--cc=rwahl@gmx.de \
--cc=stable@vger.kernel.org \
/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).