From: Sinan Kaya <okaya@codeaurora.org>
To: Vinod Koul <vinod.koul@intel.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: dmaengine@vger.kernel.org, timur@codeaurora.org,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org, robin.murphy@arm.com,
linux-kernel@vger.kernel.org,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH V3 2/4] ACPI / bus: introduce acpi_device_get_match_data() function
Date: Wed, 29 Nov 2017 15:49:26 -0500 [thread overview]
Message-ID: <7a89f75e-d740-9252-419a-58a7b26b0df2@codeaurora.org> (raw)
In-Reply-To: <20171129135536.GD32417@localhost>
On 11/29/2017 8:55 AM, Vinod Koul wrote:
>> While I understand that the name follows the OF convention, I have some
>> doubts on whether it is the best one.
> Perhpas acpi_get_match_data() ?
Will change as recommended unless Rafael has a better idea.
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2017-11-29 20:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 2:32 [PATCH V3 1/4] Documentation: DT: qcom_hidma: bump HW revision for the bugfixed HW Sinan Kaya
2017-11-10 2:32 ` [PATCH V3 2/4] ACPI / bus: introduce acpi_device_get_match_data() function Sinan Kaya
2017-11-10 2:35 ` Sinan Kaya
2017-11-12 0:14 ` Rafael J. Wysocki
2017-11-29 13:55 ` Vinod Koul
2017-11-29 20:49 ` Sinan Kaya [this message]
2017-11-10 2:32 ` [PATCH V3 3/4] dmaengine: qcom_hidma: add support for the new revision Sinan Kaya
2017-11-29 13:58 ` Vinod Koul
2017-11-29 22:14 ` Sinan Kaya
2017-11-10 2:32 ` [PATCH V3 4/4] dmaengine: qcom_hidma: add identity register support Sinan Kaya
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=7a89f75e-d740-9252-419a-58a7b26b0df2@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=robin.murphy@arm.com \
--cc=timur@codeaurora.org \
--cc=vinod.koul@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).