From: "H. Peter Anvin" <hpa@zytor.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Borislav Petkov <bp@amd64.org>, Borislav Petkov <bp@alien8.de>,
"user-mode-linux-devel@lists.sourceforge.net"
<user-mode-linux-devel@lists.sourceforge.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86, hweight: Fix UML boot crash
Date: Mon, 14 Jun 2010 08:20:13 -0700 [thread overview]
Message-ID: <4C1648AD.5020607@zytor.com> (raw)
In-Reply-To: <201006141711.26975.toralf.foerster@gmx.de>
On 06/14/2010 08:11 AM, Toralf Förster wrote:
>
> Geert Uytterhoeven wrote at 16:39:00
>> I assume you did a `make clean' in between?
> ...
>> BTW, I'm also using ccache. Always. Ever. All my (cross)compilers are
> Well, I'm unsure - might be I made that mistake, especially b/c I use ccache
> too since years and didn't experienced any fault so far.
I have certainly seen a number of cases where ccache doesn't pick up
sublte differences, for reasons unknown.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2010-06-14 15:21 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 17:44 current git kernel crashes UML system during boot Toralf Förster
2010-05-30 11:39 ` Geert Uytterhoeven
2010-05-30 11:57 ` Geert Uytterhoeven
2010-05-30 15:02 ` Borislav Petkov
2010-05-30 15:18 ` Geert Uytterhoeven
2010-05-30 15:46 ` Borislav Petkov
2010-05-30 15:28 ` Toralf Förster
2010-05-30 17:03 ` [PATCH] x86, hweight: Fix UML boot crash Borislav Petkov
2010-05-30 18:36 ` H. Peter Anvin
2010-05-30 19:39 ` Borislav Petkov
2010-05-30 20:17 ` Borislav Petkov
2010-05-30 21:09 ` H. Peter Anvin
2010-06-12 13:34 ` [uml-devel] " Paolo Giarrusso
2010-06-12 14:18 ` Borislav Petkov
2010-06-12 16:01 ` Paolo Giarrusso
2010-06-12 16:34 ` Borislav Petkov
2010-06-12 18:37 ` Geert Uytterhoeven
2010-06-13 6:58 ` Borislav Petkov
2010-05-31 13:55 ` Toralf Förster
2010-05-31 14:10 ` Borislav Petkov
2010-05-31 14:36 ` Toralf Förster
2010-06-14 9:49 ` Toralf Förster
2010-06-14 10:26 ` [uml-devel] " Paolo Giarrusso
2010-06-14 12:54 ` Toralf Förster
2010-06-14 13:00 ` Borislav Petkov
2010-06-14 13:44 ` Toralf Förster
2010-06-14 14:39 ` Geert Uytterhoeven
2010-06-14 15:11 ` Toralf Förster
2010-06-14 15:20 ` H. Peter Anvin [this message]
2010-05-31 14:25 ` [uml-devel] " Boaz Harrosh
2010-05-31 2:32 ` Jeff Dike
2010-05-31 13:51 ` Borislav Petkov
2010-05-31 15:56 ` Jeff Dike
2010-05-31 16:29 ` Borislav Petkov
[not found] ` <tip-cc7f0a7b3004a4ca0bfef0e1ca79f2e0da6ca1b0@git.kernel.org>
2010-06-09 22:43 ` [tip:x86/urgent] " H. Peter Anvin
2010-06-10 5:32 ` Geert Uytterhoeven
2010-06-10 6:26 ` H. Peter Anvin
2010-06-09 8:04 ` [PATCH resend] um, " Boaz Harrosh
2010-06-09 8:09 ` [uml-devel] " Boaz Harrosh
2010-06-09 8:46 ` Geert Uytterhoeven
2010-06-09 9:08 ` Boaz Harrosh
2010-06-09 9:32 ` Américo Wang
2010-06-09 18:29 ` H. Peter Anvin
2010-06-14 16:08 ` Boaz Harrosh
2010-06-14 16:41 ` H. Peter Anvin
2010-06-14 18:18 ` Boaz Harrosh
2010-06-09 16:39 ` Boaz Harrosh
2010-06-10 23:43 ` [tip:x86/urgent] um, hweight: Fix UML boot crash due to x86 optimized hweight tip-bot for Borislav Petkov
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=4C1648AD.5020607@zytor.com \
--to=hpa@zytor.com \
--cc=bp@alien8.de \
--cc=bp@amd64.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=toralf.foerster@gmx.de \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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
Powered by JetHome