From: Steven Rostedt <rostedt@goodmis.org>
To: "igor.stoppa@gmail.com" <igor.stoppa@gmail.com>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
Greg KH <gregkh@linuxfoundation.org>,
ksummit@lists.linux.dev, istoppa@nvidia.com
Subject: Re: [TECH TOPIC] Improving kernel security & integrity by generalizing ad-hoc safety mechanisms
Date: Tue, 8 Sep 2026 13:35:45 -0400 [thread overview]
Message-ID: <20260908133545.05cbbd74@gandalf.local.home> (raw)
In-Reply-To: <CAH2bzCRuoa9BPWr2wvHGe6XVU5gu_Z2kC8h4DZm4Ub+PiVfuNA@mail.gmail.com>
On Tue, 8 Sep 2026 19:09:09 +0300
"igor.stoppa@gmail.com" <igor.stoppa@gmail.com> wrote:
> On Tue, 8 Sept 2026 at 18:39, Steven Rostedt <rostedt@goodmis.org> wrote:
>
> > Perhaps if you do your development on LKML with something in the subject
> > showing that it is for your fork (like we used "[RT PATCH]" to
> > differentiate our work from normal kernel), but it could elicit those that
> > find your work interesting, and then you may get the discussion you are
> > looking for.
>
> That's very good advice, thanks.
> It seemed a bit intrusive to spam everyone with it, but if that's how
> this sort of thing
> gets discussed, sure, why not.
>
Just don't Cc the maintainers of the code you modify, as they may think
it's for inclusion. Cc'ing LKML is one thing, as the only ones that read it
are those that are curious about what is happening around the kernel. If it
has some marking in the subject that denotes the patch is for a fork of the
kernel (that you would be happy to be included one day) it should be fine.
-- Steve
next prev parent reply other threads:[~2026-09-08 17:34 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 16:53 [TECH TOPIC] Improving kernel security & integrity by generalizing ad-hoc safety mechanisms igor.stoppa
2026-09-07 19:46 ` Greg KH
2026-09-07 21:42 ` igor.stoppa
2026-09-08 3:51 ` Theodore Tso
2026-09-08 10:14 ` igor.stoppa
2026-09-08 13:55 ` Theodore Tso
2026-09-08 14:32 ` igor.stoppa
2026-09-08 19:29 ` Steven Rostedt
2026-09-08 21:13 ` igor.stoppa
2026-09-08 23:14 ` Steven Rostedt
2026-09-08 23:48 ` igor.stoppa
2026-09-09 7:44 ` Gabriele Monaco
2026-09-09 9:40 ` igor.stoppa
2026-09-09 15:22 ` Gabriele Monaco
2026-09-09 16:07 ` igor.stoppa
2026-09-09 16:14 ` Steven Rostedt
2026-09-09 16:24 ` igor.stoppa
2026-09-09 16:32 ` Steven Rostedt
2026-09-10 10:10 ` Gabriele Monaco
2026-09-30 2:57 ` Chuck Wolber
2026-09-30 1:58 ` Chuck Wolber
2026-09-08 5:05 ` Greg KH
2026-09-08 11:26 ` igor.stoppa
2026-09-08 11:54 ` Greg KH
2026-09-08 12:25 ` igor.stoppa
2026-09-08 12:39 ` Greg KH
2026-09-08 12:52 ` igor.stoppa
2026-09-08 13:11 ` Miguel Ojeda
2026-09-08 13:52 ` igor.stoppa
2026-09-08 14:44 ` Theodore Tso
2026-09-08 15:32 ` igor.stoppa
2026-09-08 12:41 ` James Bottomley
2026-09-08 13:03 ` igor.stoppa
2026-09-08 15:40 ` Steven Rostedt
2026-09-08 16:09 ` igor.stoppa
2026-09-08 17:35 ` Steven Rostedt [this message]
2026-09-09 1:31 ` Theodore Tso
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=20260908133545.05cbbd74@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=gregkh@linuxfoundation.org \
--cc=igor.stoppa@gmail.com \
--cc=istoppa@nvidia.com \
--cc=ksummit@lists.linux.dev \
/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