public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: David Herrmann <dh.herrmann@gmail.com>,
	Jim Davis <jim.epost@gmail.com>,
	linux-next <linux-next@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Daniel Mack <daniel@zonque.org>,
	David Herrmann <dh.herrmann@googlemail.com>,
	Djalal Harouni <tixxdz@opendz.org>
Subject: Re: randconfig build error with next-20150316, in samples/kdbus/kdbus-workers
Date: Tue, 17 Mar 2015 09:28:12 +1100	[thread overview]
Message-ID: <20150317092812.58da11cb@canb.auug.org.au> (raw)
In-Reply-To: <1426540369.20069.1.camel@ellerman.id.au>

[-- Attachment #1: Type: text/plain, Size: 503 bytes --]

Hi Michael,

On Tue, 17 Mar 2015 08:12:49 +1100 Michael Ellerman <mpe@ellerman.id.au> wrote:
>
> But the samples are also including the unsanitised headers, which I think is
> what's causing the problem here.
> 
> HOSTCFLAGS_kdbus-workers.o +=           \
>          -I$(objtree)/usr/include/       \
>          -I$(objtree)/include/uapi/

There is a new patch in the kdbus tree today that removes the uapi
include.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      parent reply	other threads:[~2015-03-16 22:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16 16:22 randconfig build error with next-20150316, in samples/kdbus/kdbus-workers Jim Davis
2015-03-16 16:31 ` David Herrmann
2015-03-16 21:12   ` Michael Ellerman
2015-03-16 22:27     ` David Herrmann
2015-03-16 22:51       ` Michael Ellerman
2015-03-16 23:00         ` David Herrmann
2015-03-17  2:09           ` Michael Ellerman
2015-03-16 22:28     ` Stephen Rothwell [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=20150317092812.58da11cb@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=daniel@zonque.org \
    --cc=dh.herrmann@gmail.com \
    --cc=dh.herrmann@googlemail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jim.epost@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mpe@ellerman.id.au \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox