From: Pavel Roskin <proski@gnu.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] Use the kernel source tree for includes, not the kernel build tree
Date: Tue, 16 Sep 2008 16:34:56 -0400 [thread overview]
Message-ID: <1221597296.17084.4.camel@dv> (raw)
In-Reply-To: <1221596322.9262.7.camel@johannes.berg>
On Tue, 2008-09-16 at 22:18 +0200, Johannes Berg wrote:
> > diff --git a/Makefile b/Makefile
> > index 74cb1e1..9e79381 100644
> > --- a/Makefile
> > +++ b/Makefile
> > @@ -6,7 +6,7 @@ INSTALL ?= install
> > PREFIX ?= /usr
> > CC ?= "gcc"
> > CFLAGS += -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration
> > -CFLAGS += -I/lib/modules/`uname -r`/build/include
> > +CFLAGS += -I/lib/modules/`uname -r`/source/include
>
> I'll remove that line entirely though.
In Makefile? Please make sure that .config remains optional.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-09-16 20:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-16 20:08 [PATCH] Use the kernel source tree for includes, not the kernel build tree Pavel Roskin
2008-09-16 20:18 ` Johannes Berg
2008-09-16 20:34 ` Pavel Roskin [this message]
2008-09-16 20:37 ` Johannes Berg
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=1221597296.17084.4.camel@dv \
--to=proski@gnu.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/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