public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown@intel.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: ACPI Developers <acpi-devel@lists.sourceforge.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] #ifdef ACPI_FUTURE_USAGE acpi_ut_create_pkg_state_and_push
Date: 27 Jan 2005 18:18:34 -0500	[thread overview]
Message-ID: <1106867914.2395.2321.camel@d845pe> (raw)
In-Reply-To: <20050127110443.GF28047@stusta.de>

Applied.

thanks,
-Len

On Thu, 2005-01-27 at 06:04, Adrian Bunk wrote:
> The prototype of the unused global function
> acpi_ut_create_pkg_state_and_push was already #ifdef
> ACPI_FUTURE_USAGE'd, but the actual function wasn't.
> 
> Most likely this was a bug in my patch that added
> ACPI_FUTURE_USAGE.
> 
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
> 
> ---
> linux-2.6.11-rc2-mm1-full/drivers/acpi/utilities/utmisc.c.old      
> 2005-01-26 22:31:11.000000000 +0100
> +++ linux-2.6.11-rc2-mm1-full/drivers/acpi/utilities/utmisc.c  
> 2005-01-26 22:40:40.000000000 +0100
> @@ -872,7 +885,7 @@
>   * DESCRIPTION: Create a new state and push it
>   *
>  
> ******************************************************************************/
> -
> +#ifdef ACPI_FUTURE_USAGE
>  acpi_status
>  acpi_ut_create_pkg_state_and_push (
>         void                            *internal_object,
> @@ -894,7 +907,7 @@
>         acpi_ut_push_generic_state (state_list, state);
>         return (AE_OK);
>  }
> -
> +#endif  /*  ACPI_FUTURE_USAGE  */
> 
>  /*******************************************************************************
>   *
> 
> 
> 

      reply	other threads:[~2005-01-27 23:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-27 11:04 [2.6 patch] #ifdef ACPI_FUTURE_USAGE acpi_ut_create_pkg_state_and_push Adrian Bunk
2005-01-27 23:18 ` 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=1106867914.2395.2321.camel@d845pe \
    --to=len.brown@intel.com \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.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