linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: hanjun.guo@linaro.org (Hanjun Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2] ACPI: Update the ownership and developers for ACPI in Kconfig
Date: Tue, 08 Apr 2014 20:21:18 +0800	[thread overview]
Message-ID: <5343E9BE.7030608@linaro.org> (raw)
In-Reply-To: <3442476.Y3PYFAt6A7@vostro.rjw.lan>

Hi Rafael,

On 2014-4-8 20:01, Rafael J. Wysocki wrote:
> On Tuesday, April 08, 2014 07:24:01 PM Hanjun Guo wrote:
>> The UEFI Forum included the ACPI spec in its portfolio in October 2013
>> and will host future spec iterations, following the ACPI v5.0a release.
>>
>> A UEFI Forum working group named ACPI Specification Working Group (ASWG)
>> has been established to handle future ACPI developments, any UEFI member
>> can join the group and contribute to ACPI specification.
>>
>> So update the ownership and developers for ACPI in Kconfig accordingly,
>> and add another website link to ACPI specification too.
>>
>> Signed-off-by: Hanjun Guo <hanjun.guo@linaro.org>
>> ---
>>  drivers/acpi/Kconfig |    4 +++-
>>  1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig
>> index c205653..6bbf36e 100644
>> --- a/drivers/acpi/Kconfig
>> +++ b/drivers/acpi/Kconfig
>> @@ -32,9 +32,11 @@ menuconfig ACPI
>>  	  <http://acpica.org/>
>>  
>>  	  ACPI is an open industry specification co-developed by
>> -	  Hewlett-Packard, Intel, Microsoft, Phoenix, and Toshiba.
>> +	  ACPI Specification Working Group (ASWG) under UEFI Forum, any
>> +	  UEFI member can join ASWG and contribute to ACPI specification.
> 
> Thinking a bit more about that, I'd prefer this wording:
> 
> 	ACPI is an open industry specification originally co-developed by
> 	Hewlett-Packard, Intel, Microsoft, Phoenix, and Toshiba.  Currently,
> 	it is developed by the ACPI Specification Working Group (ASWG) under
> 	the UEFI Forum and any UEFI member can join the ASWG and contribute
> 	to the ACPI specification.

Great, I like your wording very much, will sent another version shortly :)

Thanks
Hanjun

      reply	other threads:[~2014-04-08 12:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-08 11:24 [PATCH V2] ACPI: Update the ownership and developers for ACPI in Kconfig Hanjun Guo
2014-04-08 12:01 ` Rafael J. Wysocki
2014-04-08 12:21   ` Hanjun Guo [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=5343E9BE.7030608@linaro.org \
    --to=hanjun.guo@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).