From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: David Herrmann <dh.herrmann@gmail.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
David Herrmann <dh.herrmann@googlemail.com>,
Daniel Mack <daniel@zonque.org>,
Djalal Harouni <tixxdz@opendz.org>,
linux-mips@linux-mips.org,
linux-kernel <linux-kernel@vger.kernel.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: Re: samples/kdbus/kdbus-workers.c and cross compiling MIPS
Date: Fri, 31 Jul 2015 09:29:21 -0700 [thread overview]
Message-ID: <20150731162921.GA6335@kroah.com> (raw)
In-Reply-To: <1438326061.29353.9.camel@ellerman.id.au>
On Fri, Jul 31, 2015 at 05:01:01PM +1000, Michael Ellerman wrote:
> It's obviously possible that some samples build with that configuration, but
> building against another arch'es kernel headers just seems like it's asking for
> trouble. Even if we can build the samples, they will never run correctly.
>
> So I suggest we should just disable SAMPLES if we're cross compiling, full stop.
Yes, that seems like a much better solution overall. Can you send a
patch for this?
thanks,
greg k-h
next prev parent reply other threads:[~2015-07-31 16:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 16:19 samples/kdbus/kdbus-workers.c and cross compiling MIPS Paul Gortmaker
2015-07-29 16:19 ` Paul Gortmaker
2015-07-29 16:31 ` David Herrmann
2015-07-30 13:50 ` Paul Gortmaker
2015-07-30 13:50 ` Paul Gortmaker
2015-07-30 14:23 ` David Herrmann
2015-07-30 15:32 ` Paul Gortmaker
2015-07-30 15:32 ` Paul Gortmaker
2015-07-30 23:55 ` Stephen Rothwell
2015-07-30 23:55 ` Stephen Rothwell
2015-07-31 6:54 ` Michael Ellerman
2015-07-31 7:01 ` Michael Ellerman
2015-07-31 16:29 ` Greg Kroah-Hartman [this message]
2015-08-03 4:58 ` Michael Ellerman
2015-07-30 1:28 ` Michael Ellerman
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=20150731162921.GA6335@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=daniel@zonque.org \
--cc=dh.herrmann@gmail.com \
--cc=dh.herrmann@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-next@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=paul.gortmaker@windriver.com \
--cc=tixxdz@opendz.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 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.