[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5c4ad938-eef4-4d6a-84e0-ffb10630fef9@linux.dev>
Date: Thu, 18 Jan 2024 13:30:05 -0800
From: Martin KaFai Lau <martin.lau@...ux.dev>
To: thinker.li@...il.com
Cc: sinquersw@...il.com, kuifeng@...a.com, netdev@...r.kernel.org,
bpf@...r.kernel.org, ast@...nel.org, song@...nel.org, kernel-team@...a.com,
andrii@...nel.org, drosen@...gle.com
Subject: Re: [PATCH bpf-next v16 03/14] bpf, net: introduce
bpf_struct_ops_desc.
On 1/17/24 5:49 PM, thinker.li@...il.com wrote:
> @@ -1750,11 +1755,6 @@ static inline int bpf_struct_ops_map_sys_lookup_elem(struct bpf_map *map,
> {
> return -EINVAL;
> }
> -static inline int bpf_struct_ops_link_create(union bpf_attr *attr)
> -{
> - return -EOPNOTSUPP;
> -}
> -
This patch is about adding bpf_struct_ops_desc. Why the
bpf_struct_ops_link_create() is removed here?
An unrelated (and unnecessary?) changes?
Powered by blists - more mailing lists