public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ivan T. Ivanov" <iivanov@mm-sol.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	Grant Likely <grant.likely@linaro.org>,
	Bjorn Andersson <bjorn.andersson@sonymobile.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH v5 0/4] Qualcomm SPMI PMIC pin controller drivers
Date: Tue, 21 Oct 2014 14:41:27 +0300	[thread overview]
Message-ID: <1413891687.30282.4.camel@mm-sol.com> (raw)
In-Reply-To: <CACRpkdaZ8o=Kmbez3iA_-0euuWQKwKyNNYPjnx1fBZOns0yN6A@mail.gmail.com>


On Tue, 2014-10-21 at 12:59 +0200, Linus Walleij wrote:
> On Wed, Oct 1, 2014 at 6:30 PM, Ivan T. Ivanov <iivanov@mm-sol.com> 
> wrote:
> 
> >  Changes since v4:
> > >
> >  - Use PMIC name in compatible string.
> >  - PINCTRL_QCOM_SPMI_PMIC from Kconfig symbol.
> >  - Remove pmic string from drivers file names.
> >  - Fixed coding style issues.
> >  - Use qcom-spmi-gpio and qcom-spmi-mpp from dirver names,
> >    to be similar to qcom-spmi-iadc, qcom-spmi-vadc and
> >    qcom-spmi-temp-alarm drivers.
> > >
> >  Short description:
> > >
> >  Patches adds pin control drivers for Multi-Purpose Pin (MPP) and
> >  General-purpose pin (GPIO) controllers found in Qualcomm SPMI 
> > based
> >  PMIC chips.
> > >
> >  MPP's are enhanced GPIO's with analog circuits, which support
> >  analog and digital input/output.
> 
> I think I'm happy to apply this for v3.19 now that I have Björn's
> ACK on it too (or is it even Reviewed-by..?)
> 
> But I can't find these patches in my mailbox, do you have
> a branch based off v3.18-rc1 I can pull from?

They are prepared but not sent. Will try to send them shortly. 

Thank you.
Ivan

> 
> Yours,
> Linus Walleij
> 


      reply	other threads:[~2014-10-21 11:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-01 16:30 [PATCH v5 0/4] Qualcomm SPMI PMIC pin controller drivers Ivan T. Ivanov
2014-10-01 16:30 ` [PATCH v5 1/4] pinctrl: Device tree bindings for Qualcomm PMIC GPIO block Ivan T. Ivanov
2014-10-01 16:30 ` [PATCH v5 2/4] pinctrl: Device tree bindings for Qualcomm PMIC MPP block Ivan T. Ivanov
2014-10-01 16:30 ` [PATCH v5 3/4] pinctrl: Qualcomm SPMI PMIC GPIO pin controller driver Ivan T. Ivanov
2014-10-21 18:15   ` Srinivas Kandagatla
2014-10-22  9:35     ` Ivan T. Ivanov
2014-10-01 16:30 ` [PATCH v5 4/4] pinctrl: Qualcomm SPMI PMIC MPP " Ivan T. Ivanov
2014-10-03 23:53 ` [PATCH v5 0/4] Qualcomm SPMI PMIC pin controller drivers Bjorn Andersson
2014-10-07 11:55   ` Ivan T. Ivanov
2014-10-21 10:59 ` Linus Walleij
2014-10-21 11:41   ` Ivan T. Ivanov [this message]

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=1413891687.30282.4.camel@mm-sol.com \
    --to=iivanov@mm-sol.com \
    --cc=bjorn.andersson@sonymobile.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=grant.likely@linaro.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@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