From: Ingo Molnar <mingo@elte.hu>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] x86: disable hpet legacy replacement for kdump
Date: Sun, 2 Dec 2007 17:42:04 +0100 [thread overview]
Message-ID: <20071202164204.GA4898@elte.hu> (raw)
In-Reply-To: <8763zhrqwt.fsf_-_@duaron.myhome.or.jp>
* OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> wrote:
> OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> writes:
>
> > This seems to introduced after 2.6.23, so if possible, I'd like to fix
> > before 2.6.24. What do you think the following?
>
> The following patch fixes the kdump path. Please apply.
thanks, added.
Ingo
prev parent reply other threads:[~2007-12-02 16:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 19:33 [git pull] x86 arch fixes for v2.6.24 Ingo Molnar
2007-11-26 21:42 ` [PATCH] x86: disable hpet legacy replacement for kexec OGAWA Hirofumi
2007-11-26 23:03 ` Ingo Molnar
2007-11-27 18:17 ` Pallipadi, Venkatesh
2007-12-02 16:40 ` [PATCH] x86: disable hpet legacy replacement for kdump OGAWA Hirofumi
2007-12-02 16:42 ` Ingo Molnar [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=20071202164204.GA4898@elte.hu \
--to=mingo@elte.hu \
--cc=hirofumi@mail.parknet.co.jp \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--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