public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Michael D Labriola <mlabriol@gdeb.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Kushal Koolwal <kushalkoolwal@gmail.com>,
	linux-kernel@vger.kernel.org, michael.d.labriola@gmail.com,
	Matthew Garrett <mjg59@srcf.ucam.org>,
	support@versalogic.com, Thomas Gleixner <tglx@linutronix.de>,
	x86@kernel.org
Subject: Re: [PATCH] x86, reboot: skip DMI checks if reboot set by user
Date: Thu, 19 Jan 2012 20:41:08 +0100	[thread overview]
Message-ID: <20120119194108.GB28362@elte.hu> (raw)
In-Reply-To: <OFE1B368BB.B6249713-ON8525798A.00692513-8525798A.0069B44E@gdeb.com>


* Michael D Labriola <mlabriol@gdeb.com> wrote:

> > Yes, and such a patch would be appreciated.
> > 
> > The reason it is as it is dates back to before the 32-64 bit 
> > unification, as far as I know.
> > 
> > (BIOS reboot is currently not supported on 64 bits, mainly.)
> 
> Well, that does complicate it a bit.  I'll gin something up 
> and see what you think.  I guess it will involve having an
> #ifdef CONFIG_X86_32 block inside a single dmi_table structure
> for the BIOS quirks.

Btw., i'd suggest to keep the two changes in separate patches, 
so that if any causes problems we can bisect to it separately. 
The more patches you can reasonably split it up into, the 
better.

Thanks,

	Ingo

      parent reply	other threads:[~2012-01-19 19:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-17 15:16 [PATCH] x86, reboot: skip DMI checks if reboot set by user Michael D Labriola
2012-01-17 19:58 ` Alan Cox
2012-01-19 15:32   ` Michael D Labriola
2012-01-19 15:45     ` Alan Cox
2012-01-19 15:48       ` Michael D Labriola
     [not found]       ` <OF8642E997.5ED041E1-ON8525798A.0056983A-8525798A.0056E05B@LocalDomain>
2012-01-19 17:46         ` Michael D Labriola
2012-01-19 17:52           ` H. Peter Anvin
2012-01-19 19:14             ` Michael D Labriola
2012-01-19 19:17               ` H. Peter Anvin
2012-01-19 19:34                 ` Michael D Labriola
2012-01-19 19:41               ` 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=20120119194108.GB28362@elte.hu \
    --to=mingo@elte.hu \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hpa@zytor.com \
    --cc=kushalkoolwal@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.d.labriola@gmail.com \
    --cc=mjg59@srcf.ucam.org \
    --cc=mlabriol@gdeb.com \
    --cc=support@versalogic.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