[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <005b01cbb130$712f8f80$538eae80$@mprc.pku.edu.cn>
Date: Tue, 11 Jan 2011 09:39:49 +0800
From: "Guan Xuetao" <guanxuetao@...c.pku.edu.cn>
To: "'Sam Ravnborg'" <sam@...nborg.org>
Cc: "'lkml'" <linux-kernel@...r.kernel.org>,
"'linux-kbuild'" <linux-kbuild@...r.kernel.org>,
"'linux arch'" <linux-arch@...r.kernel.org>,
"'Arnd Bergmann'" <arnd@...db.de>,
"'Michal Marek'" <mmarek@...e.cz>
Subject: RE: [PATCH 1/2] kbuild: asm-generic support
> -----Original Message-----
> From: Sam Ravnborg [mailto:sam@...nborg.org]
> Sent: Tuesday, January 11, 2011 12:27 AM
> To: Guan Xuetao
> Cc: 'lkml'; 'linux-kbuild'; 'linux arch'; 'Arnd Bergmann'; 'Michal Marek'
> Subject: Re: [PATCH 1/2] kbuild: asm-generic support
>
> Hi Guan (I will try to spell you name correct fom now on!)
Thanks.
>
> > > + During the prepare phase of the build a wrapper include
> > > + file is generated in the directory:
> > > +
> > > + arch/$(ARCH)/include/generated/asm
> > IMHO, the directory could be include/generated/asm
>
> We have moved all the arch specific files away from include/*
> which is why I invented arch/$(ARCH)/include/generated.
>
> I was actually considering:
>
> arch/$(ARCH)/generated.
>
> But using include/generated just seems wrong.
The generated headers is just the wrapper of asm-generic headers, so it's
more the interface than the arch specific files.
Using include/generated avoids two generated header dirs, and simplifies
the thought and handler.
Guan Xuetao
--
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