From: Daniel Borkmann <daniel@iogearbox.net>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Martin Rodriguez Reboredo <yakoyoku@gmail.com>,
linux-kernel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Neal Gompa <neal@gompa.dev>, Eric Curtin <ecurtin@redhat.com>,
bpf@vger.kernel.org, rust-for-linux@vger.kernel.org,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Yonghong Song <yhs@fb.com>
Subject: Re: [PATCH v3] scripts: Exclude Rust CUs with pahole
Date: Mon, 16 Jan 2023 18:06:20 +0100 [thread overview]
Message-ID: <bec74b32-e35f-9489-4748-cbb241b31be7@iogearbox.net> (raw)
In-Reply-To: <CANiq72m+8D8OGtkyEjmyqCynp48DCKEw4-zLZ4pm6-OmFe4p1w@mail.gmail.com>
On 1/16/23 5:52 PM, Miguel Ojeda wrote:
> On Mon, Jan 16, 2023 at 5:37 PM Daniel Borkmann <daniel@iogearbox.net> wrote:
>>
>> I presume Miguel will pick this up via rust tree? (Either way, would be nice to
>> also get an Ack from Arnaldo.)
>
> I am happy to, but I think it would be great if BPF takes it whenever
> you think it is a good time. And indeed, let's give time to Arnaldo to
> take a look.
Ok, if you could ack it for the rust bits, we can route it via bpf-next.
Thanks,
Daniel
next prev parent reply other threads:[~2023-01-16 17:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 15:20 Martin Rodriguez Reboredo
2023-01-11 15:22 ` Eric Curtin
2023-01-11 15:34 ` Neal Gompa
2023-01-11 16:16 ` Eric Curtin
2023-01-11 16:21 ` Neal Gompa
2023-01-16 16:37 ` Daniel Borkmann
2023-01-16 16:52 ` Miguel Ojeda
2023-01-16 17:06 ` Daniel Borkmann [this message]
2023-01-16 17:19 ` Miguel Ojeda
2023-02-10 20:48 ` [PATCH 1/1] pahole/Rust: Check that we're adding DW_TAG_member sorted by byte offset Arnaldo Carvalho de Melo
2023-02-13 12:09 ` pahole issues with Rust DWARF was: " Arnaldo Carvalho de Melo
2023-02-13 12:45 ` Miguel Ojeda
2023-02-13 12:53 ` Eric Curtin
2023-02-13 21:53 ` Arnaldo Carvalho de Melo
2023-02-13 21:05 ` Arnaldo Carvalho de Melo
2023-02-14 21:22 ` Arnaldo Carvalho de Melo
2023-01-16 19:22 ` [PATCH v3] scripts: Exclude Rust CUs with pahole Arnaldo Carvalho de Melo
2023-01-17 16:40 ` patchwork-bot+netdevbpf
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=bec74b32-e35f-9489-4748-cbb241b31be7@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=acme@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=ecurtin@redhat.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=neal@gompa.dev \
--cc=rust-for-linux@vger.kernel.org \
--cc=yakoyoku@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®