[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20181203162315.548ad882@cakuba.netronome.com>
Date:   Mon, 3 Dec 2018 16:23:15 -0800
From:   Jakub Kicinski <jakub.kicinski@...ronome.com>
To:     Paul Burton <paul.burton@...s.com>
Cc:     "daniel@...earbox.net" <daniel@...earbox.net>,
        "ast@...nel.org" <ast@...nel.org>,
        Jiong Wang <jiong.wang@...ronome.com>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "oss-drivers@...ronome.com" <oss-drivers@...ronome.com>,
        Markos Chandras <markos.chandras@...tec.com>,
        Paul Burton <pburton@...ecomp.com>,
        "linux-mips@...r.kernel.org" <linux-mips@...r.kernel.org>
Subject: Re: [PATCH v2 bpf] mips: bpf: fix encoding bug for mm_srlv32_op
On Tue, 4 Dec 2018 00:06:24 +0000, Paul Burton wrote:
> If you have related patches the best thing to do would be to submit them
> together as a series. Then after the maintainers involved can see the
> patches we can figure out the best way to apply them.
Right, in hindsight that could've worked better, but for netdev/bpf
patches posting fixes and features in one series is a no-no :)
I guess the best way forward would be for Jiong to post the dependent
set (BPF_ALU | BPF_ARSH support) as an RFC and then decide.  The
conflict will be trivial, yet avoidable if we wait for this to
propagate to bpf-next.
Powered by blists - more mailing lists
 
