From: "Eric Brower" <ebrower@gmail.com>
To: "David Miller" <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: sym53c8xx PCI card broken in 2.6.18
Date: Tue, 22 Aug 2006 22:35:14 -0700 [thread overview]
Message-ID: <ec7cefb0608222235p155b7ab0ld8a23d2db1fbe56d@mail.gmail.com> (raw)
In-Reply-To: <20060822.210136.59470258.davem@davemloft.net>
On 8/22/06, David Miller <davem@davemloft.net> wrote:
> From: "Eric Brower" <ebrower@gmail.com>
> Date: Tue, 22 Aug 2006 20:59:14 -0700
>
> > The envctrl OOPS is definately my fault in the blind conversion of the
> > driver to the OF interface-- of_find_propery() return values should be
> > checked for NULL rather than relying upon a -1 value stored into lenp.
> > We can discuss this separately, since you are using an out-of-kernel
> > driver.
>
> Ok.
>
> BTW, it is better to use "of_get_property()" if you are actually
> interested in the value since it will return a void pointer to the
> property value instead of a "struct property". of_find_property() is
> useful if you just want to check for existence or if you want to
> modify the property value.
>
Thanks, Dave. This driver is interested in property existence and
length-- some OBP versions don't create all expected envctrl
properties, and due to lack of implementation documentation the
property lengths are being checked as well; so of_find_property()
seems appropriate in this case.
Would you consider assigning -1 to lenp (if provided) in
of_find_property() when no matching device is found?
Thanks,
E
--
E
next prev parent reply other threads:[~2006-08-23 5:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 14:46 David Johnson
2006-08-22 20:39 ` David Miller
2006-08-22 22:39 ` David Johnson
2006-08-23 3:59 ` Eric Brower
2006-08-23 4:01 ` David Miller
2006-08-23 5:35 ` Eric Brower [this message]
2006-08-23 5:50 ` David Miller
2006-08-23 21:01 ` Daniel Smolik
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=ec7cefb0608222235p155b7ab0ld8a23d2db1fbe56d@mail.gmail.com \
--to=ebrower@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.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
Powered by JetHome