From mboxrd@z Thu Jan  1 00:00:00 1970
From: Daniel Borkmann <daniel@iogearbox.net>
Subject: Re: [net-next V9 PATCH 00/16] XDP redirect memory return API
Date: Wed, 4 Apr 2018 10:41:18 +0200
Message-ID: <e653aca7-41d5-1ed9-2212-bb2297ca6b53@iogearbox.net>
References: <152275360298.1026.10333759008401281682.stgit@firesoul>
 <20180403.105427.1908874085989267860.davem@davemloft.net>
 <20180403180716.66c3daee@redhat.com>
 <20180403.122338.1130037886539379926.davem@davemloft.net>
 <CALzJLG8bbMnBWvnKP-OvhZ2NF2=KzHVqyuiepnsJRQEMv86_JQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Cc: Jesper Dangaard Brouer <brouer@redhat.com>,
        Linux Netdev List <netdev@vger.kernel.org>,
        bjorn.topel@intel.com, magnus.karlsson@intel.com,
        Eugenia Emantayev <eugenia@mellanox.com>, jasowang@redhat.com,
        John Fastabend <john.fastabend@gmail.com>,
        Eran Ben Elisha <eranbe@mellanox.com>,
        Saeed Mahameed <saeedm@mellanox.com>,
        Gal Pressman <galp@mellanox.com>,
        Daniel Borkmann <borkmann@iogearbox.net>,
        Alexei Starovoitov <alexei.starovoitov@gmail.com>,
        Tariq Toukan <tariqt@mellanox.com>
To: Saeed Mahameed <saeedm@dev.mellanox.co.il>,
        David Miller <davem@davemloft.net>
Return-path: <netdev-owner@vger.kernel.org>
Received: from www62.your-server.de ([213.133.104.62]:36122 "EHLO
        www62.your-server.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751274AbeDDIlZ (ORCPT
        <rfc822;netdev@vger.kernel.org>); Wed, 4 Apr 2018 04:41:25 -0400
In-Reply-To: <CALzJLG8bbMnBWvnKP-OvhZ2NF2=KzHVqyuiepnsJRQEMv86_JQ@mail.gmail.com>
Content-Language: en-US
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

On 04/03/2018 07:03 PM, Saeed Mahameed wrote:
> On Tue, Apr 3, 2018 at 9:23 AM, David Miller <davem@davemloft.net> wrote:
>> From: Jesper Dangaard Brouer <brouer@redhat.com>
>> Date: Tue, 3 Apr 2018 18:07:16 +0200
>>> On Tue, 03 Apr 2018 10:54:27 -0400 (EDT)
>>> David Miller <davem@davemloft.net> wrote:
>>>
>>>> Don't worry, just resubmit when net-next opens back up.
>>>
>>> At that point in time, should I got back to posting it against the
>>> bpf-next git-tree again? Any preferences from Mellanox or BPF-guys?
>>
>> I have no personal preference, although it's probably best to go
>> through the bpf-next tree.

I'm fine either way as well.

>>> ... It have been a bit of a pain to keep track of driver changes in
>>> net-next, and waiting for them to get merged into bpf-next.
>>
>> I totally understand :)
> 
> it depends on how often bpf-next gets synced with net-next, mlx5
> constantly changes and
> I can't gurantee no merge conflicts will occur.

We push out bpf and bpf-next typically once a week to sync, but in case
of potential merge conflict or a dependency that we need to pull into
bpf-next we can always push it out immediately and re-sync if we get a
heads up.