From: Andi Kleen <ak@suse.de>
To: "Amit S. Kale" <amitkale@emsyssoft.com>
Cc: pavel@ucw.cz, akale@users.sourceforge.net,
linux-kernel@vger.kernel.org,
kgdb-bugreport@lists.sourceforge.net, jim.houston@ccur.com,
trini@kernel.crashing.org
Subject: Re: hweight64
Date: Wed, 18 Feb 2004 02:39:21 +0100 [thread overview]
Message-ID: <20040218023921.60d8a037.ak@suse.de> (raw)
In-Reply-To: <200402171655.44006.amitkale@emsyssoft.com>
On Tue, 17 Feb 2004 16:55:43 +0530
"Amit S. Kale" <amitkale@emsyssoft.com> wrote:
> Hi Pavel and kgdb gurus,
>
> I inherited this change from x86_64 patch. Probably it was required on x86_64.
> I can't think of any reason why it is necessary.
>
> Unless someone finds a problem with this patch, I am going to apply it.
You can just remove it. It's not needed. kgdb does not even use hweight*
I checked some time ago with Jim Houston (from which it originated) and he said
it was a merging error leaking from some Concurrent internal tree.
-Andi
prev parent reply other threads:[~2004-02-17 11:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 10:34 hweight64 Pavel Machek
2004-02-17 11:25 ` hweight64 Amit S. Kale
2004-02-18 1:39 ` Andi Kleen [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=20040218023921.60d8a037.ak@suse.de \
--to=ak@suse.de \
--cc=akale@users.sourceforge.net \
--cc=amitkale@emsyssoft.com \
--cc=jim.houston@ccur.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=trini@kernel.crashing.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.