From: Keith Owens <kaos@ocs.com.au>
To: "Grover, Andrew" <andrew.grover@intel.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"Acpi-linux (E-mail)" <acpi@phobos.fachschaften.tu-muenchen.de>
Subject: Re: RFC: moving ACPI includes under include/
Date: Thu, 02 Aug 2001 09:55:03 +1000 [thread overview]
Message-ID: <19806.996710103@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Wed, 01 Aug 2001 15:40:48 MST." <4148FEAAD879D311AC5700A0C969E89006CDE006@orsmsx35.jf.intel.com>
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.
prev parent reply other threads:[~2001-08-01 23:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-01 22:40 RFC: moving ACPI includes under include/ Grover, Andrew
2001-08-01 23:55 ` Keith Owens [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=19806.996710103@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=acpi@phobos.fachschaften.tu-muenchen.de \
--cc=andrew.grover@intel.com \
--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