From: Dave Hansen <dave.hansen@linux.intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Guenter Roeck <linux@roeck-us.net>,
Thomas Gleixner <tglx@linutronix.de>,
"open list:ABI/API" <linux-api@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: Build failures in -next: sys_pkey_mprotect etc. undefined
Date: Mon, 12 Sep 2016 13:34:54 -0700 [thread overview]
Message-ID: <57D7116E.4050708@linux.intel.com> (raw)
In-Reply-To: <3540553.8BkpiafJJ2@wuerfel>
On 09/12/2016 01:28 PM, Arnd Bergmann wrote:
> FWIW, you should be able to test this with an arm64 cross-compiler
> too, many distros ship one.
arm64 build fine for me with and without the patch. There must be
something else specific to h8300 and the other broken architectures.
Is there some other part of the configuration that could be hiding the
issue in my arm64 build?
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <dave.hansen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: Arnd Bergmann <arnd-r2nGTMty4D4@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 13:34:54 -0700 [thread overview]
Message-ID: <57D7116E.4050708@linux.intel.com> (raw)
In-Reply-To: <3540553.8BkpiafJJ2@wuerfel>
On 09/12/2016 01:28 PM, Arnd Bergmann wrote:
> FWIW, you should be able to test this with an arm64 cross-compiler
> too, many distros ship one.
arm64 build fine for me with and without the patch. There must be
something else specific to h8300 and the other broken architectures.
Is there some other part of the configuration that could be hiding the
issue in my arm64 build?
next prev parent reply other threads:[~2016-09-12 20:34 UTC|newest]
Thread overview: 11+ 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
2016-09-12 14:59 ` Arnd Bergmann
2016-09-12 14:59 ` Arnd Bergmann
2016-09-12 15:03 ` Dave Hansen
2016-09-12 20:09 ` Dave Hansen
2016-09-12 20:28 ` Arnd Bergmann
2016-09-12 20:28 ` Arnd Bergmann
2016-09-12 20:33 ` Guenter Roeck
2016-09-12 20:34 ` Dave Hansen [this message]
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=57D7116E.4050708@linux.intel.com \
--to=dave.hansen@linux.intel.com \
--cc=arnd@arndb.de \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.