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: [PATCH RESEND net v4 1/4] ax25: Use kernel universal linked list to implement ax25_dev_list
Date: Tue, 7 May 2024 09:52:54 +0200 [thread overview]
Message-ID: <04bb96a0-0561-4583-88e1-d98253e0808a@web.de> (raw)
In-Reply-To: <5022fa6a280c3fa852bf3724149251c41ee8303f.1715062582.git.duoming@zju.edu.cn>
> … that need to notice:
I suggest to improve such a wording.
> [1] We should add a check to judge whether …
Are imperative wordings more desirable for improved change descriptions?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.9-rc7#n94
Regards,
Markus
next prev parent reply other threads:[~2024-05-07 7:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 6:21 [PATCH RESEND net v4 0/4] ax25: Fix issues of ax25_dev and net_device Duoming Zhou
2024-05-07 6:21 ` [PATCH RESEND net v4 1/4] ax25: Use kernel universal linked list to implement ax25_dev_list Duoming Zhou
2024-05-07 7:52 ` Markus Elfring [this message]
2024-05-07 6:21 ` [PATCH RESEND net v4 2/4] ax25: Fix reference count leak issues of ax25_dev Duoming Zhou
2024-05-07 6:21 ` [PATCH RESEND net v4 3/4] ax25: Fix reference count leak issues of net_device Duoming Zhou
2024-05-07 7:30 ` [PATCH RESEND net v4 0/4] ax25: Fix issues of ax25_dev and net_device Markus Elfring
2024-05-07 7:48 ` duoming
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=04bb96a0-0561-4583-88e1-d98253e0808a@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).