From: Linus Torvalds <torvalds@linux-foundation.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"the arch/x86 maintainers" <x86@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Ian Rogers <irogers@google.com>
Subject: Re: [GIT pull] x86/urgent for v5.15-rc3
Date: Tue, 28 Sep 2021 15:44:10 -0700 [thread overview]
Message-ID: <CAHk-=wjyNDcrS1nEskxdes38wAajF+4B+cFwh4HCPhPEDvFL9w@mail.gmail.com> (raw)
In-Reply-To: <YVN94ojuLApdN1IT@zn.tnic>
On Tue, Sep 28, 2021 at 1:41 PM Borislav Petkov <bp@alien8.de> wrote:
>
> Bah, I got carried away with the axe...
>
> And looka here: 1d509f2a6ebc ("x86/insn: Support big endian cross-compiles")
Ahh. s390. For some reason I thought they were LE too, clearly
incorrectly. So yeah, there still are serious big BE machines that you
might want to cross-compile from.
Linus
next prev parent reply other threads:[~2021-09-28 22:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-26 10:30 [GIT pull] irq/urgent for v5.15-rc3 Thomas Gleixner
2021-09-26 10:30 ` [GIT pull] timers/urgent " Thomas Gleixner
2021-09-26 17:27 ` pr-tracker-bot
2021-09-26 10:30 ` [GIT pull] x86/urgent " Thomas Gleixner
2021-09-26 17:21 ` Linus Torvalds
2021-09-26 18:15 ` Borislav Petkov
2021-09-26 19:10 ` Linus Torvalds
2021-09-28 17:56 ` Borislav Petkov
2021-09-28 20:13 ` Linus Torvalds
2021-09-28 20:41 ` Borislav Petkov
2021-09-28 22:44 ` Linus Torvalds [this message]
2021-09-29 18:10 ` [PATCH] x86/insn: Use get_unaligned() instead of memcpy() Borislav Petkov
2021-09-30 0:00 ` Masami Hiramatsu
2021-10-04 9:48 ` [tip: x86/misc] " tip-bot2 for Borislav Petkov
2021-10-06 10:02 ` tip-bot2 for Borislav Petkov
2021-09-26 17:27 ` [GIT pull] x86/urgent for v5.15-rc3 pr-tracker-bot
2021-09-26 17:27 ` [GIT pull] irq/urgent " pr-tracker-bot
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='CAHk-=wjyNDcrS1nEskxdes38wAajF+4B+cFwh4HCPhPEDvFL9w@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=adrian.hunter@intel.com \
--cc=bp@alien8.de \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@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).