The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Sachin Kamat <sachin.kamat@linaro.org>
Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
	LKML <linux-kernel@vger.kernel.org>,
	broonie@kernel.org
Subject: Re: [PATCH v3 Resend 2/3] regulator: Add support for S2MPA01 regulator
Date: Mon, 10 Mar 2014 10:39:05 +0000	[thread overview]
Message-ID: <20140310103905.GK14976@lee--X1> (raw)
In-Reply-To: <20140310103812.GJ14976@lee--X1>

> > >> >> Add support for S2MPA01 voltage and current regulator.
> > >>
> > >> >> +
> > >> >> +struct s2mpa01_info {
> > >> >> +     struct regulator_dev *rdev[S2MPA01_REGULATOR_MAX];
> > >> >
> > >> > Hi,
> > >> >
> > >> > It seems that s2mpa01_info->rdev is not used anywhere, except as return
> > >> > value of devm_regulator_register. I think you can remove it completely.
> > >>
> > >> Yes. I will send a follow up patch for this.
> > >
> > > Let's not break things and fix them up later. Fix it in this patch.
> > 
> > Nothing is broken in this patch. What is suggested is just a code cleanup.
> > I did not want to disturb the existing patch set as it is already reviewed
> > and ready for merging. Anyway I can re-spin with this suggested change.
> > 
> > >
> > >> > Beside that, can this driver be merged into existing s2mps11 regulator
> > >> > driver?
> > >>
> > >> Haven't analyzed this yet. Will look into the possibility of consolidation
> > >> later.
> > >
> > > As above. If consolidation is possible it should be take care of in
> > > the first instance.
> > 
> > I need to analyze and see if this is really possible and the extent of
> > re-usability.
> > If possible, this might take a while for me before I start
> > implementing it. Considering
> > that this patch set is now over 2 months old and consolidations do
> > happen subsequently
> > I request you to queue this patch set in its current form (with the
> > above change if you
> > deem it necessary to be part of current patch set).
> 
> I think the suggestion above should be fixed-up.
> 
> Whether to consider consolidation or not is Mark's decision.

Oh, Mark (the maintainer) isn't on CC? I think this is a mistake.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2014-03-10 10:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-06 10:00 [PATCH v3 Resend 1/3] mfd: Add support for S2MPA01 device Sachin Kamat
2014-03-06 10:00 ` [PATCH v3 Resend 2/3] regulator: Add support for S2MPA01 regulator Sachin Kamat
2014-03-06 10:40   ` Krzysztof Kozlowski
2014-03-06 11:22     ` Sachin Kamat
2014-03-10  9:35       ` Lee Jones
2014-03-10  9:56         ` Sachin Kamat
2014-03-10 10:38           ` Lee Jones
2014-03-10 10:39             ` Lee Jones [this message]
2014-03-10 10:42               ` Sachin Kamat
2014-03-06 10:00 ` [PATCH v3 Resend 3/3] Documentation: mfd: Add binding document for S2MPA01 Sachin Kamat

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=20140310103905.GK14976@lee--X1 \
    --to=lee.jones@linaro.org \
    --cc=broonie@kernel.org \
    --cc=k.kozlowski@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sachin.kamat@linaro.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