All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
	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:33:44 -0700	[thread overview]
Message-ID: <20160912203344.GB2516@roeck-us.net> (raw)
In-Reply-To: <3540553.8BkpiafJJ2@wuerfel>

On Mon, Sep 12, 2016 at 10:28:56PM +0200, Arnd Bergmann wrote:
> 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@arndb.de>
> 
> FWIW, you should be able to test this with an arm64 cross-compiler
> too, many distros ship one.
> 
arm64 builds fine, though, even w/o this patch (at least for me).

Guenter

  reply	other threads:[~2016-09-12 20:33 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 [this message]
2016-09-12 20:34     ` Dave Hansen
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=20160912203344.GB2516@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=arnd@arndb.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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.