From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Alan Maguire <alan.maguire@oracle.com>
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Ihor Solodrai <ihor.solodrai@linux.dev>,
dwarves <dwarves@vger.kernel.org>, Eduard <eddyz87@gmail.com>,
bpf <bpf@vger.kernel.org>, Andrii Nakryiko <andrii@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Kernel Team <kernel-team@meta.com>
Subject: Re: [PATCH dwarves v4 0/3] btf_encoder: refactor emission of BTF funcs
Date: Fri, 14 Nov 2025 17:54:07 -0300 [thread overview]
Message-ID: <aReW7z_xjpD6ZCXG@x1> (raw)
In-Reply-To: <aReWlPqSGWnj8sPf@x1>
On Fri, Nov 14, 2025 at 05:52:41PM -0300, Arnaldo Carvalho de Melo wrote:
> On Fri, Nov 14, 2025 at 03:40:36PM +0000, Alan Maguire wrote:
> > Yeah, I think if we can augment CI to cover more we can narrow this
> > window, aiming for zero as the test coverage improves.
>
> So the 'next' is an artifact for CI usage, i.e. if we just don't
> announce that it was merged, do it for the CI sake and then when it runs
> and don't detect any problem we go ahead and merge into master and
> announce that it was merged, nothing of this drama would take place.
BTW, I looked at the patches, ran tests and merged next into master,
pushed out to master in both kernel.org and github.
- Arnaldo
prev parent reply other threads:[~2025-11-14 20:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 1:28 [PATCH dwarves v4 0/3] btf_encoder: refactor emission of BTF funcs Ihor Solodrai
2025-11-06 1:28 ` [PATCH dwarves v4 1/3] btf_encoder: Remove encoder pointer from btf_encoder_func_state Ihor Solodrai
2025-11-06 1:28 ` [PATCH dwarves v4 2/3] btf_encoder: Refactor btf_encoder__add_func_proto Ihor Solodrai
2025-11-06 1:28 ` [PATCH dwarves v4 3/3] btf_encoder: Factor out BPF kfunc emission Ihor Solodrai
2025-11-13 16:36 ` [PATCH dwarves v4 0/3] btf_encoder: refactor emission of BTF funcs Alan Maguire
2025-11-13 17:20 ` Alexei Starovoitov
2025-11-14 2:10 ` Arnaldo Carvalho de Melo
2025-11-14 2:14 ` Alexei Starovoitov
2025-11-14 15:40 ` Alan Maguire
2025-11-14 16:27 ` Arnaldo Melo
2025-11-14 20:52 ` Arnaldo Carvalho de Melo
2025-11-14 20:54 ` 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=aReW7z_xjpD6ZCXG@x1 \
--to=acme@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dwarves@vger.kernel.org \
--cc=eddyz87@gmail.com \
--cc=ihor.solodrai@linux.dev \
--cc=kernel-team@meta.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).