From: Luke Nelson <lukenels@cs.washington.edu>
To: "Björn Töpel" <bjorn.topel@gmail.com>
Cc: Netdev <netdev@vger.kernel.org>, bpf <bpf@vger.kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
linux-riscv@lists.infradead.org, Damien.LeMoal@wdc.com,
hch@infradead.org, kbuild test robot <lkp@intel.com>
Subject: Re: [PATCH bpf] riscv: remove BPF JIT for nommu builds
Date: Tue, 31 Mar 2020 07:57:35 -0700 [thread overview]
Message-ID: <CADasFoDZq=+34MSjPD7gqEDhW8Zm_zFWAamHZc7ZsAeYT2=Lrg@mail.gmail.com> (raw)
In-Reply-To: <20200331101046.23252-1-bjorn.topel@gmail.com>
Thanks for looking into this!
Acked-by: Luke Nelson <luke.r.nels@gmail.com>
WARNING: multiple messages have this Message-ID (diff)
From: Luke Nelson <lukenels@cs.washington.edu>
To: "Björn Töpel" <bjorn.topel@gmail.com>
Cc: Damien.LeMoal@wdc.com, kbuild test robot <lkp@intel.com>,
Daniel Borkmann <daniel@iogearbox.net>,
Netdev <netdev@vger.kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
hch@infradead.org, bpf <bpf@vger.kernel.org>,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH bpf] riscv: remove BPF JIT for nommu builds
Date: Tue, 31 Mar 2020 07:57:35 -0700 [thread overview]
Message-ID: <CADasFoDZq=+34MSjPD7gqEDhW8Zm_zFWAamHZc7ZsAeYT2=Lrg@mail.gmail.com> (raw)
In-Reply-To: <20200331101046.23252-1-bjorn.topel@gmail.com>
Thanks for looking into this!
Acked-by: Luke Nelson <luke.r.nels@gmail.com>
next prev parent reply other threads:[~2020-03-31 14:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 10:10 [PATCH bpf] riscv: remove BPF JIT for nommu builds Björn Töpel
2020-03-31 10:10 ` Björn Töpel
2020-03-31 14:57 ` Luke Nelson [this message]
2020-03-31 14:57 ` Luke Nelson
2020-04-02 22:51 ` Daniel Borkmann
2020-04-02 22:51 ` 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='CADasFoDZq=+34MSjPD7gqEDhW8Zm_zFWAamHZc7ZsAeYT2=Lrg@mail.gmail.com' \
--to=lukenels@cs.washington.edu \
--cc=Damien.LeMoal@wdc.com \
--cc=ast@kernel.org \
--cc=bjorn.topel@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=hch@infradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.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 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.