From mboxrd@z Thu Jan  1 00:00:00 1970
From: Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: [PATCH bpf-next v8 00/12] bpf: More sock_ops callbacks
Date: Wed, 24 Jan 2018 07:48:00 -0800
Message-ID: <1516808880.3715.20.camel@gmail.com>
References: <20180124075802.1522053-1-brakmo@fb.com>
         <1516803255.3715.16.camel@gmail.com>
         <7c73497a-19c3-bfa9-3a66-a1187d429c6d@fb.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: Kernel Team <kernel-team@fb.com>, Blake Matheny <bmatheny@fb.com>,
        Daniel Borkmann <daniel@iogearbox.net>,
        Neal Cardwell <ncardwell@google.com>,
        Yuchung Cheng <ycheng@google.com>
To: Alexei Starovoitov <ast@fb.com>, Lawrence Brakmo <brakmo@fb.com>,
        netdev <netdev@vger.kernel.org>
Return-path: <netdev-owner@vger.kernel.org>
Received: from mail-pf0-f174.google.com ([209.85.192.174]:39871 "EHLO
        mail-pf0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S934132AbeAXPsE (ORCPT
        <rfc822;netdev@vger.kernel.org>); Wed, 24 Jan 2018 10:48:04 -0500
Received: by mail-pf0-f174.google.com with SMTP id e11so3360214pff.6
        for <netdev@vger.kernel.org>; Wed, 24 Jan 2018 07:48:04 -0800 (PST)
In-Reply-To: <7c73497a-19c3-bfa9-3a66-a1187d429c6d@fb.com>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

On Wed, 2018-01-24 at 07:27 -0800, Alexei Starovoitov wrote:
> 
> Most of the time, Yes, but it's the other way around this time.
> I specifically asked Larry to do it this way, since net tree is
> practically closed (only critical fixes allowed).
> When 4.15 is released on Sunday we'll send this patch
> independently to 4.15 and 4.14
> 

How hard would it be to put the fix first in the series then ?
If this proves complex, then maybe we have a bigger problem.

I did not know merging bpf into bpf-next would be hard :)


Thanks.