From: Dan Carpenter <dan.carpenter@oracle.com>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"fmhess@users.sourceforge.net" <fmhess@users.sourceforge.net>,
"abbotti@mev.co.uk" <abbotti@mev.co.uk>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] staging: comedi: remove this_board macro in the s526 driver
Date: Wed, 23 May 2012 21:51:09 +0300 [thread overview]
Message-ID: <20120523185109.GO4629@mwanda> (raw)
In-Reply-To: <ADE657CA350FB648AAC2C43247A983F0020698BAC8A9@AUSP01VMBX24.collaborationhost.net>
On Wed, May 23, 2012 at 11:06:39AM -0500, H Hartley Sweeten wrote:
> On Tuesday, May 22, 2012 10:49 PM, Dan Carpenter wrote:
> > On Tue, May 22, 2012 at 06:20:10PM -0700, H Hartley Sweeten wrote:
> >> The 'thisboard' macro depends on having a local variable with
> >> a magic name. The CodingStyle document suggests not doing this
> >> to avoid confusion. Remove the macro and use the comedi_board()
> >> inline helper to get the dev->board_ptr information.
> >>
> >> Signed-off-by: H Hartley Sweeten <hsweeten@visionengravers.com>
> >> Cc: Ian Abbott <abbotti@mev.co.uk>
> >> Cc: Mori Hess <fmhess@users.sourceforge.net>
> >> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> >>
> >> ---
> >> @@ -769,13 +765,7 @@ static int s526_attach(struct comedi_device *dev, struct comedi_devconfig *it)
> >> }
> >> ***/
> >>
> >> -/*
> >> - * Initialize dev->board_name. Note that we can use the "thisboard"
> >> - * macro now, since we just initialized it in the last line.
> >> - */
> >> - dev->board_ptr = &s526_boards[0];
> >
> > Was this intended? Most of the boards have auto probing so the
> > ->board_ptr gets set automatically. We already called
> > comedi_board() so I wonder if the autoprobed board is the same as
> > the &s526_boards[0];? NULL pointer perhaps? I don't know.
>
> Yes, removing the line was intended. Sorry I didn't mention it in the
> commit message.
>
> The dev->board_ptr will already be set by comedi_device_attach()
> before the drivers attach() method is called.
>
> I think the author of this driver misunderstood the skel driver and
> thought this was needed in order to simulate a "probe". See this
> comment in the skel.c driver:
>
> /*
> * If you can probe the device to determine what device in a series
> * it is, this is the place to do it. Otherwise, dev->board_ptr
> * should already be initialized.
> */
> /* dev->board_ptr = skel_probe(dev, it); */
>
Heh. Yeah. I saw you removed a bunch of these comments and this
was the only one that wasn't commented so I wondered.
Ian already explained how the probing works. Looks good.
regards,
dan carpenter
prev parent reply other threads:[~2012-05-23 18:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 1:20 [PATCH] staging: comedi: remove this_board macro in the s526 driver H Hartley Sweeten
2012-05-23 5:48 ` Dan Carpenter
2012-05-23 9:18 ` Ian Abbott
2012-05-23 16:28 ` H Hartley Sweeten
2012-05-23 16:48 ` Ian Abbott
2012-05-23 16:53 ` H Hartley Sweeten
2012-05-23 19:07 ` Dan Carpenter
2012-05-24 8:53 ` Ian Abbott
2012-05-23 16:06 ` H Hartley Sweeten
2012-05-23 18:51 ` Dan Carpenter [this message]
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=20120523185109.GO4629@mwanda \
--to=dan.carpenter@oracle.com \
--cc=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=fmhess@users.sourceforge.net \
--cc=gregkh@linuxfoundation.org \
--cc=hartleys@visionengravers.com \
--cc=linux-kernel@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.