public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
To: Manish Badarkhe
	<badarkhe.manish-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Dmitry Torokhov
	<dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	"linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Liam Girdwood <lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH V2] regulator: fixed: update to devm_* API
Date: Tue, 28 Jan 2014 09:55:26 +0100	[thread overview]
Message-ID: <1939430.3DVPas1i8V@phil> (raw)
In-Reply-To: <CAKDJKT4jPLmtrm6Ngp+nT5vf0H4zXwwAM=oURDF-DSAJodVN6A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Tuesday, 28. January 2014 14:16:39 Manish Badarkhe wrote:
> Hi Heiko
> 
> Thank you for your reply.
> 
> On Tue, Jan 28, 2014 at 1:08 PM, Heiko Stübner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org> wrote:
> > On Tuesday, 28. January 2014 12:46:01 Manish Badarkhe wrote:
> >> Hi Dmitry,
> >> 
> >> Thank you for your review.
> >> 
> >> On Tue, Jan 28, 2014 at 12:03 PM, Dmitry Torokhov
> >> 
> >> <dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> >> > Hi Manish,
> >> > 
> >> > On Tue, Jan 28, 2014 at 08:42:00AM +0530, Manish Badarkhe wrote:
> >> >> Update the code to use devm_* API so that driver core will manage
> >> >> resources.
> >> >> 
> >> >> Signed-off-by: Manish Badarkhe <badarkhe.manish-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> >> >> ---
> >> >> Changes since V1:
> >> >> 1. Updated driver to use "devm_kzalloc" to "kstrdup".
> >> >> 2. Updated commit message.
> >> >> 
> >> >> Not tested on any board.
> >> >> 
> >> >> :100644 100644 5ea64b9... e9763a4... M       
> >> >> :drivers/regulator/fixed.c
> >> >> :
> >> >>  drivers/regulator/fixed.c |   42
> >> >>  ++++++++++++------------------------------
> >> >>  1 file changed, 12 insertions(+), 30 deletions(-)
> >> >> 
> >> >> diff --git a/drivers/regulator/fixed.c b/drivers/regulator/fixed.c
> >> >> index 5ea64b9..e9763a4 100644
> >> >> --- a/drivers/regulator/fixed.c
> >> >> +++ b/drivers/regulator/fixed.c
> >> >> @@ -132,15 +132,15 @@ static int reg_fixed_voltage_probe(struct
> >> >> platform_device *pdev)>>
> >> >> 
> >> >>                              GFP_KERNEL);
> >> >>       
> >> >>       if (drvdata == NULL) {
> >> >>       
> >> >>               dev_err(&pdev->dev, "Failed to allocate device data\n");
> >> >> 
> >> >> -             ret = -ENOMEM;
> >> >> -             goto err;
> >> >> +             return -ENOMEM;
> >> >> 
> >> >>       }
> >> >> 
> >> >> -     drvdata->desc.name = kstrdup(config->supply_name, GFP_KERNEL);
> >> >> +     drvdata->desc.name = devm_kzalloc(&pdev->dev,
> >> >> +                                       strlen(config->supply_name) +
> >> >> 1,
> >> >> +                                       GFP_KERNEL);
> >> >> 
> >> >>       if (drvdata->desc.name == NULL) {
> >> >>       
> >> >>               dev_err(&pdev->dev, "Failed to allocate supply name\n");
> >> >> 
> >> >> -             ret = -ENOMEM;
> >> >> -             goto err;
> >> >> +             return -ENOMEM;
> >> >> 
> >> >>       }
> >> > 
> >> > Umm, I am fairly certain that devm_kzalloc() can't be used as a
> >> > substitute for kstrdup, at least not without accompanying memcpy.
> >> 
> >> Yes, I have provided allocation but it should be followed with
> >> assignment.
> >> Can I modify like this,
> >> 
> >> +     drvdata->desc.name = devm_kzalloc(&pdev->dev,
> >> +                                       strlen(config->supply_name) + 1,
> >> +                                       GFP_KERNEL);
> >> +     if (drvdata->desc.name)
> >> +     sprintf(drvdata->desc.name, "%s", config->supply_name);
> > 
> > hmm, so you replaced a general helper function by open coding the string-
> > duplication. Doesn't this defeat the target of simplifying the code?
> 
> Intention here, is to use devm_ API and to adopt this I have to do these
> modifications for "kstrdup" functions. I have seen in regulator folder
> almost all drivers adopted to "devm_" API. Hence same thing I am following
> to update this driver. Please let me know whether to go ahead with this
> patch or retain driver as it is.

I don't have a strong opinion on this and others are most likely more qualified 
to have a definitive answer, I just found it strange to exchange one open-coded 
pattern against another open-coded one.

So don't let me keep you from it ;-)

Heiko

  parent reply	other threads:[~2014-01-28  8:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-28  3:12 [PATCH V2] regulator: fixed: update to devm_* API Manish Badarkhe
     [not found] ` <1390878720-8676-1-git-send-email-badarkhe.manish-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-01-28  6:33   ` Dmitry Torokhov
2014-01-28  7:16     ` Manish Badarkhe
2014-01-28  7:38       ` Heiko Stübner
2014-01-28  8:46         ` Manish Badarkhe
     [not found]           ` <CAKDJKT4jPLmtrm6Ngp+nT5vf0H4zXwwAM=oURDF-DSAJodVN6A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-01-28  8:55             ` Heiko Stübner [this message]
2014-01-28  9:01               ` Manish Badarkhe
2014-01-28 10:45                 ` Mark Brown
2014-01-28 16:41   ` Stephen Warren
2014-01-28 17:06     ` Manish Badarkhe

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=1939430.3DVPas1i8V@phil \
    --to=heiko-4mtyjxux2i+zqb+pc5nmwq@public.gmane.org \
    --cc=badarkhe.manish-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.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