rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Desaulniers <ndesaulniers@google.com>
To: Josh Triplett <josh@joshtriplett.org>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
	rust-for-linux <rust-for-linux@vger.kernel.org>
Subject: Re: Poll for call
Date: Mon, 19 Apr 2021 16:11:42 -0700	[thread overview]
Message-ID: <CAKwvOdmwhn4_Uba-WpGKJd3aL_1Re2Z7xJ3rT-qCzuFpKxx_ZQ@mail.gmail.com> (raw)
In-Reply-To: <YH4NRfghnRB2z1E4@localhost>

On Mon, Apr 19, 2021 at 4:07 PM Josh Triplett <josh@joshtriplett.org> wrote:
>
> On Mon, Apr 19, 2021 at 02:20:11PM -0700, Nick Desaulniers wrote:
> > On Mon, Apr 19, 2021 at 1:43 PM Josh Triplett <josh@joshtriplett.org> wrote:
> > >
> > > Either day works for me, and I'd love to join.
> > >
> > > Linux Plumbers Conference and Kernel Summit are coming up. I'd like to
> > > propose a "What Does the Kernel Need from Rust?" session, with my lang
> > > and libs hats on.
> > >
> > > I'd also love to talk about the recent LKML thread, and the plans for a
> > > custom alloc crate vs reusing the Rust alloc crate.
> >
> > I have a microconf proposal for "Toolchains and Kernel MC" (similar to
> > last year) that I'm waiting to hear back on.  It would be nice if you
> > could hold that proposal for that MC, rather than the general
> > "Refereed-track."
>
> I'd actually like to propose it for Kernel Summit. I'd also be happy to
> participate in an LPC session similar to last year.

Ok, I will recall the "Toolchains and Kernel MC" proposal then; my
main interest was to have a venue for discussion about Rust+Linux; if
there's another venue more appropriate let's use that so that conf
organizers aren't confused by multiple proposals.
-- 
Thanks,
~Nick Desaulniers

  reply	other threads:[~2021-04-19 23:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-19 16:14 Poll for call Miguel Ojeda
2021-04-19 18:15 ` Nick Desaulniers
2021-04-19 20:42 ` Josh Triplett
2021-04-19 21:20   ` Nick Desaulniers
2021-04-19 23:07     ` Josh Triplett
2021-04-19 23:11       ` Nick Desaulniers [this message]
2021-04-20  1:27         ` Josh Triplett
2021-04-20  1:28         ` Miguel Ojeda
2021-04-20  2:22           ` Nick Desaulniers
2021-04-19 20:52 ` Joshua Abraham
2021-04-20 11:03 ` Finn Behrens
2021-04-20 17:44   ` Adam Bratschi-Kaye
2021-04-21  7:29 ` Robin Randhawa
2021-04-23 18:30 ` Miguel Ojeda
2021-04-24 16:54   ` Gary Guo

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=CAKwvOdmwhn4_Uba-WpGKJd3aL_1Re2Z7xJ3rT-qCzuFpKxx_ZQ@mail.gmail.com \
    --to=ndesaulniers@google.com \
    --cc=josh@joshtriplett.org \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=rust-for-linux@vger.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;
as well as URLs for NNTP newsgroup(s).