From: Darren Hart <dvhart@infradead.org>
To: Kast Bernd <kastbernd@gmx.de>
Cc: corentin.chary@gmail.com, rjw@rjwysocki.net, lenb@kernel.org,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
acpi4asus-user@lists.sourceforge.net,
platform-driver-x86@vger.kernel.org
Subject: Re: [RFC 1/2] ACPI: activate&export acpi_os_get_physical_address
Date: Thu, 30 Apr 2015 11:10:25 -0700 [thread overview]
Message-ID: <20150430181025.GC40200@fury.dvhart.com> (raw)
In-Reply-To: <f14ffb9df15cdf617bb4ccae575a9787866675c8.1429653764.git.kastbernd@gmx.de>
On Wed, Apr 22, 2015 at 04:12:24PM +0200, Kast Bernd wrote:
> acpi_os_get_physical_address will be needed by an acpi driver (asus-wmi.c).
> Additionally it could be used by dell-laptop.c instead of directly calling virt_to_phys.
>
> acpi_os_get_physical_address gets exported and ACPI_FUTURE_USAGE is removed
>
Hrm, well... this doesn't get rid of virt_to_phys, it just wraps it really. I'm
not sure that makes this any more acceptable than the original from Felipe - but
that's not my call.
Rafael?
Len?
--
Darren Hart
Intel Open Source Technology Center
next prev parent reply other threads:[~2015-04-30 18:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 14:12 [RFC 0/2] asus notebook fan control Kast Bernd
2015-04-22 14:12 ` [RFC 2/2] asus-wmi: add " Kast Bernd
2015-04-30 18:42 ` Darren Hart
2015-05-02 12:37 ` Corentin Chary
2015-04-22 14:12 ` [RFC 1/2] ACPI: activate&export acpi_os_get_physical_address Kast Bernd
2015-04-30 18:10 ` Darren Hart [this message]
2015-05-01 1:32 ` Rafael J. Wysocki
2015-05-01 1:45 ` Rafael J. Wysocki
2015-05-01 4:56 ` Matthew Garrett
2015-05-03 17:57 ` Darren Hart
2015-04-30 18:00 ` [RFC 0/2] asus notebook fan control Darren Hart
2015-05-04 22:58 ` [RFC v2] asus-wmi: add " Kast Bernd
2015-05-05 19:48 ` Darren Hart
2015-05-10 21:12 ` [RFC v3] " Kast Bernd
2015-05-11 17:55 ` Darren Hart
2015-05-12 22:09 ` [RFC v4] " Kast Bernd
2015-05-13 8:21 ` Corentin Chary
2015-05-13 14:24 ` [RFC v5] " Kast Bernd
2015-05-13 18:08 ` Darren Hart
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=20150430181025.GC40200@fury.dvhart.com \
--to=dvhart@infradead.org \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=corentin.chary@gmail.com \
--cc=kastbernd@gmx.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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