public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: linux-acpi@vger.kernel.org
Cc: Zhao Yakui <yakui.zhao@intel.com>,
	Alexey Starikovskiy <astarikovskiy@suse.de>
Subject: [PATCH 0/4] ACPI: improve modularity and remove initcalls
Date: Fri, 14 Nov 2008 16:02:43 -0700	[thread overview]
Message-ID: <20081114230117.18623.8172.stgit@bob.kio> (raw)

I'm on a quest to improve modularity and remove initcalls.

When possible, we should avoid initcalls because the order they
happen depends on the module link order, so innocuous makefile
changes can break things.

Yakui, I think I addressed your comments about sysfs duplicate
filenames (I think the link order dependency was removed by
commit 9b473de87209fa86eb421b23386693b461612f30).  But if not,
let me know.

Len, instead of making drivers/acpi/acpi.h, I made a
drivers/acpi/acpi_core.h.  The things in there shouldn't be
visible outside of drivers/acpi, so I don't really want to
put them in include/acpi/acpi_drivers.h.

I also added new pci.h and processor.h header files in drivers/acpi
for those drivers.  You mentioned Bob's ongoing header clean-up,
but I assume he's concentrating on the ACPI CA, whereas the ones
I added are for Linux drivers.

Comments welcome.

Bjorn

             reply	other threads:[~2008-11-14 23:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-14 23:02 Bjorn Helgaas [this message]
2008-11-14 23:02 ` [PATCH 1/4] ACPI: pci: make new pci.h header local to driver Bjorn Helgaas
2008-11-14 23:02 ` [PATCH 2/4] ACPI: processor: make new processor.h " Bjorn Helgaas
2008-11-14 23:02 ` [PATCH 3/4] ACPI: move internal core declaration to private header Bjorn Helgaas
2008-11-14 23:03 ` [PATCH 4/4] ACPI: call core init functions explicitly instead of using initcalls Bjorn Helgaas

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=20081114230117.18623.8172.stgit@bob.kio \
    --to=bjorn.helgaas@hp.com \
    --cc=astarikovskiy@suse.de \
    --cc=linux-acpi@vger.kernel.org \
    --cc=yakui.zhao@intel.com \
    /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