public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* RFC: moving ACPI includes under include/
@ 2001-08-01 22:40 Grover, Andrew
  2001-08-01 23:55 ` Keith Owens
  0 siblings, 1 reply; 2+ messages in thread
From: Grover, Andrew @ 2001-08-01 22:40 UTC (permalink / raw)
  To: 'linux-kernel@vger.kernel.org'; +Cc: Acpi-linux (E-mail)

The ACPI driver currently has its own little include directory under
drivers/acpi.

...thinking about moving these to include/acpi -- that seems to be the
dominant Linux paradigm. Sound reasonable?

Regards -- Andy

PS general ACPI flames >/dev/null

----------------------------
Andrew Grover
Intel/TRL/Mobile Arch Lab
andrew.grover@intel.com


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: RFC: moving ACPI includes under include/
  2001-08-01 22:40 RFC: moving ACPI includes under include/ Grover, Andrew
@ 2001-08-01 23:55 ` Keith Owens
  0 siblings, 0 replies; 2+ messages in thread
From: Keith Owens @ 2001-08-01 23:55 UTC (permalink / raw)
  To: Grover, Andrew
  Cc: 'linux-kernel@vger.kernel.org', Acpi-linux (E-mail)

On Wed, 1 Aug 2001 15:40:48 -0700 , 
"Grover, Andrew" <andrew.grover@intel.com> wrote:
>The ACPI driver currently has its own little include directory under
>drivers/acpi.
>
>...thinking about moving these to include/acpi -- that seems to be the
>dominant Linux paradigm. Sound reasonable?

Good idea.  SCSI used to have include/scsi but moved the include files
to drivers/scsi and it is obvious that the move was a mistake.  Far too
much code has abominations like #include "../../scsi/hosts.h".  large
enough sub systems should have their own directory under include.


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2001-08-01 23:55 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-08-01 22:40 RFC: moving ACPI includes under include/ Grover, Andrew
2001-08-01 23:55 ` Keith Owens

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox