[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHS8izNSO-4efu8x6OqxHdyuyqQgS_t6EDh3JjjC1k4R_Gtm2Q@mail.gmail.com>
Date: Mon, 27 Oct 2025 17:33:45 -0700
From: Mina Almasry <almasrymina@...gle.com>
To: Bobby Eshleman <bobbyeshleman@...il.com>
Cc: "David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, Simon Horman <horms@...nel.org>,
Kuniyuki Iwashima <kuniyu@...gle.com>, Willem de Bruijn <willemb@...gle.com>,
Neal Cardwell <ncardwell@...gle.com>, David Ahern <dsahern@...nel.org>,
Stanislav Fomichev <sdf@...ichev.me>, netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
Bobby Eshleman <bobbyeshleman@...a.com>
Subject: Re: [PATCH net-next v5 1/4] net: devmem: rename tx_vec to vec in
dmabuf binding
On Thu, Oct 23, 2025 at 2:00 PM Bobby Eshleman <bobbyeshleman@...il.com> wrote:
>
> From: Bobby Eshleman <bobbyeshleman@...a.com>
>
> Rename the 'tx_vec' field in struct net_devmem_dmabuf_binding to 'vec'.
> This field holds pointers to net_iov structures. The rename prepares for
> reusing 'vec' for both TX and RX directions.
>
> No functional change intended.
>
> Signed-off-by: Bobby Eshleman <bobbyeshleman@...a.com>
Looks like a straightforward name change,
Reviewed-by: Mina Almasry <almasrymina@...gle.com>
Powered by blists - more mailing lists