From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Paul Burton <paul.burton@mips.com>
Cc: "daniel@iogearbox.net" <daniel@iogearbox.net>,
"ast@kernel.org" <ast@kernel.org>,
Jiong Wang <jiong.wang@netronome.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"oss-drivers@netronome.com" <oss-drivers@netronome.com>,
Markos Chandras <markos.chandras@imgtec.com>,
Paul Burton <pburton@wavecomp.com>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>
Subject: Re: [PATCH v2 bpf] mips: bpf: fix encoding bug for mm_srlv32_op
Date: Mon, 3 Dec 2018 16:23:15 -0800 [thread overview]
Message-ID: <20181203162315.548ad882@cakuba.netronome.com> (raw)
In-Reply-To: <20181204000623.6tmqntmxi2dydrlz@pburton-laptop>
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.
prev parent reply other threads:[~2018-12-04 0:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 22:27 [PATCH v2 bpf] mips: bpf: fix encoding bug for mm_srlv32_op Jiong Wang
2018-12-03 22:42 ` Paul Burton
2018-12-03 23:55 ` Jakub Kicinski
2018-12-04 0:06 ` Paul Burton
2018-12-04 0:23 ` Jakub Kicinski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181203162315.548ad882@cakuba.netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=jiong.wang@netronome.com \
--cc=linux-mips@vger.kernel.org \
--cc=markos.chandras@imgtec.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.com \
--cc=paul.burton@mips.com \
--cc=pburton@wavecomp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.