From: Steven Rostedt <rostedt@goodmis.org>
To: Bradley Morgan <include@grrlz.net>
Cc: "Jérémy Jean" <Jeremy.Jean@oss.cyber.gouv.fr>,
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 17:52:09 -0400 [thread overview]
Message-ID: <20260822175209.3bc255d3@fedora> (raw)
In-Reply-To: <20260822170928.1acba2cc@fedora>
On Sat, 22 Aug 2026 17:09:28 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> > >Resending v2
> >
> > (no! V3!!)
>
> Right, when resending, it is best to add "[RESEND]" to the subject:
I shouldn't have said "right" because it wasn't. You add "RESEND" not
v3. You should not up the version if the patch has not changed and you
are only resending to update the Cc. I do that all the time.
-- Steve
>
> [RESEND][PATCH v2] fork: initialize function graph state before copy_exec_state()
prev parent reply other threads:[~2026-08-22 21:52 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
2026-08-24 14:00 ` Steven Rostedt
2026-08-22 21:52 ` Steven Rostedt [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=20260822175209.3bc255d3@fedora \
--to=rostedt@goodmis.org \
--cc=Jeremy.Jean@oss.cyber.gouv.fr \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=include@grrlz.net \
--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=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