From: Michal Marek <mmarek@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: mmarek@suse.cz, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, sfr@canb.auug.org.au
Subject: [GIT] kbuild anticipatory fix
Date: Mon, 21 Feb 2011 15:20:36 +0100 [thread overview]
Message-ID: <20110221142036.GA3583@sepie.suse.cz> (raw)
Hi Linus,
Commit 9599ec0 in the tip tree is going to replace
arch/x86/lib/memmove_64.c with arch/x86/lib/memmove_64.S, which breaks
build if one does not run 'make clean' after merging that commit. While
this is not a regression, the kbuild fix is rather simple and will avoid
the annoyance in the merge window if merged now. Please consider.
Michal
The following changes since commit 85e2efbb1db9a18d218006706d6e4fbeb0216213:
Linux 2.6.38-rc5 (2011-02-15 19:23:45 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild-2.6.git rc-fixes
Michal Marek (1):
fixdep: Do not record dependency on the source file itself
scripts/basic/fixdep.c | 12 +++++++++++-
1 files changed, 11 insertions(+), 1 deletions(-)
reply other threads:[~2011-02-21 14:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20110221142036.GA3583@sepie.suse.cz \
--to=mmarek@suse.cz \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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