Linux Input/HID development
 help / color / mirror / Atom feed
From: Joshua Clayton <stillcompiling@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, Mark Brown <broonie@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: arizona-haptic - convert to use managed input devices
Date: Mon, 20 Jul 2015 07:48:19 -0700	[thread overview]
Message-ID: <2971079.LMgqEoTvan@jclayton-pc> (raw)
In-Reply-To: <20150717232834.GI39282@dtor-ws>

On Friday, July 17, 2015 04:28:34 PM Dmitry Torokhov wrote:
> On Mon, Jul 06, 2015 at 02:40:05PM -0700, Dmitry Torokhov wrote:
> > On Mon, Jul 06, 2015 at 12:33:06PM -0700, Joshua Clayton wrote:
> > > Hi,
> > > It seems to me that swapping error for ret buries the functional changes in 
> > > the patch...
> > > would it be better to split them into a second  cleanup patch?
> > 
> > Fair enough, although I am not sure if I ever get to the renaming again
> > 
> 
> Joshua, does the below look OK to you?
> 
> Thanks!
> 
> > 
> > Thanks.
> > 
> > -- 
> > Dmitry
> > 
> > 
> > Input: arizona-haptic - convert to use managed input devices
> > 
> > From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> > 
> > Using managed input device (via devm_input_allocate_device) simplifies
> > error handling and driver removal paths and also silences CID# 712569.
> > 
> > Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> > ---
> >  drivers/input/misc/arizona-haptics.c |   26 ++++----------------------
> >  1 file changed, 4 insertions(+), 22 deletions(-)
> > 
> > diff --git a/drivers/input/misc/arizona-haptics.c b/drivers/input/misc/arizona-haptics.c
> > index 4dbbed7..4bf6785 100644
> > --- a/drivers/input/misc/arizona-haptics.c
> > +++ b/drivers/input/misc/arizona-haptics.c
> > @@ -170,8 +170,8 @@ static int arizona_haptics_probe(struct platform_device *pdev)
> >  
> >       INIT_WORK(&haptics->work, arizona_haptics_work);
> >  
> > -     haptics->input_dev = input_allocate_device();
> > -     if (haptics->input_dev == NULL) {
> > +     haptics->input_dev = devm_input_allocate_device(&pdev->dev);
> > +     if (!haptics->input_dev) {
> >               dev_err(arizona->dev, "Failed to allocate input device\n");
> >               return -ENOMEM;
> >       }
> > @@ -188,41 +188,23 @@ static int arizona_haptics_probe(struct platform_device *pdev)
> >       if (ret < 0) {
> >               dev_err(arizona->dev, "input_ff_create_memless() failed: %d\n",
> >                       ret);
> > -             goto err_ialloc;
> > +             return ret;
> >       }
> >  
> >       ret = input_register_device(haptics->input_dev);
> >       if (ret < 0) {
> >               dev_err(arizona->dev, "couldn't register input device: %d\n",
> >                       ret);
> > -             goto err_iff;
> > +             return ret;
> >       }
> >  
> >       platform_set_drvdata(pdev, haptics);
> >  
> >       return 0;
> > -
> > -err_iff:
> > -     if (haptics->input_dev)
> > -             input_ff_destroy(haptics->input_dev);
> > -err_ialloc:
> > -     input_free_device(haptics->input_dev);
> > -
> > -     return ret;
> > -}
> > -
> > -static int arizona_haptics_remove(struct platform_device *pdev)
> > -{
> > -     struct arizona_haptics *haptics = platform_get_drvdata(pdev);
> > -
> > -     input_unregister_device(haptics->input_dev);
> > -
> > -     return 0;
> >  }
> >  
> >  static struct platform_driver arizona_haptics_driver = {
> >       .probe          = arizona_haptics_probe,
> > -     .remove         = arizona_haptics_remove,
> >       .driver         = {
> >               .name   = "arizona-haptics",
> >       },
> 
> -- 
> Dmitry
devm for the win.
Yes, that looks good.

-- 
~Joshua Clayton

      reply	other threads:[~2015-07-20 14:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-06 17:38 [PATCH] Input: arizona-haptic - convert to use managed input devices Dmitry Torokhov
2015-07-06 19:33 ` Joshua Clayton
2015-07-06 21:40   ` Dmitry Torokhov
2015-07-17 23:28     ` Dmitry Torokhov
2015-07-20 14:48       ` Joshua Clayton [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=2971079.LMgqEoTvan@jclayton-pc \
    --to=stillcompiling@gmail.com \
    --cc=broonie@kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox