All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: myungjoo.ham@samsung.com
Cc: "Axel Lin" <axel.lin@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Kevin Hilman" <khilman@ti.com>, 박경민 <kyungmin.park@samsung.com>,
	"Mike Turquette" <mturquette@ti.com>
Subject: Re: [PATCH 2/2] devfreq: separate error paths from successful path
Date: Tue, 15 Nov 2011 00:19:59 +0100	[thread overview]
Message-ID: <201111150019.59967.rjw@sisk.pl> (raw)
In-Reply-To: <201111150017.41439.rjw@sisk.pl>

On Tuesday, November 15, 2011, Rafael J. Wysocki wrote:
> On Friday, November 11, 2011, MyungJoo Ham wrote:
> > Sender : Axel Lin<axel.lin@gmail.com> Date : 2011-11-10 16:30 (GMT+09:00)
> > > I think this change improves readability.
> > > 
> > > Signed-off-by: Axel Lin 
> > 
> > I agree. It makes it easier to read.
> > 
> > Acked-by: MyungJoo Ham <myungjoo.ham@samsung.com>
> 
> Applied to linux-pm/pm-fixes.

Sorry, this one went to linux-pm/linux-next and will wait for the 3.3 merge
window.

Thanks,
Rafael


> > > ---
> > > drivers/devfreq/devfreq.c |   15 +++++++--------
> > > 1 files changed, 7 insertions(+), 8 deletions(-)
> > > 
> > > diff --git a/drivers/devfreq/devfreq.c b/drivers/devfreq/devfreq.c
> > > index 59d24e9..c189b82 100644
> > > --- a/drivers/devfreq/devfreq.c
> > > +++ b/drivers/devfreq/devfreq.c
> > > @@ -347,7 +347,7 @@ struct devfreq *devfreq_add_device(struct device *dev,
> > > if (!IS_ERR(devfreq)) {
> > > dev_err(dev, "%s: Unable to create devfreq for the device. It already has one. ", __func__);
> > > err = -EINVAL;
> > > - goto out;
> > > + goto err_out;
> > > }
> > > }
> > > 
> > > @@ -356,7 +356,7 @@ struct devfreq *devfreq_add_device(struct device *dev,
> > > dev_err(dev, "%s: Unable to create devfreq for the device ",
> > > __func__);
> > > err = -ENOMEM;
> > > - goto out;
> > > + goto err_out;
> > > }
> > > 
> > > mutex_init(&devfreq->lock);
> > > @@ -399,17 +399,16 @@ struct devfreq *devfreq_add_device(struct device *dev,
> > >    devfreq->next_polling);
> > > }
> > > mutex_unlock(&devfreq_list_lock);
> > > - goto out;
> > > +out:
> > > + return devfreq;
> > > +
> > > err_init:
> > > device_unregister(&devfreq->dev);
> > > err_dev:
> > > mutex_unlock(&devfreq->lock);
> > > kfree(devfreq);
> > > -out:
> > > - if (err)
> > > - return ERR_PTR(err);
> > > - else
> > > - return devfreq;
> > > +err_out:
> > > + return ERR_PTR(err);
> > > }
> > > 
> > > /**
> > 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 
> 


  reply	other threads:[~2011-11-14 23:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-11  4:09 [PATCH 2/2] devfreq: separate error paths from successful path MyungJoo Ham
2011-11-14 23:17 ` Rafael J. Wysocki
2011-11-14 23:19   ` Rafael J. Wysocki [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-11-10  7:28 [PATCH 1/2] devfreq: fix use after free in devfreq_remove_device Axel Lin
2011-11-10  7:30 ` [PATCH 2/2] devfreq: separate error paths from successful path Axel Lin

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=201111150019.59967.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=axel.lin@gmail.com \
    --cc=khilman@ti.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@ti.com \
    --cc=myungjoo.ham@samsung.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.