[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221129081510.56b1025e@kernel.org>
Date: Tue, 29 Nov 2022 08:15:10 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Steffen Klassert <steffen.klassert@...unet.com>
Cc: Martin KaFai Lau <martin.lau@...ux.dev>,
Eyal Birger <eyal.birger@...il.com>, <netdev@...r.kernel.org>,
<bpf@...r.kernel.org>, <linux-kselftest@...r.kernel.org>,
<davem@...emloft.net>, <edumazet@...gle.com>, <pabeni@...hat.com>,
<herbert@...dor.apana.org.au>, <andrii@...nel.org>,
<daniel@...earbox.net>, <nicolas.dichtel@...nd.com>,
<razor@...ckwall.org>, <mykolal@...com>, <ast@...nel.org>,
<song@...nel.org>, <yhs@...com>, <john.fastabend@...il.com>,
<kpsingh@...nel.org>, <sdf@...gle.com>, <haoluo@...gle.com>,
<jolsa@...nel.org>, <shuah@...nel.org>
Subject: Re: [PATCH ipsec-next 2/3] xfrm: interface: Add unstable helpers
for setting/getting XFRM metadata from TC-BPF
On Tue, 29 Nov 2022 10:50:01 +0100 Steffen Klassert wrote:
> > Please tag for bpf-next
>
> This is a change to xfrm ipsec, so it should go
> through the ipsec-next tree, unless there is
> a good reason for handling that different.
Yeah, this is borderline. Do the patches apply cleanly to Linus's tree?
If so maybe they can be posted as a PR and both trees can pull them in,
avoiding any unnecessary back and forth...
Powered by blists - more mailing lists