From: Rasmus Villemoes <linux@rasmusvillemoes.dk>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
Dan Carpenter <dan.carpenter@oracle.co>,
linux-sparse@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: detecting misuse of of_get_property
Date: Tue, 29 Oct 2019 12:43:24 +0100 [thread overview]
Message-ID: <e255d01b-ecd7-8386-e99e-b3226dac27c4@rasmusvillemoes.dk> (raw)
In-Reply-To: <20191029104917.GI1944@kadam>
On 29/10/2019 11.50, Dan Carpenter wrote:
> This should probably work?
I haven't tested it, but yes, something like that. Can you also do the
case of struct property::value, i.e. handling
struct property *p = ...;
u32 *v = p->value;
Thanks,
Rasmus
next prev parent reply other threads:[~2019-10-29 11:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 19:32 detecting misuse of of_get_property Rasmus Villemoes
2019-10-28 22:49 ` Luc Van Oostenryck
2019-10-29 7:24 ` Rasmus Villemoes
2019-10-29 10:50 ` Dan Carpenter
2019-10-29 11:43 ` Rasmus Villemoes [this message]
2019-10-29 12:57 ` Dan Carpenter
2019-10-29 11:47 ` Luc Van Oostenryck
2019-10-29 12:55 ` Dan Carpenter
2019-10-29 13:37 ` Luc Van Oostenryck
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=e255d01b-ecd7-8386-e99e-b3226dac27c4@rasmusvillemoes.dk \
--to=linux@rasmusvillemoes.dk \
--cc=dan.carpenter@oracle.co \
--cc=dan.carpenter@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.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).