From: James Morris <jmorris@namei.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Christian Brauner <brauner@kernel.org>,
Julia Lawall <julia.lawall@inria.fr>, Greg KH <greg@kroah.com>,
gmonaco@redhat.com, ojeda@kernel.org, aliceryhl@google.com,
gary@garyguo.net, namcao@linutronix.de, sashal@kernel.org,
natalie.klaus@runtimeverification.com, willy@infradead.org,
linux-kernel@vger.kernel.org, Paul Moore <paul@paul-moore.com>,
tytso@mit.edu, keisuke.nishimura@inria.fr,
jean-pierre.lozi@inria.fr, ejratl@gmail.com,
corinn_tiffany@alumni.brown.edu, kate.stewart@att.net
Subject: Re: Kernel formal methods mailing list?
Date: Wed, 4 Nov 2026 12:56:30 -0800 (PST) [thread overview]
Message-ID: <b765a5d3-9844-fed8-4277-2a998980b33f@namei.org> (raw)
In-Reply-To: <4ea0f231-eec4-4f41-bd2c-e5484c0535de@paulmck-laptop>
On Wed, 4 Nov 2026, Paul E. McKenney wrote:
> > Thoughts? Would it be worth setting up a mailing list?
>
> We do have (low-traffic) lkmm@lists.linux.dev, though that was intended to
> be specific to the Linux kernel memory model and its formal-verification
> tooling.
That's a possibility. Would the mm folk there would want to keep it domain-focused?
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2026-11-04 20:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 23:59 James Morris
2026-11-04 2:57 ` Natalie Klaus
2026-11-04 11:22 ` Greg KH
2026-11-04 13:23 ` Miguel Ojeda
2026-11-04 17:54 ` Paul E. McKenney
2026-11-04 20:56 ` James Morris [this message]
2026-11-04 21:43 ` Miguel Ojeda
2026-11-04 22:21 ` Paul E. McKenney
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=b765a5d3-9844-fed8-4277-2a998980b33f@namei.org \
--to=jmorris@namei.org \
--cc=aliceryhl@google.com \
--cc=brauner@kernel.org \
--cc=corinn_tiffany@alumni.brown.edu \
--cc=ejratl@gmail.com \
--cc=gary@garyguo.net \
--cc=gmonaco@redhat.com \
--cc=greg@kroah.com \
--cc=jean-pierre.lozi@inria.fr \
--cc=julia.lawall@inria.fr \
--cc=kate.stewart@att.net \
--cc=keisuke.nishimura@inria.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=namcao@linutronix.de \
--cc=natalie.klaus@runtimeverification.com \
--cc=ojeda@kernel.org \
--cc=paul@paul-moore.com \
--cc=paulmck@kernel.org \
--cc=sashal@kernel.org \
--cc=tytso@mit.edu \
--cc=willy@infradead.org \
/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®