From: Ingo Molnar <mingo@elte.hu>
To: Len Brown <lenb@kernel.org>
Cc: x86@kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
linux-acpi@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] x86/hpet: prevent boot hang when hpet=force used on old ICH
Date: Sat, 25 Apr 2009 01:45:02 +0200 [thread overview]
Message-ID: <20090424234502.GF6403@elte.hu> (raw)
In-Reply-To: <alpine.LFD.2.00.0904231901570.15843@localhost.localdomain>
* Len Brown <lenb@kernel.org> wrote:
> Ingo,
> Thanks for the reply.
>
> But please disregard that patch -- we've cooked up a better one
> that allows ICH4M to continue to use hpet=force, even for clocksource.
> (and it is an ACPI patch rather than an x86 patch:-)
ok.
> However, I'll also send a 2nd patch to stop soliciting more
> hpet=force users, since technically we shouldn't be encouraging
> the use of this un-documented and lightly-validated hardware.
agreed - i've applied this patch.
Ingo
next prev parent reply other threads:[~2009-04-24 23:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 2:27 [PATCH] x86/hpet: prevent boot hang when hpet=force used on old ICH Len Brown
2009-04-23 6:09 ` Ingo Molnar
2009-04-23 23:05 ` Len Brown
2009-04-24 23:45 ` Ingo Molnar [this message]
2009-04-23 23:18 ` [PATCH] ACPI/hpet: prevent boot hang when hpet=force used on ICH-4M Len Brown
2009-04-23 23:18 ` Pallipadi, Venkatesh
2009-04-23 23:19 ` [PATCH] HPET: stop soliciting hpet=force users on ICH4M Len Brown
2009-04-23 23:19 ` Pallipadi, Venkatesh
2009-04-24 6:43 ` Ingo Molnar
2009-04-24 6:37 ` [PATCH] ACPI/hpet: prevent boot hang when hpet=force used on ICH-4M Ingo Molnar
2009-04-24 14:49 ` Len Brown
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=20090424234502.GF6403@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).