From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Himangi Saraogi <himangi774@gmail.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt/sparc: Introduce the use of the managed version of kzalloc
Date: Thu, 22 May 2014 16:14:34 -0700 [thread overview]
Message-ID: <20140522231434.GA9546@core.coreip.homeip.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1405230700090.2606@hadrien>
Hi Julia,
On Fri, May 23, 2014 at 07:03:37AM +0800, Julia Lawall wrote:
>
>
> On Thu, 22 May 2014, Dmitry Torokhov wrote:
>
> > Hi Himangi,
> >
> > On Fri, May 23, 2014 at 01:04:30AM +0530, Himangi Saraogi wrote:
> > > This patch moves data allocated using kzalloc to managed data allocated
> > > using devm_kzalloc and cleans now unnecessary kfrees in probe and remove
> > > functions. Also the unnecessary labels are done away with.
> >
> > Please no more partial devm conversions. I am not interested in patches
> > that change only 1 resource to be managed and leaving the rest as is.
> >
> > If you want to do devm conversion please do it if you convert all (or at
> > least majority) of resource handling to managed resources.
>
> Sorry, I don't think we are clear on what is wanted. Himangi's patches
> convert everything where a devm function is already available (to our
> knowledge). Do you prefer that new devm functions be introduced? On the
> one hand, that is perhaps useful from a safety point of view. On the
> other hand, it could lead to a huge number of rarely used devm functions
> that no one knows about and to a lot of code diversity. So I don't know
> what is the good solution.
I strongly dislike changes that mix managed and non-managed resources in
the same driver as it only leads to confusion: should this resource be
freed or will it be freed automatically.
I am applying patches that convert all (or almost all) resources in a
driver into managed ones, but if that is not [currently] possible then
those drivers are probably better left alone (maybe after additional
audit).
Thanks.
--
Dmitry
next prev parent reply other threads:[~2014-05-22 23:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 19:34 [PATCH] dt/sparc: Introduce the use of the managed version of kzalloc Himangi Saraogi
2014-05-22 19:45 ` Dmitry Torokhov
2014-05-22 23:03 ` Julia Lawall
2014-05-22 23:14 ` Dmitry Torokhov [this message]
2014-05-23 0:07 ` Julia Lawall
2014-05-22 23:35 ` Julia Lawall
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=20140522231434.GA9546@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=himangi774@gmail.com \
--cc=julia.lawall@lip6.fr \
--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;
as well as URLs for NNTP newsgroup(s).