[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170820.200619.821714603187353951.davem@davemloft.net>
Date: Sun, 20 Aug 2017 20:06:19 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: david.daney@...ium.com
Cc: ast@...nel.org, daniel@...earbox.net, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mips@...ux-mips.org,
ralf@...ux-mips.org
Subject: Re: [PATCH 0/3] MIPS,bpf: Improvements for MIPS eBPF JIT
From: David Daney <david.daney@...ium.com>
Date: Fri, 18 Aug 2017 16:40:30 -0700
> I suggest that the whole thing go via the BPF/net-next path as there
> are dependencies on code that is not yet merged to Linus' tree.
What kind of dependency? On networking or MIPS changes?
If the dependency is on MIPS changes, then if I cannot apply this as
it will break the net-next build on MIPS. You should merge this
via the MIPS tree, where the dependencies are, in that case.
Please clarify what is specifically happening here.
Thanks.
Powered by blists - more mailing lists