From: Ingo Molnar <mingo@elte.hu>
To: Michael D Labriola <michael.d.labriola@gmail.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Michael D Labriola <mlabriol@gdeb.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86, reboot: reduce to a single DMI table for reboot quirks
Date: Mon, 30 Jan 2012 10:55:37 +0100 [thread overview]
Message-ID: <20120130095537.GA8924@elte.hu> (raw)
In-Reply-To: <87ty3eb9c9.fsf@gmail.com>
I've applied your first two patches, thanks Michael!
Regarding this patch, it does not apply cleanly to the latest
x86 tree:
2 out of 5 hunks FAILED -- rejects in file arch/x86/kernel/reboot.c
which you can pick up from:
git pull git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git master
Also, a style nit, these comments:
> + /* Write zero to CMOS register number 0x0f, which the BIOS POST
> + routine will recognize as telling it to do a proper reboot. (Well
> + that's what this book in front of me says -- it may only apply to
> + the Phoenix BIOS though, it's not clear). At the same time,
> + disable NMIs by setting the top bit in the CMOS address register,
> + as we're about to do peculiar things to the CPU. I'm not sure if
> + `outb_p' is needed instead of just `outb'. Use it to be on the
> + safe side. (Yes, CMOS_WRITE does outb_p's. - Paul G.)
> + */
and the other similar comments that you move should be coverted
to the customary (multi-line) comment style:
/*
* Comment .....
* ...... goes here.
*/
specified in Documentation/CodingStyle.
I realize that you only move code here - but it's worth cleaning
it up a bit when touching it.
Thanks,
Ingo
next parent reply other threads:[~2012-01-30 9:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ty3eb9c9.fsf@gmail.com>
2012-01-30 9:55 ` Ingo Molnar [this message]
2012-01-30 13:36 ` [PATCH] x86, reboot: reduce to a single DMI table for reboot quirks Michael D Labriola
2012-01-30 13:42 ` Ingo Molnar
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=20120130095537.GA8924@elte.hu \
--to=mingo@elte.hu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.d.labriola@gmail.com \
--cc=mlabriol@gdeb.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.