From: Michal Marek <mmarek@suse.cz>
To: David Howells <dhowells@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, arnd@arndb.de,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] UAPI: Remove empty Kbuild files
Date: Wed, 27 Mar 2013 00:29:38 +0100 [thread overview]
Message-ID: <51522F62.4030108@suse.cz> (raw)
In-Reply-To: <32381.1364338459@warthog.procyon.org.uk>
On 26.3.2013 23:54, David Howells wrote:
> Michal Marek <mmarek@suse.cz> wrote:
>
>>> I want to know whether I should extend my patch to remove include/Kbuild and
>>> any refs to it.
>>
>> make headers_install starts at include/uapi, so include/Kbuild is not
>> needed. And new exported headers end up in inclde/uapi, so there will
>> probably not be need for include/Kbuild in the future either. IMO, just
>> remove it.
>
> That's not all Kbuild does. It also handles autogenerated headers.
That's true. But include/generated is handled by the main Makefile
directly as well.
Michal
next prev parent reply other threads:[~2013-03-26 23:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 17:48 [PATCH] UAPI: Remove empty Kbuild files David Howells
2013-03-26 17:48 ` David Howells
2013-03-26 20:18 ` Andrew Morton
2013-03-26 20:59 ` David Howells
2013-03-26 20:59 ` David Howells
2013-03-26 21:05 ` Andrew Morton
2013-03-26 21:27 ` David Howells
2013-03-26 21:47 ` Michal Marek
2013-03-26 22:54 ` David Howells
2013-03-26 22:54 ` David Howells
2013-03-26 23:29 ` Michal Marek [this message]
2013-03-26 23:29 ` Michal Marek
2013-03-26 23:32 ` David Howells
2013-03-26 23:32 ` David Howells
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=51522F62.4030108@suse.cz \
--to=mmarek@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=dhowells@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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