[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070525051245.GA4958@uranus.ravnborg.org>
Date: Fri, 25 May 2007 07:12:45 +0200
From: Sam Ravnborg <sam@...nborg.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Romano Giannetti <romano.giannetti@...il.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Chris Wright <chrisw@...s-sol.org>,
Chuck Ebbert <cebbert@...hat.com>,
linux-kernel@...r.kernel.org, stable@...nel.org,
Justin Forbes <jmforbes@...uxtx.org>,
Zwane Mwaikambo <zwane@....linux.org.uk>,
Theodore Ts'o <tytso@....edu>,
Randy Dunlap <rdunlap@...otime.net>,
Dave Jones <davej@...hat.com>,
Chuck Wolber <chuckw@...ntumlinux.com>,
Chris Wedgwood <reviews@...cw.f00f.org>,
Michael Krufky <mkrufky@...uxtv.org>, alan@...rguk.ukuu.org.uk
Subject: Re: Long delay in resume from RAM (Was Re: [patch 00/69] -stablereview)
On Thu, May 24, 2007 at 02:21:26PM -0700, Andrew Morton wrote:
>
> It's not a matter of when it's evaluated. The user is supposed to be
> able to set EXTRA_CFLAGS on the command-line, yes? If they do that then
> the "=" in there will rub out their efforts. The makefiles should be
> appending new things to EXTRA_CFLAGS, rather than doing a replacement?
There is no way to specify additional CFLAGS on the commandline today.
For sparse we took the shorthand CF so you can do:
make C=2 CF=-warn-bitwise
But we have no such thing for CFLAGS.
If there is a real need I can cook up something.
But frankly I have alway edited top-level Makefile and be doen with it.
I will fix it so Kbuild do not barf out if you set EXTRA_* on the commandline
but silently ignore it instead.
Sam
-
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/
Powered by blists - more mailing lists