From: Michal Marek <mmarek@suse.cz>
To: linux-kbuild@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Paul Gortmaker <paul.gortmaker@windriver.com>,
David Howells <dhowells@redhat.com>
Subject: Re: [PATCH] kbuild: Automatically remove stale <linux/version.h> file
Date: Fri, 28 Nov 2014 16:40:49 +0100 [thread overview]
Message-ID: <54789781.7060009@suse.cz> (raw)
In-Reply-To: <1417102689-19040-1-git-send-email-mmarek@suse.cz>
On 2014-11-27 16:38, Michal Marek wrote:
> In 3.7, the file moved from include/linux/ to
> include/generated/uapi/linux/. The path in the #include directive
> remained the same for compatibility reasons, but this created a problem
> when bisecting. Commit 9c8cdb71 (kbuild: unconditionally clobber
> include/linux/version.h on distclean) fixes this, provided the user does
> make distclean between builds. Better not rely on the user and delete
> the stale file each time make is invoked.
I added this to kbuild.git#kbuild.
Michal
prev parent reply other threads:[~2014-11-28 15:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 15:38 [PATCH] kbuild: Automatically remove stale <linux/version.h> file Michal Marek
2014-11-28 15:40 ` Michal Marek [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=54789781.7060009@suse.cz \
--to=mmarek@suse.cz \
--cc=dhowells@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
/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.