Re: [PATCH RESEND net v4 0/4] ax25: Fix issues of ax25_dev and net_device

[PATCH RESEND net v4 0/4] ax25: Fix issues of ax25_dev and net_device · Duoming Zhou <hidden> · 2024-05-07
[PATCH RESEND net v4 1/4] ax25: Use kernel universal linked list to implement ax25_dev_list · Duoming Zhou <hidden> · 2024-05-07
Re: [PATCH RESEND net v4 1/4] ax25: Use kernel universal linked list to implement ax25_dev_list · Markus Elfring <hidden> · 2024-05-07
[PATCH RESEND net v4 2/4] ax25: Fix reference count leak issues of ax25_dev · Duoming Zhou <hidden> · 2024-05-07
[PATCH RESEND net v4 3/4] ax25: Fix reference count leak issues of net_device · Duoming Zhou <hidden> · 2024-05-07
Re: [PATCH RESEND net v4 0/4] ax25: Fix issues of ax25_dev and net_device · Markus Elfring <hidden> · 2024-05-07
Re: [PATCH RESEND net v4 0/4] ax25: Fix issues of ax25_dev and net_device · <hidden> · 2024-05-07

From: <hidden>
Date: 2024-05-07 07:49:07
Also in: kernel-janitors, linux-hams, lkml

On Date: Tue, 7 May 2024 09:30:16 +0200 Markus Elfring wrote:

Does this change approach represent another subsequent patch version
instead of a “RESEND”?

How do you think about to improve patch changelogs accordingly?

Thank you for your reply and suggestions, I have already sent the v5:
https://patchwork.kernel.org/project/netdevbpf/list/?series=851052

Best regards,
Duoming Zhou

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help