From: Richard Weinberger <richard@nod.at>
To: davidgow <davidgow@google.com>
Cc: anton ivanov <anton.ivanov@cambridgegreys.com>,
Johannes Berg <johannes@sipsolutions.net>,
linux-um <linux-um@lists.infradead.org>, x86 <x86@kernel.org>,
llvm@lists.linux.dev,
Rust for Linux Kernel <rust-for-linux@vger.kernel.org>,
kunit-dev <kunit-dev@googlegroups.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
SeongJae Park <sj@kernel.org>,
Roberto Sassu <roberto.sassu@huaweicloud.com>,
Miguel Ojeda <ojeda@kernel.org>,
Nathan Chancellor <nathan@kernel.org>, mingo <mingo@redhat.com>,
tglx <tglx@linutronix.de>,
Nick Desaulniers <ndesaulniers@google.com>
Subject: Re: [PATCH] arch:um: Only disable SSE on clang to work around old GCC bugs
Date: Fri, 31 Mar 2023 10:37:31 +0200 (CEST) [thread overview]
Message-ID: <2128345299.463203.1680251851757.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <CABVgOS=pr=jXq4qRrKaCy47xczDaFXFKCPanVvaZ+MfQmtwK8A@mail.gmail.com>
----- Ursprüngliche Mail -----
> Von: "davidgow" <davidgow@google.com>
> An: "richard" <richard@nod.at>, "anton ivanov" <anton.ivanov@cambridgegreys.com>, "Johannes Berg"
> Any chance we could get this picked up as a fix for 6.3? The UML build
> is still broken with older gcc versions.
Sure. Just got flooded with other stuff. :-S
Thanks,
//richard
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2023-03-31 9:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-18 4:15 [PATCH] arch:um: Only disable SSE on clang to work around old GCC bugs David Gow
2023-03-20 17:22 ` Vincenzo Palazzo
2023-03-21 20:11 ` Arthur Grillo Queiroz Cabral
2023-03-31 8:25 ` David Gow
2023-03-31 8:37 ` Richard Weinberger [this message]
2023-04-04 7:59 ` Richard Weinberger
2023-03-31 13:39 ` Miguel Ojeda
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=2128345299.463203.1680251851757.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=anton.ivanov@cambridgegreys.com \
--cc=davidgow@google.com \
--cc=johannes@sipsolutions.net \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=mingo@redhat.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
--cc=roberto.sassu@huaweicloud.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=sj@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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).