From: Joe Perches <joe@perches.com>
To: Toshi Kani <toshi.kani@hp.com>
Cc: linux-acpi@vger.kernel.org, rjw@sisk.pl, lenb@kernel.org,
linux-kernel@vger.kernel.org, bhelgaas@google.com,
isimatu.yasuaki@jp.fujitsu.com, vijaymohan.pandarathil@hp.com,
imammedo@redhat.com, prarit@redhat.com
Subject: Re: [PATCH v5 RESEND 1/5] ACPI: Add acpi_pr_<level>() interfaces
Date: Mon, 19 Nov 2012 08:06:32 -0800 [thread overview]
Message-ID: <1353341192.5287.9.camel@joe-AO722> (raw)
In-Reply-To: <1353340280.10939.42.camel@misato.fc.hp.com>
On Mon, 2012-11-19 at 08:51 -0700, Toshi Kani wrote:
> On Mon, 2012-11-19 at 00:56 -0800, Joe Perches wrote:
> > is acpi_bus.h really the right file for these prototypes?
> This interface is limited for ACPI, so it should be declared in a header
> file under include/acpi. Among the files in this directory, acpi_bus.h
> seems to be a good fit as it declares the interfaces provided by ACPI
> core.
I'd've put them in acpi.h or maybe created acpi_utils.h
cheers, Joe
next prev parent reply other threads:[~2012-11-19 16:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 15:02 [PATCH v5 RESEND 0/5] ACPI: hotplug messages improvement Toshi Kani
2012-11-06 15:02 ` [PATCH v5 RESEND 1/5] ACPI: Add acpi_pr_<level>() interfaces Toshi Kani
2012-11-19 8:10 ` Rafael J. Wysocki
2012-11-19 15:37 ` Toshi Kani
2012-11-20 1:17 ` Rafael J. Wysocki
2012-11-20 1:18 ` Toshi Kani
2012-11-19 8:56 ` Joe Perches
2012-11-19 15:51 ` Toshi Kani
2012-11-19 16:06 ` Joe Perches [this message]
2012-11-19 16:16 ` Toshi Kani
2012-11-19 17:35 ` Rafael J. Wysocki
2012-11-19 17:26 ` Toshi Kani
2012-11-20 1:04 ` Rafael J. Wysocki
2012-11-20 1:26 ` Toshi Kani
2012-11-06 15:02 ` [PATCH v5 RESEND 2/5] ACPI: Update CPU hotplug error messages Toshi Kani
2012-11-06 15:02 ` [PATCH v5 RESEND 3/5] ACPI: Update Memory " Toshi Kani
2012-11-06 15:02 ` [PATCH v5 RESEND 4/5] ACPI: Update Container " Toshi Kani
2012-11-06 15:02 ` [PATCH v5 RESEND 5/5] ACPI: Update Dock " Toshi Kani
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=1353341192.5287.9.camel@joe-AO722 \
--to=joe@perches.com \
--cc=bhelgaas@google.com \
--cc=imammedo@redhat.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prarit@redhat.com \
--cc=rjw@sisk.pl \
--cc=toshi.kani@hp.com \
--cc=vijaymohan.pandarathil@hp.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
all inboxes | Powered by JetHome®