linux-kernel - Re: [PATCH] doc: change example to existing Makefile fragment

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1364258406.15703.70@driftwood>
Date:	Mon, 25 Mar 2013 19:40:06 -0500
From:	Rob Landley <rob@...dley.net>
To:	Paul Bolle <pebolle@...cali.nl>
Cc:	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
	Michal Marek <mmarek@...e.cz>
Subject: Re: [PATCH] doc: change example to existing Makefile fragment

On 03/25/2013 05:16:24 AM, Paul Bolle wrote:
> Signed-off-by: Paul Bolle <pebolle@...cali.nl>
> ---
>  Documentation/kbuild/makefiles.txt | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)

Acked-by: Rob Landley <rob@...dley.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
> 
> 
> 
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/