public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Andrew Morton <akpm-3NddpPZAyC0@public.gmane.org>
Cc: ACPI Developers
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	thoenig-l3A5Bk7waGM@public.gmane.org
Subject: Re: [patch 04/12] pcc_acpi build fix
Date: 02 Mar 2005 13:47:09 -0500	[thread overview]
Message-ID: <1109789229.2103.568.camel@d845pe> (raw)
In-Reply-To: <200502230953.j1N9rEUr020699-bipKiLWnuIsyyg0EjBt7GtHuzzzSOjJt@public.gmane.org>

ditto.
I'll not apply this patch b/c I don't plan to add this driver.

Timo,
if you maintain ppc_acpi.c out of tree, you should address this.

thanks,
-Len


On Wed, 2005-02-23 at 04:53, akpm-3NddpPZAyC0@public.gmane.org wrote:
> 
> With older gcc's:
> 
> drivers/acpi/pcc_acpi.c: In function `acpi_pcc_write_sset':
> drivers/acpi/pcc_acpi.c:111: field `integer' already initialized
> drivers/acpi/pcc_acpi.c:111: unknown field `value' specified in
> initializer
> drivers/acpi/pcc_acpi.c:111: warning: excess elements in union
> initializer
> drivers/acpi/pcc_acpi.c:111: warning: (near initialization for
> `in_objs[0]')
> drivers/acpi/pcc_acpi.c:113: field `integer' already initialized
> drivers/acpi/pcc_acpi.c:113: unknown field `value' specified in
> initializer
> drivers/acpi/pcc_acpi.c:113: warning: excess elements in union
> initializer
> drivers/acpi/pcc_acpi.c:113: warning: (near initialization for
> `in_objs[1]')
> 
> 
> Signed-off-by: Andrew Morton <akpm-3NddpPZAyC0@public.gmane.org>
> ---
> 
>  25-akpm/drivers/acpi/pcc_acpi.c |    6 ++----
>  1 files changed, 2 insertions(+), 4 deletions(-)
> 
> diff -puN drivers/acpi/pcc_acpi.c~pcc_acpi-build-fix
> drivers/acpi/pcc_acpi.c
> --- 25/drivers/acpi/pcc_acpi.c~pcc_acpi-build-fix       2005-02-23
> 01:48:02.000000000 -0800
> +++ 25-akpm/drivers/acpi/pcc_acpi.c     2005-02-23 01:48:02.000000000
> -0800
> @@ -107,10 +107,8 @@ static int acpi_pcc_write_sset(struct ac
>  {
>         acpi_status status;
>         union acpi_object in_objs[] = {
> -               { .integer.type  = ACPI_TYPE_INTEGER,
> -                 .integer.value = func, },
> -               { .integer.type  = ACPI_TYPE_INTEGER,
> -                 .integer.value = val, },
> +               { .integer = { .type  = ACPI_TYPE_INTEGER, .value =
> func, }},
> +               { .integer = { .type  = ACPI_TYPE_INTEGER, .value =
> val, }},
>         };
>         struct acpi_object_list params = {
>                 .count   = ARRAY_SIZE(in_objs),
> _
> 
> 



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

      parent reply	other threads:[~2005-03-02 18:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-23  9:53 [patch 04/12] pcc_acpi build fix akpm-3NddpPZAyC0
     [not found] ` <200502230953.j1N9rEUr020699-bipKiLWnuIsyyg0EjBt7GtHuzzzSOjJt@public.gmane.org>
2005-03-02 18:47   ` Len Brown [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=1109789229.2103.568.camel@d845pe \
    --to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=akpm-3NddpPZAyC0@public.gmane.org \
    --cc=thoenig-l3A5Bk7waGM@public.gmane.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