[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0334480f-1545-455b-8d5f-0f7a804ad186@web.de>
Date: Tue, 7 May 2024 09:30:16 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Dan Carpenter <dan.carpenter@...aro.org>,
Duoming Zhou <duoming@....edu.cn>, linux-hams@...r.kernel.org,
netdev@...r.kernel.org, kernel-janitors@...r.kernel.org
Cc: "David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>,
Jörg Reuter <jreuter@...na.de>,
Paolo Abeni <pabeni@...hat.com>, LKML <linux-kernel@...r.kernel.org>,
Lars Kellogg-Stedman <lars@...bit.com>, Simon Horman <horms@...nel.org>
Subject: Re: [PATCH RESEND net v4 0/4] ax25: Fix issues of ax25_dev and
net_device
…
> You can see the former discussion in the following link:
> https://lore.kernel.org/netdev/20240501060218.32898-1-duoming@zju.edu.cn/
…
Does this change approach represent another subsequent patch version
instead of a “RESEND”?
How do you think about to improve patch changelogs accordingly?
Regards,
Markus
Powered by blists - more mailing lists