[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7233d29e-ea01-4eb6-8018-b9c8e3730a30@email.android.com>
Date: Wed, 21 Aug 2013 11:07:48 +0200
From: "H. Peter Anvin" <hpa@...or.com>
To: "Li, Fei" <fei.li@...el.com>, Ingo Molnar <mingo@...nel.org>
CC: "mingo@...hat.com" <mingo@...hat.com>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"Liu, Chuansheng" <chuansheng.liu@...el.com>,
"x86@...nel.org" <x86@...nel.org>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"holt@....com" <holt@....com>,
"rmk+kernel@....linux.org.uk" <rmk+kernel@....linux.org.uk>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] reboot: perform warm/cold reset correctly for CF9 type
The thing is that the existing "warm" and "cold" means something different, I believe (skip post vs do post.) It is possible it just works, but it would be good to know which platforms or works on.
Also, why do you need the cf9 boot method at all? All current systems * should * use the ACPI method.
"Li, Fei" <fei.li@...el.com> wrote:
>> Careful. This is a very different definition of warm vs cold boot
>used elsewhere.
>
>We have tested both warm and cold reboot on our x86 platform, and it
>works well.
>Besides with commit, the expected warm and reboot type can be specified
>through
>command line.
>
>> >Looks good, but please introduce a reboot_val intermediate
>> >variable instead of duplicating that ugly line-broken
>> >construct twice.
>
>Accepted and will update it in later version.
>
>> >
>> >Thanks,
>> >
>> > Ingo
>>
>
>Thanks,
>Fei
--
Sent from my mobile phone. Please excuse brevity and lack of formatting.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists