mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, Michal Marek <mmarek@suse.com>,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] Kbuild: don't add obj tree in additional includes
Date: Wed, 15 Jun 2016 17:42:07 +0200	[thread overview]
Message-ID: <12307786.ur6o1LYuVt@wuerfel> (raw)
In-Reply-To: <201606140609.AQumlVjN%fengguang.wu@intel.com>

On Tuesday, June 14, 2016 6:42:16 AM CEST kbuild test robot wrote:
>    kernel/time/Kconfig:155:warning: range is invalid
>    In file included from arch/x86/include/asm/seccomp.h:4:0,
>                     from include/linux/seccomp.h:11,
>                     from include/linux/sched.h:43,
>                     from arch/x86/um/shared/sysdep/kernel-offsets.h:2,
>                     from arch/um/kernel/asm-offsets.c:1:
> >> arch/x86/include/asm/unistd.h:15:29: fatal error: asm/unistd_32.h: No such file or directory
>     #  include <asm/unistd_32.h>

Clearly this version was no good, I'm following up with a (longer) replacement,
let's see how that works out.

	Arnd

  reply	other threads:[~2016-06-15 15:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-13 21:19 [PATCH 1/3] Kbuild: don't add ../../ to include path Arnd Bergmann
2016-06-13 21:19 ` [PATCH 2/3] Kbuild: don't add obj tree in additional includes Arnd Bergmann
2016-06-13 21:38   ` kbuild test robot
2016-06-13 22:42   ` kbuild test robot
2016-06-15 15:42     ` Arnd Bergmann [this message]
2016-06-13 22:51   ` kbuild test robot
2016-06-13 21:19 ` [PATCH 3/3] Kbuild: avoid duplicate include path Arnd Bergmann

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=12307786.ur6o1LYuVt@wuerfel \
    --to=arnd@arndb.de \
    --cc=kbuild-all@01.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mmarek@suse.com \
    /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

all inboxes | Powered by JetHome®