From: Jason@zx2c4.com (Jason A. Donenfeld)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: support big-endian for the virt architecture
Date: Sat, 29 Sep 2018 04:52:30 +0200 [thread overview]
Message-ID: <CAHmME9rGgnNTd84-ywcNZfRx0a3dnqUaCMoSkKHYSUPN1jZiew@mail.gmail.com> (raw)
In-Reply-To: <CAK8P3a3riqD9kzGZHLxhYug7zO34e2icOaWddzH2JezbZKVNPg@mail.gmail.com>
Hey Arnd,
On Fri, Sep 28, 2018 at 9:19 PM Arnd Bergmann <arnd@arndb.de> wrote:
> You can probably work around it by enabling ARCH_HIGHBANK,
> which is a minimal platform with no other requirements, so it
> should only add a few milliseconds to the build.
Nice hack, thanks for the suggestion. Committed here:
https://git.kernel.org/pub/scm/linux/kernel/git/zx2c4/WireGuard.git/commit/?id=56ff2eb9480e6c691a5b8d8ff1fa01090df61e1d
> Another option would be to do the testing on top of linux-next,
> which should have your fix starting on Monday. Testing on
> linux-next carries a higher risk of running into unrelated
> regressions, but also lets you find out about conflicts with
> other patches early on.
I do actually test on linux-next (and tons of other kernels too), but
I like to have things working for at least the latest mainline.
Jason
prev parent reply other threads:[~2018-09-29 2:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 13:51 [PATCH] arm: support big-endian for the virt architecture Jason A. Donenfeld
2018-09-28 8:41 ` Ard Biesheuvel
2018-09-28 15:52 ` Arnd Bergmann
2018-09-28 16:04 ` Jason A. Donenfeld
2018-09-28 19:19 ` Arnd Bergmann
2018-09-29 2:52 ` Jason A. Donenfeld [this message]
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=CAHmME9rGgnNTd84-ywcNZfRx0a3dnqUaCMoSkKHYSUPN1jZiew@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=linux-arm-kernel@lists.infradead.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).