From: walter harms <wharms@bfs.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [patch] staging: comedi: cleanup comedi_recognize()
Date: Wed, 06 Jun 2012 12:28:59 +0000 [thread overview]
Message-ID: <4FCF4D0B.60806@bfs.de> (raw)
In-Reply-To: <20120524102851.GA4399@elgon.mountain>
Am 06.06.2012 13:20, schrieb Ian Abbott:
> On 2012-06-06 10:49, Dan Carpenter wrote:
>> On Wed, Jun 06, 2012 at 11:45:43AM +0200, walter harms wrote:
>>>
>>>
>>> Am 06.06.2012 11:28, schrieb Ian Abbott:
>>>> On 2012-06-05 12:01, Dan Carpenter wrote:
>>>>> On Tue, Jun 05, 2012 at 12:06:10PM +0200, walter harms wrote:
>>>>>> Hi all,
>>>>>> the patch is fine with me but i have a few basic questions:
>>>>>>
>>>>>> Why the (void *) at all ? it returns a name what is a const char *.
>>>>>>
>>>>>
>>>>> We're really returning a pointer to a private struct, it's just that
>>>>> the first element on the struct always has to be a pointer to char *.
>>>>
>>>> To be pedantic, it's really returning a pointer to some member of type
>>>> 'const char *' within a private struct. To make life easier for
>>>> themselves, those drivers make that the first member of the private
>>>> struct so a void pointer to the member is also a void pointer to the
>>>> struct.
>>>>
>>>
>>> I do not like it. It is confusing.
>>
>> Yep.
>
> But at least the confusion is concentrated in a single place! From the
> individual drivers' point of view it's fairly simple (as long as it puts
> the 'const char pointer to board name' member at the top of its private
> data structure).
>
Sometimes you can not write "clean" code but a few lines of comments are
then a must.
>>> Are these struct comedi_driver *driv of different size every time ?
>>
>> Nope.
>
> It's the private board information data structures for each driver that
> are different sizes, but the size is passed in the comedi comedi_driver
> 'offset' member along with the 'board_name' and 'num_names' members. Not
> all drivers set those members and just use the 'driver_name' to match
> any supported device, but I digress.
>
If i can believe the comments in the structure offset is the distance to the next
name /* offset in bytes from one board name pointer to the next */
and the name is not the first entry it is the second.
That means any program assuming that this code returns a (struct comedi_driver *)
has to do some correction or it will be off-bye-one sizeof(struct comedi_driver *).
Please correct me if i am wrong:
I have no clue how dev->board_ptr is used, if it works it is fine with me.
re,
wh
next prev parent reply other threads:[~2012-06-06 12:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 10:28 [patch] staging: comedi: cleanup comedi_recognize() Dan Carpenter
2012-05-24 10:57 ` Ian Abbott
2012-05-24 11:16 ` Dan Carpenter
2012-05-24 11:17 ` Ian Abbott
2012-06-05 10:06 ` walter harms
2012-06-05 11:01 ` Dan Carpenter
2012-06-06 9:28 ` Ian Abbott
2012-06-06 9:45 ` walter harms
2012-06-06 9:49 ` Dan Carpenter
2012-06-06 11:20 ` Ian Abbott
2012-06-06 12:28 ` walter harms [this message]
2012-06-06 14:11 ` Ian Abbott
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=4FCF4D0B.60806@bfs.de \
--to=wharms@bfs.de \
--cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.