From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: "Jiri Olsa" <jolsa@kernel.org>,
"Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Network Development" <netdev@vger.kernel.org>,
bpf <bpf@vger.kernel.org>, "Andrii Nakryiko" <andriin@fb.com>,
"Yonghong Song" <yhs@fb.com>, "Martin KaFai Lau" <kafai@fb.com>,
"Jakub Kicinski" <jakub.kicinski@netronome.com>,
"David Miller" <davem@redhat.com>,
"Björn Töpel" <bjorn.topel@intel.com>,
"John Fastabend" <john.fastabend@gmail.com>
Subject: Re: [PATCHv4 0/3] bpf: trampoline fixes
Date: Sat, 25 Jan 2020 16:35:30 +0100 [thread overview]
Message-ID: <20200125153530.GC26877@kernel.org> (raw)
In-Reply-To: <CAADnVQLBQ2t30BwqBb9wJc5rM5M9URvKk25HUBa94PuL8tYcDw@mail.gmail.com>
Em Sat, Jan 25, 2020 at 07:23:21AM -0800, Alexei Starovoitov escreveu:
> On Thu, Jan 23, 2020 at 8:15 AM Jiri Olsa <jolsa@kernel.org> wrote:
> > v4 changes:
> > - rebased on latest bpf-next/master
> > - removed image tree mutex and use trampoline_mutex instead
> > - checking directly for string pointer in patch 1 [Alexei]
> > - skipped helpers patches, as they are no longer needed [Alexei]
>
> Applied. Thanks
While watching Jiri's talk about bpftrace, cool.
- Arnaldo
prev parent reply other threads:[~2020-01-25 15:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 16:15 [PATCHv4 0/3] bpf: trampoline fixes Jiri Olsa
2020-01-23 16:15 ` [PATCH 1/3] bpf: Allow BTF ctx access for string pointers Jiri Olsa
2020-01-23 16:15 ` [PATCH 2/3] bpf: Allow to resolve bpf trampoline and dispatcher in unwind Jiri Olsa
2020-01-23 16:15 ` [PATCH 3/3] selftest/bpf: Add test for allowed trampolines count Jiri Olsa
2020-01-25 15:23 ` [PATCHv4 0/3] bpf: trampoline fixes Alexei Starovoitov
2020-01-25 15:35 ` Arnaldo Carvalho de Melo [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=20200125153530.GC26877@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=bjorn.topel@intel.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@redhat.com \
--cc=jakub.kicinski@netronome.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=netdev@vger.kernel.org \
--cc=yhs@fb.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.