mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: stern@rowland.harvard.edu, parri.andrea@gmail.com,
	will@kernel.org, peterz@infradead.org, boqun.feng@gmail.com,
	npiggin@gmail.com, dhowells@redhat.com, j.alglave@ucl.ac.uk,
	luc.maranget@inria.fr, akiyks@gmail.com, dlustig@nvidia.com,
	joel@joelfernandes.org
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: Another possible use for LKMM, or a subset (strengthening) thereof
Date: Mon, 18 Oct 2021 15:53:13 -0700	[thread overview]
Message-ID: <20211018225313.GA855976@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <20211007205621.GA584182@paulmck-ThinkPad-P17-Gen-1>

On Thu, Oct 07, 2021 at 01:56:21PM -0700, Paul E. McKenney wrote:
> Hello!
> 
> On the perhaps unlikely chance that this is new news of interest...
> 
> I have finally prototyped the full "So You Want to Rust the Linux
> Kernel?" series (as in marked "under construction").
> 
> https://paulmck.livejournal.com/62436.html

And this blog series is now proclaimed to be feature complete.

Recommendations (both short- and long-term) may be found in the last post,
"TL;DR: Memory-Model Recommendations for Rusting the Linux Kernel",
at https://paulmck.livejournal.com/65341.html.

Thoughts?

							Thanx, Paul

  reply	other threads:[~2021-10-18 22:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-07 20:56 Paul E. McKenney
2021-10-18 22:53 ` Paul E. McKenney [this message]
2021-10-18 23:56   ` Boqun Feng
2021-10-19  0:07     ` Paul E. McKenney
2021-10-19  2:28       ` Boqun Feng
2021-10-19  3:50         ` 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=20211018225313.GA855976@paulmck-ThinkPad-P17-Gen-1 \
    --to=paulmck@kernel.org \
    --cc=akiyks@gmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=dlustig@nvidia.com \
    --cc=j.alglave@ucl.ac.uk \
    --cc=joel@joelfernandes.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luc.maranget@inria.fr \
    --cc=npiggin@gmail.com \
    --cc=parri.andrea@gmail.com \
    --cc=peterz@infradead.org \
    --cc=stern@rowland.harvard.edu \
    --cc=will@kernel.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®