From: Conor Dooley <conor@kernel.org>
To: Alexandre Ghiti <alex@ghiti.fr>
Cc: linux-riscv@lists.infradead.org,
Conor Dooley <conor.dooley@microchip.com>,
Jason Montleon <jmontleo@redhat.com>,
ojeda@kernel.org, alex.gaynor@gmail.com, boqun.feng@gmail.com,
gary@garyguo.net, bjorn3_gh@protonmail.com,
benno.lossin@proton.me, a.hindborg@kernel.org,
aliceryhl@google.com, paul.walmsley@sifive.com,
palmer@dabbelt.com, nathan@kernel.org, ndesaulniers@google.com,
morbo@google.com, justinstitt@google.com,
rust-for-linux@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH v1] RISC-V: disallow gcc + rust builds
Date: Wed, 9 Oct 2024 09:23:40 +0100 [thread overview]
Message-ID: <20241009-tamale-revisit-7d2606c5fdf3@spud> (raw)
In-Reply-To: <c4906bfc-5bc1-428e-a76f-3fb0bb8711ac@ghiti.fr>
[-- Attachment #1.1: Type: text/plain, Size: 934 bytes --]
On Wed, Oct 09, 2024 at 10:10:14AM +0200, Alexandre Ghiti wrote:
> > > , it is better
> > > to disable gcc + rust builds to match the original intent, and
> > > subsequently support it when an appropriate set of extensions can be
> > > deduced from the version of libclang.
> > >
> > > Closes:
> > > https://lore.kernel.org/all/20240917000848.720765-2-jmontleo@redhat.com/
> > > [1]
> > > Link:
> > > https://lore.kernel.org/all/20240926-battering-revolt-6c6a7827413e@spud/
> > > [2]
> > > Fixes: 70a57b247251a ("RISC-V: enable building 64-bit kernels with
> > > rust support")
>
>
> I also fixed the Fixes tag ^, it contains 13 characters instead of 12 and
> added a cc: stable tag.
FYI, checkpatch is not an arbiter of truth, and I intentionally left the
13th character that git determined it needed to have there. Apparently
the kernel now has enough objects that there can be 12 character
collisions.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2024-10-09 8:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 11:28 [PATCH v1] RISC-V: disallow gcc + rust builds Conor Dooley
2024-10-01 15:12 ` Miguel Ojeda
2024-10-01 18:55 ` Nathan Chancellor
2024-10-01 19:27 ` Conor Dooley
2024-10-09 7:46 ` Alexandre Ghiti
2024-10-09 8:10 ` Alexandre Ghiti
2024-10-09 8:23 ` Conor Dooley [this message]
2024-10-09 8:34 ` Alexandre Ghiti
2024-10-09 12:52 ` Miguel Ojeda
2024-10-17 16:30 ` patchwork-bot+linux-riscv
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=20241009-tamale-revisit-7d2606c5fdf3@spud \
--to=conor@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=alex@ghiti.fr \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=conor.dooley@microchip.com \
--cc=gary@garyguo.net \
--cc=jmontleo@redhat.com \
--cc=justinstitt@google.com \
--cc=linux-riscv@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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