From: Rob Landley <rob@landley.net>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Michal Marek <mmarek@suse.cz>
Subject: Re: [PATCH] doc: change example to existing Makefile fragment
Date: Mon, 25 Mar 2013 19:40:06 -0500 [thread overview]
Message-ID: <1364258406.15703.70@driftwood> (raw)
In-Reply-To: <1364206584.1390.268.camel@x61.thuisdomein> (from pebolle@tiscali.nl on Mon Mar 25 05:16:24 2013)
On 03/25/2013 05:16:24 AM, Paul Bolle wrote:
> Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
> ---
> Documentation/kbuild/makefiles.txt | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
Acked-by: Rob Landley <rob@landley.net>
Please send through the kbuild tree.
Rob
> diff --git a/Documentation/kbuild/makefiles.txt
> b/Documentation/kbuild/makefiles.txt
> index 5198b74..020bb67 100644
> --- a/Documentation/kbuild/makefiles.txt
> +++ b/Documentation/kbuild/makefiles.txt
> @@ -921,8 +921,9 @@ When kbuild executes, the following steps are
> followed (roughly):
> Often, the KBUILD_CFLAGS variable depends on the configuration.
>
> Example:
> - #arch/x86/Makefile
> - cflags-$(CONFIG_M386) += -march=i386
> + #arch/x86/boot/compressed/Makefile
> + cflags-$(CONFIG_X86_32) := -march=i386
> + cflags-$(CONFIG_X86_64) := -mcmodel=small
> KBUILD_CFLAGS += $(cflags-y)
>
> Many arch Makefiles dynamically run the target C compiler to
> --
> 1.7.11.7
>
>
>
>
next prev parent reply other threads:[~2013-03-26 0:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 10:16 [PATCH] doc: change example to existing Makefile fragment Paul Bolle
2013-03-26 0:40 ` Rob Landley [this message]
2013-04-08 10:42 ` Michal Marek
2013-04-08 10:51 ` [PATCH v2] " Paul Bolle
2013-04-08 11:01 ` Michal Marek
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=1364258406.15703.70@driftwood \
--to=rob@landley.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=pebolle@tiscali.nl \
/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.