From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
To: Dave Hansen <dave.hansen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Cc: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>,
Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
"open list:ABI/API"
<linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-arch <linux-arch-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Build failures in -next: sys_pkey_mprotect etc. undefined
Date: Mon, 12 Sep 2016 22:28:56 +0200 [thread overview]
Message-ID: <3540553.8BkpiafJJ2@wuerfel> (raw)
In-Reply-To: <57D70B6D.6010208-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
On Monday, September 12, 2016 1:09:17 PM CEST Dave Hansen wrote:
>
> So, I've done what Arnd suggested, but I don't have a working
> cross-compiler than can do h8300 or c6x. Could you test the attached
> patch and see if it gets things working for you?
>
> Also, do you have a handy place to grab a cross-compiler for h8300
> without having to build one? The kernel.org ones don't seem to work for
> h8300.
>
I haven't tested it, but it looks good to me
Acked-by: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
FWIW, you should be able to test this with an arm64 cross-compiler
too, many distros ship one.
Arnd
next prev parent reply other threads:[~2016-09-12 20:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 14:55 Build failures in -next: sys_pkey_mprotect etc. undefined Guenter Roeck
[not found] ` <9d74497b-1522-b350-42fa-49df2df48c4a-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2016-09-12 14:59 ` Arnd Bergmann
2016-09-12 15:03 ` Dave Hansen
2016-09-12 20:09 ` Dave Hansen
[not found] ` <57D70B6D.6010208-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2016-09-12 20:28 ` Arnd Bergmann [this message]
2016-09-12 20:33 ` Guenter Roeck
2016-09-12 20:34 ` Dave Hansen
2016-09-12 20:32 ` Guenter Roeck
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=3540553.8BkpiafJJ2@wuerfel \
--to=arnd-r2ngtmty4d4@public.gmane.org \
--cc=dave.hansen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arch-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.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