[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e98df2e2-6b57-6c1c-e80e-732434b177ad@huawei.com>
Date: Tue, 20 Aug 2019 19:46:56 +0800
From: Yuehaibing <yuehaibing@...wei.com>
To: Dan Carpenter <dan.carpenter@...cle.com>,
Björn Töpel <bjorn.topel@...il.com>
CC: Björn Töpel <bjorn.topel@...el.com>,
"Karlsson, Magnus" <magnus.karlsson@...el.com>,
Jonathan Lemon <jonathan.lemon@...il.com>,
Alexei Starovoitov <ast@...nel.org>,
"Daniel Borkmann" <daniel@...earbox.net>,
Martin KaFai Lau <kafai@...com>,
Song Liu <songliubraving@...com>, Yonghong Song <yhs@...com>,
John Fastabend <john.fastabend@...il.com>,
Netdev <netdev@...r.kernel.org>, bpf <bpf@...r.kernel.org>,
<kernel-janitors@...r.kernel.org>
Subject: Re: [PATCH -next] bpf: Use PTR_ERR_OR_ZERO in xsk_map_inc()
On 2019/8/20 17:44, Dan Carpenter wrote:
> On Tue, Aug 20, 2019 at 11:25:29AM +0200, Björn Töpel wrote:
>> On Tue, 20 Aug 2019 at 10:59, Dan Carpenter <dan.carpenter@...cle.com> wrote:
>>>
>>> On Tue, Aug 20, 2019 at 09:28:26AM +0200, Björn Töpel wrote:
>>>> For future patches: Prefix AF_XDP socket work with "xsk:" and use "PATCH
>>>> bpf-next" to let the developers know what tree you're aiming for.
>>>
>>> There are over 300 trees in linux-next. It impossible to try remember
>>> everyone's trees. No one else has this requirement.
>>>
>>
>> Net/bpf are different, and I wanted to point that out to lessen the
>> burden for the maintainers. It's documented in:
>>
>> Documentation/bpf/bpf_devel_QA.rst.
>> Documentation/networking/netdev-FAQ.rst
>
> Ah... I hadn't realized that BPF patches were confusing to Dave.
>
> I actually do keep track of net and net-next. I do quite a bit of extra
> stuff for netdev patches. So what about if we used [PATCH] for bpf and
> [PATCH net] and [PATCH net-next] for networking?
>
> I will do that.
bpf-next is a good choice.
>
> regards,
> dan carpenter
>
> .
>
Powered by blists - more mailing lists