From: Joe Perches <joe@perches.com>
To: Aleksander Jan Bajkowski <olek2@wp.pl>,
davem@davemloft.net, kuba@kernel.org, rdunlap@infradead.org,
jgg@ziepe.ca, arnd@arndb.de, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: John Crispin <john@phrozen.org>
Subject: Re: [PATCH net-next] net: lantiq_etop: add blank line after declaration
Date: Sat, 08 Jan 2022 00:04:08 -0800 [thread overview]
Message-ID: <fc1bf93d92bb5b2f99c6c62745507cc22f3a7b2d.camel@perches.com> (raw)
In-Reply-To: <20211228220031.71576-1-olek2@wp.pl>
(adding John Crispin, the original submitter of this driver)
On Tue, 2021-12-28 at 23:00 +0100, Aleksander Jan Bajkowski wrote:
> This patch adds a missing line after the declaration and
> fixes the checkpatch warning:
>
> WARNING: Missing a blank line after declarations
> + int desc;
> + for (desc = 0; desc < LTQ_DESC_NUM; desc++)
>
> Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
[]
> diff --git a/drivers/net/ethernet/lantiq_etop.c b/drivers/net/ethernet/lantiq_etop.c
[]
> @@ -218,6 +218,7 @@ ltq_etop_free_channel(struct net_device *dev, struct ltq_etop_chan *ch)
> free_irq(ch->dma.irq, priv);
> if (IS_RX(ch->idx)) {
> int desc;
> +
> for (desc = 0; desc < LTQ_DESC_NUM; desc++)
> dev_kfree_skb_any(ch->skb[ch->dma.desc]);
> }
The change is innocuous and has already been applied but the code
doesn't seem to make sense.
Why is dev_kfree_skb_any called multiple times with the same argument?
Is there some missing logic here? Maybe a missing ++?
Something like:
for (desc = 0; desc < LTQ_DESC_NUM; desc++)
dev_kfree_skb_any(ch->skb[ch->dma.desc++]);
Dunno, but the current code seems wrong.
next prev parent reply other threads:[~2022-01-08 8:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-28 22:00 Aleksander Jan Bajkowski
2021-12-29 0:20 ` patchwork-bot+netdevbpf
2022-01-08 8:04 ` Joe Perches [this message]
2022-01-08 15:38 ` Aleksander Bajkowski
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=fc1bf93d92bb5b2f99c6c62745507cc22f3a7b2d.camel@perches.com \
--to=joe@perches.com \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=jgg@ziepe.ca \
--cc=john@phrozen.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olek2@wp.pl \
--cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®