From: David Howells <dhowells@redhat.com>
To: Michal Marek <mmarek@suse.cz>
Cc: dhowells@redhat.com, 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: Tue, 26 Mar 2013 23:32:40 +0000 [thread overview]
Message-ID: <902.1364340760@warthog.procyon.org.uk> (raw)
In-Reply-To: <51522F62.4030108@suse.cz>
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.
But there are generated header files that aren't so handled - though those are
only currently to be found in arch/. I don't mind removing it, it's just that
I don't want to preclude anyone's use of it.
David
prev parent reply other threads:[~2013-03-26 23:32 UTC|newest]
Thread overview: 9+ 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 20:18 ` Andrew Morton
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 23:29 ` Michal Marek
2013-03-26 23:32 ` David Howells [this message]
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=902.1364340760@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.