From: David Miller <davem@redhat.com>
To: bjorn.topel@gmail.com
Cc: linux-riscv@lists.infradead.org, daniel@iogearbox.net,
ast@kernel.org, netdev@vger.kernel.org, palmer@sifive.com,
hch@infradead.org
Subject: Re: [PATCH bpf-next 2/3] MAINTAINERS: add RISC-V BPF JIT maintainer
Date: Sun, 03 Feb 2019 09:08:31 -0800 (PST) [thread overview]
Message-ID: <20190203.090831.1775635225008332226.davem@redhat.com> (raw)
In-Reply-To: <20190203115132.8766-3-bjorn.topel@gmail.com>
From: bjorn.topel@gmail.com
Date: Sun, 3 Feb 2019 12:51:30 +0100
> 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>
Acked-by: David S. Miller <davem@davemloft.net>
WARNING: multiple messages have this Message-ID (diff)
From: David Miller <davem@redhat.com>
To: bjorn.topel@gmail.com
Cc: daniel@iogearbox.net, netdev@vger.kernel.org, palmer@sifive.com,
ast@kernel.org, hch@infradead.org,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH bpf-next 2/3] MAINTAINERS: add RISC-V BPF JIT maintainer
Date: Sun, 03 Feb 2019 09:08:31 -0800 (PST) [thread overview]
Message-ID: <20190203.090831.1775635225008332226.davem@redhat.com> (raw)
In-Reply-To: <20190203115132.8766-3-bjorn.topel@gmail.com>
From: bjorn.topel@gmail.com
Date: Sun, 3 Feb 2019 12:51:30 +0100
> 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>
Acked-by: David S. Miller <davem@davemloft.net>
_______________________________________________
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-03 17:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-03 11:51 [PATCH bpf-next 0/3] Add RISC-V (RV64G) BPF JIT bjorn.topel
2019-02-03 11:51 ` bjorn.topel
2019-02-03 11:51 ` [PATCH bpf-next 1/3] bpf, riscv: add BPF JIT for RV64G bjorn.topel
2019-02-03 11:51 ` bjorn.topel
2019-02-03 17:08 ` David Miller
2019-02-03 17:08 ` David Miller
2019-02-04 20:06 ` Daniel Borkmann
2019-02-04 20:06 ` Daniel Borkmann
2019-02-04 20:27 ` Björn Töpel
2019-02-04 20:27 ` Björn Töpel
2019-02-03 11:51 ` [PATCH bpf-next 2/3] MAINTAINERS: add RISC-V BPF JIT maintainer bjorn.topel
2019-02-03 11:51 ` bjorn.topel
2019-02-03 17:08 ` David Miller [this message]
2019-02-03 17:08 ` David Miller
2019-02-03 11:51 ` [PATCH bpf-next 3/3] bpf, doc: add RISC-V to filter.txt bjorn.topel
2019-02-03 11:51 ` bjorn.topel
2019-02-03 17:08 ` David Miller
2019-02-03 17:08 ` David Miller
2019-02-04 20:09 ` Daniel Borkmann
2019-02-04 20:09 ` Daniel Borkmann
2019-02-04 20:16 ` Björn Töpel
2019-02-04 20:16 ` Björn Töpel
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=20190203.090831.1775635225008332226.davem@redhat.com \
--to=davem@redhat.com \
--cc=ast@kernel.org \
--cc=bjorn.topel@gmail.com \
--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 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.