All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Vladimirs Ambrosovs <rodriguez.twister@gmail.com>
Cc: Daniel Baluta <daniel.baluta@intel.com>,
	Lars-Peter Clausen <lars@metafoo.de>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	driverdev-devel@linuxdriverproject.org,
	Peter Meerwald <pmeerw@pmeerw.net>,
	Hartmut Knaack <knaack.h@gmx.de>,
	Cristina Georgiana Opriceana <cristina.opriceana@gmail.com>,
	Jonathan Cameron <jic23@kernel.org>
Subject: Re: [PATCH 1/2] staging: iio_simple_dummy: fix init
Date: Wed, 27 May 2015 20:29:07 +0300	[thread overview]
Message-ID: <20150527172907.GT11588@mwanda> (raw)
In-Reply-To: <20150527172418.GA22971@gmail.com>

On Wed, May 27, 2015 at 08:24:18PM +0300, Vladimirs Ambrosovs wrote:
> 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?

No no.  Please resend the patches.

regards,
dan carpenter

  reply	other threads:[~2015-05-27 17:29 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
2015-05-27 17:29     ` Dan Carpenter [this message]
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=20150527172907.GT11588@mwanda \
    --to=dan.carpenter@oracle.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 \
    --cc=rodriguez.twister@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 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.