From: Sinan Kaya <okaya@codeaurora.org>
To: "Lothar Waßmann" <LW@KARO-electronics.de>
Cc: devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
timur@codeaurora.org, open list <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
dmaengine@vger.kernel.org, Frank Rowand <frowand.list@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V6 4/7] OF: properties: Implement get_match_data() callback
Date: Fri, 8 Dec 2017 09:33:27 -0500 [thread overview]
Message-ID: <6a47c4f6-096e-626d-6761-5f88a07609a7@codeaurora.org> (raw)
In-Reply-To: <20171208101142.1ea9bc13@karo-electronics.de>
On 12/8/2017 4:11 AM, Lothar Waßmann wrote:
>> While implementing the ACPI piece, I have to convert an unsigned long to
>> (const void *) in ACPI code so that the APIs are compatible.
>>
> Just one more remark: Do you need write access to the data the pointer
> returned by device_get_match_data() or of_fwnode_get_match_data()
> points to?
> If not, the return type of those functions should be 'const void *'.
Yes, the only reason driver is trying to obtain this data pointer is to modify
members of it. I did a quick test with your suggestion.
test.c: In function ‘main’:
test.c:15:2: error: assignment of member ‘m’ in read-only object
t->m = 3;
^
struct test
{
int m;
};
int main(void)
{
const void *ptr;
unsigned long l =4;
const struct test *t;
ptr = (const void *)l;
t = ptr;
t->m = 3;
}
--
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-12-08 14:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1512493493-6464-1-git-send-email-okaya@codeaurora.org>
2017-12-05 17:04 ` [PATCH V6 1/7] Documentation: DT: qcom_hidma: Bump HW revision for the bugfixed HW Sinan Kaya
2017-12-05 17:04 ` [PATCH V6 2/7] ACPI / bus: Introduce acpi_get_match_data() function Sinan Kaya
2017-12-05 22:04 ` Rafael J. Wysocki
2017-12-06 16:41 ` Sinan Kaya
2017-12-05 17:04 ` [PATCH V6 3/7] device property: Introduce a common API to fetch device match data Sinan Kaya
2017-12-07 12:29 ` Sakari Ailus
2017-12-07 20:15 ` Sinan Kaya
2017-12-07 12:40 ` Sakari Ailus
2017-12-07 20:17 ` Sinan Kaya
2017-12-07 22:06 ` Sakari Ailus
2017-12-07 22:19 ` Rafael J. Wysocki
2017-12-14 10:28 ` Sakari Ailus
2017-12-05 17:04 ` [PATCH V6 4/7] OF: properties: Implement get_match_data() callback Sinan Kaya
2017-12-05 21:21 ` Rob Herring
2017-12-07 12:38 ` Sakari Ailus
2017-12-07 13:10 ` Lothar Waßmann
2017-12-07 14:45 ` Sinan Kaya
2017-12-07 15:20 ` Lothar Waßmann
2017-12-07 17:50 ` Sinan Kaya
2017-12-08 8:09 ` Lothar Waßmann
2017-12-08 9:11 ` Lothar Waßmann
2017-12-08 14:33 ` Sinan Kaya [this message]
2017-12-08 14:40 ` Sinan Kaya
2017-12-05 17:04 ` [PATCH V6 5/7] ACPI: " Sinan Kaya
2017-12-05 17:04 ` [PATCH V6 6/7] dmaengine: qcom_hidma: Add support for the new revision Sinan Kaya
2017-12-05 17:04 ` [PATCH V6 7/7] 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=6a47c4f6-096e-626d-6761-5f88a07609a7@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=LW@KARO-electronics.de \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=frowand.list@gmail.com \
--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=robh+dt@kernel.org \
--cc=timur@codeaurora.org \
/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®