From: Markus Elfring <Markus.Elfring@web.de>
To: Dan Carpenter <dan.carpenter@linaro.org>,
Duoming Zhou <duoming@zju.edu.cn>,
linux-hams@vger.kernel.org, netdev@vger.kernel.org,
kernel-janitors@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Jörg Reuter" <jreuter@yaina.de>,
"Paolo Abeni" <pabeni@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
"Lars Kellogg-Stedman" <lars@oddbit.com>,
"Simon Horman" <horms@kernel.org>
Subject: Re: [v2 2/2] ax25: fix potential reference counting leak in ax25_addr_ax25dev
Date: Fri, 3 May 2024 15:39:00 +0200 [thread overview]
Message-ID: <86a187fc-f5c1-4dd2-b04f-4bb645312778@web.de> (raw)
In-Reply-To: <e471ec93-6182-4af0-9584-a35e2680c66d@moroto.mountain>
> The commit message is fine as-is. Please stop nit-picking.
I dare to point recurring improvement possibilities out.
I became curious if the change acceptance will ever grow accordingly.
Regards,
Markus
next prev parent reply other threads:[~2024-05-03 13:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 23:36 [PATCH net v2 0/2] ax25: fix reference counting issue of ax25_dev Duoming Zhou
2024-05-02 23:36 ` [PATCH net v2 1/2] ax25: change kfree in ax25_dev_free to ax25_dev_free Duoming Zhou
2024-05-03 5:36 ` Markus Elfring
2024-05-03 11:33 ` Dan Carpenter
2024-05-02 23:36 ` [PATCH net v2 2/2] ax25: fix potential reference counting leak in ax25_addr_ax25dev Duoming Zhou
2024-05-03 7:30 ` Markus Elfring
2024-05-03 11:38 ` Dan Carpenter
2024-05-03 13:39 ` Markus Elfring [this message]
2024-05-03 5:10 ` [PATCH net v2 0/2] ax25: fix reference counting issue of ax25_dev Dan Carpenter
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=86a187fc-f5c1-4dd2-b04f-4bb645312778@web.de \
--to=markus.elfring@web.de \
--cc=dan.carpenter@linaro.org \
--cc=davem@davemloft.net \
--cc=duoming@zju.edu.cn \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jreuter@yaina.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=lars@oddbit.com \
--cc=linux-hams@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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
all inboxes | Powered by JetHome®