public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Christian Hofstaedtler <ch@zeha.at>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, tglx@linutronix.de, linux-acpi@vger.kernel.org,
	venkatesh.pallipadi@intel.com, arjan@infradead.org,
	bruce.w.allan@intel.com
Subject: Re: [PATCH] Default to ACPI reboots on newish X86 hardware
Date: Wed, 06 Jan 2010 14:38:33 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.00.1001061433260.4086@localhost.localdomain> (raw)
In-Reply-To: <201001051926.30580.ch@zeha.at>

> Also, I think we could push the year even more up, say, to 2009. On the 
> assumption that such new hardware which can't do BOOT_KBD is only being 
> produced now (late 2009). Better err on the safe side?

I'd prefer sticking with 2006 so we don't need a white-list for
brand-new machines.

Indeed, I think that 2006 is already conservative,
and I'd be willing to debug failures on machines back as far as 2003.

thanks,
-Len Brown, Intel Open Source Technology Center



  parent reply	other threads:[~2010-01-06 19:38 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100104162114.GA30113@percival.namespace.at>
2010-01-04 17:15 ` [PATCH] Add DMI quirk for Intel DP55KG mainboard Len Brown
2010-01-04 17:30   ` H. Peter Anvin
2010-01-04 22:03     ` Len Brown
2010-01-05  2:15       ` Robert Hancock
2010-01-05  3:37         ` H. Peter Anvin
2010-01-05 12:30           ` [PATCH] Default to ACPI reboots on newish X86 hardware Christian Hofstaedtler
2010-01-05 17:04             ` H. Peter Anvin
2010-01-05 18:26               ` Christian Hofstaedtler
2010-01-06  6:06                 ` H. Peter Anvin
2010-01-06 19:38                 ` Len Brown [this message]
2010-01-07 20:03                   ` Christian Hofstaedtler
2010-01-07 20:05                     ` Christian Hofstaedtler
2010-01-07 23:05                     ` H. Peter Anvin
2010-01-20  5:21                     ` Len Brown
2010-01-21 17:18                       ` [PATCH 1/2] x86: Unify reboot_type selection Christian Hofstaedtler
2010-01-21 17:18                         ` [PATCH 2/2] Default to ACPI reboots on newish X86 hardware Christian Hofstaedtler
2010-01-23 19:57                           ` Len Brown
2010-01-21 18:29                         ` [PATCH 1/2] x86: Unify reboot_type selection H. Peter Anvin
2010-01-21 17:24                       ` [PATCH] Default to ACPI reboots on newish X86 hardware Christian Hofstaedtler
2010-01-05  1:45     ` [PATCH] Add DMI quirk for Intel DP55KG mainboard Arjan van de Ven
2010-01-06 14:36       ` Matthew Garrett
2010-01-06 19:26         ` Len Brown
2010-01-06 19:36           ` Matthew Garrett
2010-01-06 20:22             ` Len Brown
2010-01-06 20:29               ` Matthew Garrett
2010-01-06 21:26               ` H. Peter Anvin
2010-01-20  5:06                 ` Len Brown
2010-01-07  1:15               ` Robert Hancock
2010-01-06  7:41   ` Pavel Machek
2010-01-06 14:51     ` Alan Cox

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=alpine.LFD.2.00.1001061433260.4086@localhost.localdomain \
    --to=lenb@kernel.org \
    --cc=arjan@infradead.org \
    --cc=bruce.w.allan@intel.com \
    --cc=ch@zeha.at \
    --cc=hpa@zytor.com \
    --cc=linux-acpi@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