public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ivan T. Ivanov" <iivanov@mm-sol.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Grant Likely <grant.likely@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Bjorn Andersson <bjorn.andersson@sonymobile.com>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v5 3/4] pinctrl: Qualcomm SPMI PMIC GPIO pin controller driver
Date: Wed, 22 Oct 2014 12:35:14 +0300	[thread overview]
Message-ID: <1413970514.30282.8.camel@mm-sol.com> (raw)
In-Reply-To: <5446A2D8.3070204@linaro.org>


On Tue, 2014-10-21 at 19:15 +0100, Srinivas Kandagatla wrote:
> Hi Ivan,
> 
> Just realized that this patch can generate compiler errors due to 
> 3.18
> changes in pinmux_ops struct and gpiochip_remove returns void now.

Yes. I am just preparing new version of this for Linus.

Regards,
Ivan

  reply	other threads:[~2014-10-22  9:35 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 [this message]
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

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=1413970514.30282.8.camel@mm-sol.com \
    --to=iivanov@mm-sol.com \
    --cc=bjorn.andersson@sonymobile.com \
    --cc=devicetree@vger.kernel.org \
    --cc=grant.likely@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=srinivas.kandagatla@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