From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Lukas Wunner <lukas@wunner.de>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Darren Hart <dvhart@infradead.org>, Lv Zheng <lv.zheng@intel.com>,
Robert Moore <robert.moore@intel.com>,
platform-driver-x86@vger.kernel.org, "Lee,
Chun-Yi" <jlee@suse.com>,
Corentin Chary <corentin.chary@gmail.com>,
acpi4asus-user@lists.sourceforge.net,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH 0/2] Use acpi_dev_present()
Date: Wed, 9 Mar 2016 23:21:18 +0100 [thread overview]
Message-ID: <CAJZ5v0gRYiWDSd-hgMPiBEAOEif8sdc-W=Ot5fibPUMv_EE+Jg@mail.gmail.com> (raw)
In-Reply-To: <20160211183157.GA15803@wunner.de>
On Thu, Feb 11, 2016 at 7:31 PM, Lukas Wunner <lukas@wunner.de> wrote:
> Hi Rafael,
>
> thanks a lot for your patience.
>
> On Tue, Jan 19, 2016 at 10:59:04PM +0100, Rafael J. Wysocki wrote:
>> On Tuesday, January 19, 2016 01:12:29 PM Darren Hart wrote:
>> > On Sun, Jan 17, 2016 at 09:49:41PM +0100, Lukas Wunner wrote:
>> > > Hi Darren,
>> > >
>> > > the acpi_dev_present() API has now landed in Linus' tree.
>> > > Thus, after Linus' tree gets merged back into yours,
>> > > it would be possible to use the API in the pdx86 drivers
>> > > as per the following patches.
>> > >
>> > > I've also pushed these to GitHub in case anyone prefers
>> > > perusing them in a browser:
>> > > https://github.com/l1k/linux/commits/acpi_dev_present_pdx86
>> > >
>> > > This is a repost of patches submitted in November, the only
>> > > change is one line added to the commit messages to reference
>> > > the commit which introduces the API:
>> > > http://thread.gmane.org/gmane.linux.alsa.devel/147414/focus=8004
>> > > http://thread.gmane.org/gmane.linux.alsa.devel/147414/focus=8005
>> >
>> > Who's tree did the API make it in through? That would likely be the best tree to
>> > pull these 2 patches in from.
>> >
>> > Robert, Lv, Rafael? Would one of you prefer to take these 2 patches using the
>> > new API?
>>
>> It was my tree and I can take these patches, but in that case I'd like the
>> function's name to be changed as discussed elsewhere.
>>
>> Executive summary is that we have acpi_dev_present() and acpi_device_is_present()
>> now and they serve different purposes which is kind of confusing. Moreover,
>> acpi_dev_present() doesn't check if the device is actually present, so
>> I would like it to be renamed to acpi_device_found() or similar.
>
> There are 4 users of acpi_dev_present in linux-next (3 in sound/soc/intel/,
> 1 in include/linux/apple-gmux.h). I expect 1 other user to appear in i915.
>
> I've created a patch (based on linux-next and included below as an RFC)
> to rename acpi_dev_present to acpi_dev_found in the function declaration
> as well as at all call sites. I've also rebased the 2 pdx86 patches onto
> this and pushed the branch to GitHub:
> https://github.com/l1k/linux/commits/acpi_dev_found
>
> My plan is currently to wait until all users are merged into 4.6,
> then rebase my branch onto Linus' tree and post the resulting patches.
> This will be either late during the 4.6 merge window or immediately
> after it has closed. You could then either pick up the patches for
> 4.6 or 4.7, whichever you prefer.
>
> If you'd prefer a different way of moving forward or would like
> something changed in the patch below, please let me know and
> I will be happy to adjust accordingly.
Thanks for doing this!
Your plan seems workable to me, so please go ahead with it.
Thanks,
Rafael
next prev parent reply other threads:[~2016-03-09 22:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1453060661.git.lukas@wunner.de>
[not found] ` <20160119211229.GB3253@malice.jf.intel.com>
[not found] ` <5367662.pAQ7mO39ru@vostro.rjw.lan>
2016-02-11 18:31 ` [PATCH 0/2] Use acpi_dev_present() Lukas Wunner
2016-03-09 22:21 ` Rafael J. Wysocki [this message]
2016-03-12 17:31 ` Lukas Wunner
2016-03-13 1:50 ` Rafael J. Wysocki
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='CAJZ5v0gRYiWDSd-hgMPiBEAOEif8sdc-W=Ot5fibPUMv_EE+Jg@mail.gmail.com' \
--to=rafael@kernel.org \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=corentin.chary@gmail.com \
--cc=dvhart@infradead.org \
--cc=jlee@suse.com \
--cc=linux-acpi@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=lv.zheng@intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=robert.moore@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;
as well as URLs for NNTP newsgroup(s).