public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kristen Accardi <kristen.c.accardi@intel.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	len.brown@intel.com, greg@kroah.com
Subject: Re: [patch] fix pciehp compile issue when CONFIG_ACPI is not enabled.
Date: Mon, 08 May 2006 12:39:43 -0700	[thread overview]
Message-ID: <1147117183.3094.16.camel@whizzy> (raw)
In-Reply-To: <20060508192431.GB7235@mipter.zuzino.mipt.ru>

On Mon, 2006-05-08 at 23:24 +0400, Alexey Dobriyan wrote:
> On Mon, May 08, 2006 at 11:54:30AM -0700, Kristen Accardi wrote:
> > Fix compile error when CONFIG_ACPI is not defined.
> 
> > --- 2.6-git.orig/include/acpi/actypes.h
> > +++ 2.6-git/include/acpi/actypes.h
> > @@ -348,6 +348,7 @@ struct acpi_pointer {
> >   * Mescellaneous types
> >   */
> >  typedef u32 acpi_status;	/* All ACPI Exceptions */
> > +#define acpi_status acpi_status
> >  typedef u32 acpi_name;		/* 4-byte ACPI name */
> >  typedef char *acpi_string;	/* Null terminated ASCII string */
> >  typedef void *acpi_handle;	/* Actually a ptr to a NS Node */
> 
> The following in include/linux/pci-acpi.h is ugly
> 
> 	#if !defined(acpi_status)
> 	typedef u32             acpi_status;
> 	#define AE_ERROR        (acpi_status) (0x0001)
> 	#endif
> 
> but you're adding more of it.

The actual solution to the problem is long.  acpi_status should not be
used outside of acpi-ca.  However, it is.  In many, many places.  The
real solution is to go around and re-write all the apis that export
acpi_status to drivers, and then fix all the drivers which rely on
acpi_status (and other acpi-caisms ).  This fix, while ugly, solves the
immediate problem in an expedient way.  However, I'm certainly open to
suggestions about nicer ways to do it.

  reply	other threads:[~2006-05-08 19:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-08 18:54 [patch] fix pciehp compile issue when CONFIG_ACPI is not enabled Kristen Accardi
2006-05-08 19:24 ` Alexey Dobriyan
2006-05-08 19:39   ` Kristen Accardi [this message]
2006-05-08 20:22   ` Kristen Accardi

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=1147117183.3094.16.camel@whizzy \
    --to=kristen.c.accardi@intel.com \
    --cc=adobriyan@gmail.com \
    --cc=greg@kroah.com \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --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