From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Miguel Ojeda <ojeda@kernel.org>, Alban Kurti <kurti@invicto.ai>,
Benno Lossin <benno.lossin@proton.me>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the rust tree with Linus' tree
Date: Mon, 17 Mar 2025 23:35:40 +0100 [thread overview]
Message-ID: <CANiq72kH9VqvhPyTxFh=_9Sbo_0ucnQbRMjN=FUshbNa6cUWHA@mail.gmail.com> (raw)
In-Reply-To: <20250318093123.22f584df@canb.auug.org.au>
On Mon, Mar 17, 2025 at 11:31 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> I did not receive your "last message" - or is it still on its way?
I was finishing a few build tests, just in case -- sending...
Cheers,
Miguel
next prev parent reply other threads:[~2025-03-17 22:35 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 10:20 linux-next: manual merge of the rust tree with Linus' tree Stephen Rothwell
2025-03-17 19:37 ` Miguel Ojeda
2025-03-17 22:31 ` Stephen Rothwell
2025-03-17 22:35 ` Miguel Ojeda [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-21 4:31 Stephen Rothwell
2025-07-21 8:23 ` Miguel Ojeda
2025-03-17 10:05 Stephen Rothwell
2025-03-17 19:36 ` Miguel Ojeda
2024-09-16 8:03 Stephen Rothwell
2024-09-16 8:12 ` Miguel Ojeda
2022-10-04 8:05 Stephen Rothwell
2022-09-12 7:24 Stephen Rothwell
2022-07-25 8:41 Stephen Rothwell
2022-07-25 8:52 ` Miguel Ojeda
2022-07-13 10:34 Stephen Rothwell
2022-07-13 10:50 ` Miguel Ojeda
2022-07-13 11:39 ` Peter Zijlstra
2022-07-15 1:13 ` Miguel Ojeda
2022-07-15 9:01 ` Peter Zijlstra
2022-07-15 11:01 ` Miguel Ojeda
2021-12-10 18:18 broonie
2021-11-03 3:19 Stephen Rothwell
2021-11-03 10:30 ` Miguel Ojeda
2021-11-03 21:01 ` Stephen Rothwell
2021-11-04 12:19 ` Miguel Ojeda
2021-11-04 20:31 ` Stephen Rothwell
2021-11-05 11:00 ` Miguel Ojeda
2021-07-19 6:16 Stephen Rothwell
2021-07-12 0:37 Stephen Rothwell
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='CANiq72kH9VqvhPyTxFh=_9Sbo_0ucnQbRMjN=FUshbNa6cUWHA@mail.gmail.com' \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=benno.lossin@proton.me \
--cc=kurti@invicto.ai \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ojeda@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).