From: Bradley Morgan <include@grrlz.net>
To: "Steven Rostedt" <rostedt@goodmis.org>,
"Jérémy Jean" <jeremy.jean@oss.cyber.gouv.fr>
Cc: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, mgorman@suse.de, bsegall@google.com,
dietmar.eggemann@arm.com, kees@kernel.org,
kprateek.nayak@amd.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, vschneid@redhat.com,
linux-trace-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v3] fork: initialize function graph state before copy_exec_state()
Date: Sat, 22 Aug 2026 22:47:36 +0100 [thread overview]
Message-ID: <B701B25D-C39D-46FB-982B-5681B3D45CC6@grrlz.net> (raw)
In-Reply-To: <20260822174053.26aa2f56@fedora>
On 22 August 2026 22:40:53 BST, Steven Rostedt <rostedt@goodmis.org> wrote:
>On Sat, 22 Aug 2026 23:12:35 +0200
>Jérémy Jean <jeremy.jean@oss.cyber.gouv.fr> wrote:
>
>> Oops, I did not know that, sorry.
>> Do you want me to resend once more, or that's okay?
>
>No need. It's in patchwork and I'll manually add Bradley's R-B tag and
>start testing it.
>
Will you merge it to one of your very cool tree(s)? I've merged it to my
friends distro tree, not maintainer tree or anything, but I do tests, I
guess that's like future learning! ;d
>-- Steve
>
Thanks!
next prev parent reply other threads:[~2026-08-22 21:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-22 19:53 [PATCH v2] fork: initialize function graph state before copy_exec_state() Jérémy Jean
2026-08-22 19:58 ` [PATCH v3] " Bradley Morgan
2026-08-22 21:09 ` Steven Rostedt
2026-08-22 21:12 ` Jérémy Jean
2026-08-22 21:40 ` Steven Rostedt
2026-08-22 21:45 ` Jérémy Jean
2026-08-22 21:47 ` Bradley Morgan [this message]
2026-08-24 14:00 ` Steven Rostedt
2026-08-22 21:52 ` Steven Rostedt
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=B701B25D-C39D-46FB-982B-5681B3D45CC6@grrlz.net \
--to=include@grrlz.net \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=jeremy.jean@oss.cyber.gouv.fr \
--cc=juri.lelli@redhat.com \
--cc=kees@kernel.org \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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