From: Daniel Borkmann <dborkman@redhat.com>
To: Markos Chandras <Markos.Chandras@imgtec.com>
Cc: linux-kernel@vger.kernel.org,
Randy Dunlap <rdunlap@infradead.org>,
"David S. Miller" <davem@davemloft.net>,
Alexei Starovoitov <ast@plumgrid.com>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation: filter: Add MIPS to architectures with BPF JIT
Date: Wed, 10 Sep 2014 15:31:13 +0200 [thread overview]
Message-ID: <541052A1.9010700@redhat.com> (raw)
In-Reply-To: <541050D0.1020302@imgtec.com>
On 09/10/2014 03:23 PM, Markos Chandras wrote:
> On 08/29/2014 04:33 PM, Daniel Borkmann wrote:
>> On 08/29/2014 04:23 PM, Markos Chandras wrote:
>>> MIPS supports BPF JIT since v3.16-rc1
>>>
>>> Cc: Randy Dunlap <rdunlap@infradead.org>
>>> Cc: "David S. Miller" <davem@davemloft.net>
>>> Cc: Daniel Borkmann <dborkman@redhat.com>
>>> Cc: Alexei Starovoitov <ast@plumgrid.com>
>>> Cc: linux-doc@vger.kernel.org
>>> Signed-off-by: Markos Chandras <markos.chandras@imgtec.com>
>>
>> Acked-by: Daniel Borkmann <dborkman@redhat.com>
...
> I think this hasn't been merged yet (I can't see it in mainline or
> linux-next). Do I need to ping someone or does it have to go via the
> MIPS tree?
You need to send this patch to netdev@vger.kernel.org so Dave
can pick it up from there.
next prev parent reply other threads:[~2014-09-10 13:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 14:23 [PATCH] Documentation: filter: Add MIPS to architectures with BPF JIT Markos Chandras
2014-08-29 15:33 ` Daniel Borkmann
2014-09-10 13:23 ` Markos Chandras
2014-09-10 13:31 ` Daniel Borkmann [this message]
2014-09-10 13:47 ` Markos Chandras
2014-09-10 18:36 ` David Miller
2014-09-10 13:51 ` Markos Chandras
2014-09-10 17:23 ` Alexei Starovoitov
2014-09-10 22:24 ` David Miller
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=541052A1.9010700@redhat.com \
--to=dborkman@redhat.com \
--cc=Markos.Chandras@imgtec.com \
--cc=ast@plumgrid.com \
--cc=davem@davemloft.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox