Re: [PATCH net-next v6 5/7] tun: Extract the vnet handling code

[PATCH net-next v6 0/7] tun: Unify vnet implementation · Akihiko Odaki <hidden> · 2025-02-07
[PATCH net-next v6 1/7] tun: Refactor CONFIG_TUN_VNET_CROSS_LE · Akihiko Odaki <hidden> · 2025-02-07
[PATCH net-next v6 2/7] tun: Keep hdr_len in tun_get_user() · Akihiko Odaki <hidden> · 2025-02-07
[PATCH net-next v6 3/7] tun: Decouple vnet from tun_struct · Akihiko Odaki <hidden> · 2025-02-07
[PATCH net-next v6 4/7] tun: Decouple vnet handling · Akihiko Odaki <hidden> · 2025-02-07
[PATCH net-next v6 5/7] tun: Extract the vnet handling code · Akihiko Odaki <hidden> · 2025-02-07
Re: [PATCH net-next v6 5/7] tun: Extract the vnet handling code · Willem de Bruijn <willemdebruijn.kernel@gmail.com> · 2025-02-07
[PATCH net-next v6 6/7] tap: Keep hdr_len in tap_get_user() · Akihiko Odaki <hidden> · 2025-02-07
Re: [PATCH net-next v6 6/7] tap: Keep hdr_len in tap_get_user() · Willem de Bruijn <willemdebruijn.kernel@gmail.com> · 2025-02-07
[PATCH net-next v6 7/7] tap: Use tun's vnet-related code · Akihiko Odaki <hidden> · 2025-02-07
Re: [PATCH net-next v6 0/7] tun: Unify vnet implementation · patchwork-bot+netdevbpf@kernel.org · 2025-02-11

From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Date: 2025-02-07 17:19:47
Also in: kvm, linux-doc, linux-kselftest, lkml, virtualization

Akihiko Odaki wrote:

The vnet handling code will be reused by tap.

Functions are renamed to ensure that their names contain "vnet" to
clarify that they are part of the decoupled vnet handling code.

Signed-off-by: Akihiko Odaki <redacted>

Reviewed-by: Willem de Bruijn <willemb@google.com>

`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