From: bjorn.topel@gmail.com
To: linux-riscv@lists.infradead.org, daniel@iogearbox.net,
ast@kernel.org, netdev@vger.kernel.org
Cc: hch@infradead.org, "Björn Töpel" <bjorn.topel@gmail.com>,
palmer@sifive.com
Subject: [PATCH bpf-next v2 2/4] MAINTAINERS: add RISC-V BPF JIT maintainer
Date: Tue, 5 Feb 2019 13:41:23 +0100 [thread overview]
Message-ID: <20190205124125.5553-3-bjorn.topel@gmail.com> (raw)
In-Reply-To: <20190205124125.5553-1-bjorn.topel@gmail.com>
From: Björn Töpel <bjorn.topel@gmail.com>
Add Björn Töpel as RISC-V BPF JIT maintainer.
Signed-off-by: Björn Töpel <bjorn.topel@gmail.com>
---
MAINTAINERS | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 019a2bcfbd09..b4491132b9ce 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2907,6 +2907,12 @@ L: netdev@vger.kernel.org
S: Maintained
F: arch/powerpc/net/
+BPF JIT for RISC-V (RV64G)
+M: Björn Töpel <bjorn.topel@gmail.com>
+L: netdev@vger.kernel.org
+S: Maintained
+F: arch/riscv/net/
+
BPF JIT for S390
M: Martin Schwidefsky <schwidefsky@de.ibm.com>
M: Heiko Carstens <heiko.carstens@de.ibm.com>
--
2.19.1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-02-05 12:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 12:41 [PATCH bpf-next v2 0/4] Add RISC-V (RV64G) BPF JIT bjorn.topel
2019-02-05 12:41 ` [PATCH bpf-next v2 1/4] bpf, riscv: add BPF JIT for RV64G bjorn.topel
2019-02-05 12:41 ` bjorn.topel [this message]
2019-02-05 12:41 ` [PATCH bpf-next v2 3/4] bpf, doc: add RISC-V JIT to BPF documentation bjorn.topel
2019-02-05 12:41 ` [PATCH bpf-next v2 4/4] selftests/bpf: add "any alignment" annotation for some tests bjorn.topel
2019-02-05 16:05 ` [PATCH bpf-next v2 0/4] Add RISC-V (RV64G) BPF JIT Daniel Borkmann
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=20190205124125.5553-3-bjorn.topel@gmail.com \
--to=bjorn.topel@gmail.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=hch@infradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=palmer@sifive.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).