From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: rust-for-linux@vger.kernel.org
Cc: Stephen Rothwell <sfr@canb.auug.org.au>
Subject: We are now in linux-next!
Date: Thu, 18 Mar 2021 11:59:13 +0100 [thread overview]
Message-ID: <CANiq72nbNxpps+p4wYp03ncrbGH9FFoTfHQZwg_vGdPO41eGmQ@mail.gmail.com> (raw)
Hi all,
Thanks to Stephen Rothwell, we are now in linux-next!
This does not mean we will make it into mainline, of course, but it is
a nice step to make things as smooth as possible.
Stephen has kindly agreed to give me a bit of leeway the first few
days until the RFC to rebase things as needed, which is very much
appreciated.
Cheers,
Miguel
next reply other threads:[~2021-03-18 11:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 10:59 Miguel Ojeda [this message]
2021-03-18 12:33 ` We are now in linux-next! Alex Gaynor
2021-03-18 19:26 ` Geert Stappers
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=CANiq72nbNxpps+p4wYp03ncrbGH9FFoTfHQZwg_vGdPO41eGmQ@mail.gmail.com \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).