From: David Howells <dhowells@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: dhowells@redhat.com, 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 20:59:43 +0000 [thread overview]
Message-ID: <29647.1364331583@warthog.procyon.org.uk> (raw)
In-Reply-To: <20130326131828.209aff73e38d3273d078bb2e@linux-foundation.org>
Andrew Morton <akpm@linux-foundation.org> wrote:
> > Remove empty Kbuild files as they cause problems with the patch program
> > which removes files that become empty.
> >
> > Should I also remove include/Kbuild as that now does nothing? Or should
> > it be left as an anchor just in case we want it in future?
>
> I think that if the build system created it, a `make clean' or `make
> mproper' should rub it out again. Ideally a `make mrproper' will give
> you a tree which is identical to a freshly-untarred kernel.org tarball
> (yes?).
Ummm... What's that got to do with it? include/Kbuild is part of the
sources: make clean/mrproper/distclean should not be removing it.
> Which reminds me of my email which you're still hiding from ;)
> Shouldn't a `make mrproper' undo the effects of `make headers_install'
> by wiping ./usr/include/?
Ummm...
warthog>cp .../.config .
warthog>make -j12 >&/dev/null
warthog>find usr/include/ | wc -l
873
warthog>make distclean >&/dev/null
warthog>find usr/include/ | wc -l
find: `usr/include/': No such file or directory
0
and:
warthog>cp .../.config .
warthog>make -j12 >&/dev/null
warthog>find usr/include/ | wc -l
873
warthog>make mrproper >&/dev/null
warthog>find usr/include/ | wc -l
find: `usr/include/': No such file or directory
0
so I don't see the problem.
David
next prev parent reply other threads:[~2013-03-26 20:59 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 [this message]
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
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=29647.1364331583@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=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