From: "H. Peter Anvin" <hpa@zytor.com>
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
tglx@linutronix.de, mingo@redhat.com, x86@kernel.org
Subject: Re: 2.6.32: x86_32: Destination address is too large.
Date: Thu, 17 Dec 2009 07:08:13 -0800 [thread overview]
Message-ID: <4B2A495D.6050605@zytor.com> (raw)
In-Reply-To: <a4423d670912170649g57137b18n6bc1419b584c44c1@mail.gmail.com>
On 12/17/2009 06:49 AM, Alexander Beregalov wrote:
> Config for 2.6.32 is attached
Actually, could you please send me you bzImage file?
-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:[~2009-12-17 15:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 13:36 2.6.32: x86_32: Destination address is too large Alexander Beregalov
2009-12-17 14:49 ` Alexander Beregalov
2009-12-17 15:08 ` H. Peter Anvin [this message]
2009-12-17 14:54 ` H. Peter Anvin
2009-12-17 14:55 ` H. Peter Anvin
2009-12-22 18:51 ` H. Peter Anvin
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=4B2A495D.6050605@zytor.com \
--to=hpa@zytor.com \
--cc=a.beregalov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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