From: andi@etezian.org (Andi Shyti)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 1/4] mfd: add syscon driver based on regmap
Date: Tue, 4 Sep 2012 17:44:30 +0200 [thread overview]
Message-ID: <20120904154430.GA4361@Jack.Whiskey> (raw)
In-Reply-To: <20120904114601.GB13046@shlinux2.ap.freescale.net>
On Tue, Sep 04, 2012 at 07:46:02PM +0800, Dong Aisheng wrote:
> On Tue, Sep 04, 2012 at 07:35:45PM +0800, Andi Shyti wrote:
> > Hi Dong,
> >
> > On Tue, Sep 04, 2012 at 11:20:08AM +0800, Dong Aisheng wrote:
> > > +static int __devinit syscon_probe(struct platform_device *pdev)
> > > +{
> > > + struct device *dev = &pdev->dev;
> >
> > Do we really need this variable? Anyway you are using it only
> > once in the dev_info.
> >
> Okay, i can remove it.
On Tue, Sep 04, 2012 at 04:16:59PM +0400, Sergei Shtylyov wrote:
> But Dong definitely could use it more than once, so it seems useful.
[sorry for pasting your e-mail here]
yes, but he is using it only once and, it's easily
reachable with pdev->dev and anyway Dong is using &pdev->dev.
> > > +
> > > + syscon = devm_kzalloc(&pdev->dev, sizeof(struct syscon),
> > > + GFP_KERNEL);
> >
> > in case of error you are not freeing syscon.
> Do we need it for managed resource of syscon?
Yes, you're right :)
> > Moreover, in my opinion, some dev_err more should not heart
^^
as Sergei points out is 'hurt'... mistype :)
> There's no much error cases here, most of them rarely fails and i don't feel
> we really need add.
> I don't know what dev_err you suggested to add?
For example some failure cases, anyway i read quickly the code
and I don't big see issues.
Andi
next prev parent reply other threads:[~2012-09-04 15:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 3:20 [PATCH v5 0/4] add syscon driver based on regmap for general registers access Dong Aisheng
2012-09-04 3:20 ` [PATCH v5 1/4] mfd: add syscon driver based on regmap Dong Aisheng
2012-09-04 11:35 ` Andi Shyti
2012-09-04 11:46 ` Dong Aisheng
2012-09-04 15:44 ` Andi Shyti [this message]
2012-09-04 12:16 ` Sergei Shtylyov
2012-09-04 3:20 ` [PATCH v5 2/4] ARM: imx6q: add iomuxc gpr support into syscon Dong Aisheng
2012-09-04 3:20 ` [PATCH v5 3/4] regulator: anatop-regulator: convert to use syscon to access anatop register Dong Aisheng
2012-09-04 11:34 ` Shawn Guo
2012-09-04 11:27 ` Dong Aisheng
2012-09-04 3:20 ` [PATCH v5 4/4] mfd: anatop-mfd: remove anatop driver Dong Aisheng
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=20120904154430.GA4361@Jack.Whiskey \
--to=andi@etezian.org \
--cc=linux-arm-kernel@lists.infradead.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).