From: Vladimirs Ambrosovs <rodriguez.twister@gmail.com>
To: Daniel Baluta <daniel.baluta@intel.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald <pmeerw@pmeerw.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
driverdev-devel@linuxdriverproject.org,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
Cristina Georgiana Opriceana <cristina.opriceana@gmail.com>
Subject: Re: [PATCH 1/2] staging: iio_simple_dummy: fix init
Date: Wed, 27 May 2015 20:24:18 +0300 [thread overview]
Message-ID: <20150527172418.GA22971@gmail.com> (raw)
In-Reply-To: <CAEnQRZC4XwYE1anLNCSyd=mTw0_cATS6_95x9CXTL49gxpJGUA@mail.gmail.com>
On Wed, May 27, 2015 at 09:21:28AM +0300, Daniel Baluta wrote:
> Hi,
>
> On Wed, May 27, 2015 at 1:19 AM, Vladimirs Ambrosovs
> <rodriguez.twister@gmail.com> wrote:
> > This patch fixes the init function for the iio_simple_dummy driver.
> > The main issues were absence of kfree for the allocated array, and no
> > devices being removed in case the probe function fails, running in a loop.
> >
> > The iio_dummy_remove function was also changed:
> > * The return value was changed to void
> > * The check for return value of iio_simple_dummy_events_unregister()
> > The reason for this changes is that, as per implementation,
> > events_unregister function always returns 0, so we are safe not to check
> > return value. As a result the return value for iio_dummy_remove function
> > becomes useless as well, hence return value type change.
>
> While at it I think we can also make
> iio_simple_dummy_events_unregister return type void.
> Nice to see that people pay attention to the dummy module :).
>
> As part of Outreachy program, Cristina (CC'ed) will work on making the
> IIO dummy driver
> more useful with the final goal of moving it out of staging.
>
> http://kernelnewbies.org/OutreachyIntro
>
>
Thanks, that's a good point. Should I re-submit the patch, or better
reject the changes, and leave it to Cristina to address in scope of
Outreachy project?
> >
> > Signed-off-by: Vladimirs Ambrosovs <rodriguez.twister@gmail.com>
> > ---
> > drivers/staging/iio/iio_simple_dummy.c | 24 +++++++++++++++---------
> > 1 file changed, 15 insertions(+), 9 deletions(-)
> >
> > diff --git a/drivers/staging/iio/iio_simple_dummy.c b/drivers/staging/iio/iio_simple_dummy.c
> > index b47bf9f..88fbb4f 100644
> > --- a/drivers/staging/iio/iio_simple_dummy.c
> > +++ b/drivers/staging/iio/iio_simple_dummy.c
> > @@ -665,9 +665,8 @@ error_ret:
> > *
> > * Parameters follow those of iio_dummy_probe for buses.
> > */
> > -static int iio_dummy_remove(int index)
> > +static void iio_dummy_remove(int index)
> > {
> > - int ret;
> > /*
> > * Get a pointer to the device instance iio_dev structure
> > * from the bus subsystem. E.g.
> > @@ -685,15 +684,14 @@ static int iio_dummy_remove(int index)
> > /* Buffered capture related cleanup */
> > iio_simple_dummy_unconfigure_buffer(indio_dev);
> >
> > - ret = iio_simple_dummy_events_unregister(indio_dev);
> > - if (ret)
> > - goto error_ret;
> > + /*
> > + * Tidy up interrupt handling
> > + * Always returns 0, so not checking for return value
> > + */
> > + iio_simple_dummy_events_unregister(indio_dev);
> >
> > /* Free all structures */
> > iio_device_free(indio_dev);
> > -
> > -error_ret:
> > - return ret;
> > }
> >
> > /**
> > @@ -722,9 +720,17 @@ static __init int iio_dummy_init(void)
> > for (i = 0; i < instances; i++) {
> > ret = iio_dummy_probe(i);
> > if (ret < 0)
> > - return ret;
> > + goto error_probe;
> > }
> > return 0;
> > +
> > +error_probe:
> > + /* Free devices registered before error */
> > + while (i--)
> > + iio_dummy_remove(i);
> > +
> > + kfree(iio_dummy_devs);
> > + return ret;
> > }
> > module_init(iio_dummy_init);
> >
> > --
> > 2.4.1
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
BR,
Vladimirs.
next prev parent reply other threads:[~2015-05-27 17:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 22:19 [PATCH 1/2] staging: iio_simple_dummy: fix init Vladimirs Ambrosovs
2015-05-26 22:19 ` [PATCH 2/2] staging: iio_simple_dummy: zero check param Vladimirs Ambrosovs
2015-05-27 8:25 ` Dan Carpenter
2015-05-27 22:12 ` Vladimirs Ambrosovs
2015-05-28 6:59 ` Dan Carpenter
2015-05-29 19:38 ` Vladimirs Ambrosovs
2015-05-27 6:21 ` [PATCH 1/2] staging: iio_simple_dummy: fix init Daniel Baluta
2015-05-27 17:24 ` Vladimirs Ambrosovs [this message]
2015-05-27 17:29 ` Dan Carpenter
2015-05-28 5:31 ` Daniel Baluta
2015-05-27 8:23 ` Dan Carpenter
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=20150527172418.GA22971@gmail.com \
--to=rodriguez.twister@gmail.com \
--cc=cristina.opriceana@gmail.com \
--cc=daniel.baluta@intel.com \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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).