From: Sam Ravnborg <sam@ravnborg.org>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: Marco Costalba <mcostalba@gmail.com>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: duplicated include files
Date: Wed, 14 Nov 2007 21:40:24 +0100 [thread overview]
Message-ID: <20071114204024.GC10669@uranus.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.62.0711051146070.28623@pademelon.sonytel.be>
>
> Are you building in a different tree than the source tree? The patch below
> fixed it for me.
>
> Question: Why don't GENKSYMS and KALLSYMS need the $(srctree) prefix?
They are generated binaries that live in the output directory structure.
> ---
> Subject: kbuild: Add missing srctree prefix for includecheck and versioncheck
>
> Add missing $(srctree)/ prefix for scripts used by the includecheck and
> versioncheck make targets
>
> Signed-off-by: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Thanks - applied.
Sam
next prev parent reply other threads:[~2007-11-14 20:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-04 19:41 duplicated include files Marco Costalba
2007-11-04 19:43 ` Marco Costalba
2007-11-04 19:49 ` Robert P. J. Day
2007-11-04 23:20 ` Jeremy Fitzhardinge
2007-11-05 3:49 ` Robert P. J. Day
2007-11-04 23:43 ` Bernd Petrovitsch
2007-11-04 19:51 ` Randy Dunlap
2007-11-05 10:51 ` Geert Uytterhoeven
2007-11-05 11:38 ` Marco Costalba
2007-11-14 20:40 ` Sam Ravnborg [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-04 17:31 Robert P. J. Day
2007-11-04 18:07 ` Randy Dunlap
2007-11-04 18:37 ` Robert P. J. Day
2007-11-04 18:46 ` Randy Dunlap
2007-11-04 19:03 ` Adrian Bunk
2007-11-04 19:10 ` Robert P. J. Day
2007-11-05 3:02 ` Paul Mundt
2007-11-05 8:27 ` Geert Uytterhoeven
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=20071114204024.GC10669@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcostalba@gmail.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;
as well as URLs for NNTP newsgroup(s).