linux-kernel - Re: [PATCH 0/5] ACPI: Add _OST support for ACPI hotplug

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1334600656.20190.139.camel@misato.fc.hp.com>
Date:	Mon, 16 Apr 2012 12:24:16 -0600
From:	Toshi Kani <toshi.kani@...com>
To:	shuahkhan@...il.com
Cc:	Jiang Liu <liuj97@...il.com>, lenb@...nel.org,
	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/5] ACPI: Add _OST support for ACPI hotplug

On Fri, 2012-04-13 at 12:34 -0600, Shuah Khan wrote:
> > I would like to explain more detail about my testing.  Unlike other ACPI
> > methods, the functionality of _OST method is not defined by the spec.
> > It is all up to the firmware implementation.  
> 
> A good reason why this patch requires more testing than on simulated
> firmware code that is based on one single firmware implementation.

Thanks Shuah for the guidance.  Do they summarize your point properly?

1. Testing a new feature on simulated / virtualized environment alone is
not sufficient.

2. Pre-enablement of a new feature is not allowed.

3. Contributing code that supports a new feature shall wait until there
are multiple firmware implementations available for the testing.

I like clear guidance, but this may be challenging for emerging
features.
-Toshi 


--
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/