From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail•com>
Cc: Thorsten Leemhuis <linux@leemhuis•info>,
linux-kernel@vger•kernel.org,
Linux regressions mailing list <regressions@lists•linux.dev>,
rust-for-linux@vger•kernel.org, Miguel Ojeda <ojeda@kernel•org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: REGRESSION: armv7 build mismatched types
Date: Wed, 4 Jun 2025 07:31:18 +1000 [thread overview]
Message-ID: <20250604073118.4205f303@canb.auug.org.au> (raw)
In-Reply-To: <CANiq72=+qUNJu5j+uoveMrTbngwA89+ScwjUPd9OyVGqps54aw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 614 bytes --]
Hi Miguel,
On Tue, 3 Jun 2025 15:04:02 +0200 Miguel Ojeda <miguel.ojeda.sandonis@gmail•com> wrote:
>
> On Tue, Jun 3, 2025 at 2:51 PM Thorsten Leemhuis <linux@leemhuis•info> wrote:
> >
> > Or is this heading towards mainline really soon now anyway?
>
> The Rust PR is, but it would be nice to have the fix in -next before
> sending the PR (I will give Linus a test merge anyway, but it is nice
> to know everything is OK in -next too, and to have another reference
> point for Linus).
Damn! I knew I would forget. Sorry about that, it will be applied
today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-06-03 21:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <700ebe13-c2d3-48e3-800f-8dc327efb6fc@gmail.com>
2025-05-30 7:46 ` REGRESSION: armv7 build mismatched types Thorsten Leemhuis
[not found] ` <CANiq72mFL4dn+0JppLLfxyKnM+xYwKeduFw2j07hUfxWVVHdUw@mail.gmail.com>
2025-06-03 12:51 ` Thorsten Leemhuis
2025-06-03 13:04 ` Miguel Ojeda
2025-06-03 21:31 ` Stephen Rothwell [this message]
2025-06-03 22:26 ` Miguel Ojeda
2025-06-04 10:46 ` Miguel Ojeda
2025-06-04 10:59 ` Rudraksha Gupta
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=20250604073118.4205f303@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux@leemhuis$(echo .)info \
--cc=miguel.ojeda.sandonis@gmail$(echo .)com \
--cc=ojeda@kernel$(echo .)org \
--cc=regressions@lists$(echo .)linux.dev \
--cc=rust-for-linux@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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