linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre Courbot <gnurou@gmail.com>
To: Kumar Gala <galak@codeaurora.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] gpio: msm: switch Kconfig to ARCH_QCOM depends
Date: Sat, 22 Feb 2014 10:57:01 +0900	[thread overview]
Message-ID: <CAAVeFuLDAhrS+ntNhOoszRXSrBLFaEhVTKkYbRtiAfogbjbexQ@mail.gmail.com> (raw)
In-Reply-To: <E44A8A90-550C-438C-9EA0-61E033BB988E@codeaurora.org>

On Sat, Feb 22, 2014 at 12:33 AM, Kumar Gala <galak@codeaurora.org> wrote:
>
> On Feb 11, 2014, at 2:22 PM, Kumar Gala <galak@codeaurora.org> wrote:
>
>> We've split Qualcomm MSM support into legacy and multiplatform.  The gpio
>> msm-v2 driver is only relevant on the multiplatform supported SoCs so
>> switch the Kconfig depends to ARCH_QCOM.
>>
>> CC: Linus Walleij <linus.walleij@linaro.org>
>> Signed-off-by: Kumar Gala <galak@codeaurora.org>
>> ---
>> Linus,
>>
>> If you can ack this I'll send it via linux-qcom/arm-soc tree's
>>
>> thanks
>>
>> - k
>
> ping.

Linus is slow to answer for some reason, but I guess that as the
co-maintainer my Ack would do for such a simple patch?

Acked-by: Alexandre Courbot <gnurou@gmail.com>

Linus, please rap on my knuckles if you feel I overstepped.

  reply	other threads:[~2014-02-22  1:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-11 20:22 [PATCH] gpio: msm: switch Kconfig to ARCH_QCOM depends Kumar Gala
2014-02-18 16:40 ` Kumar Gala
2014-02-21 15:33 ` Kumar Gala
2014-02-22  1:57   ` Alexandre Courbot [this message]
2014-02-27  9:18 ` Linus Walleij

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=CAAVeFuLDAhrS+ntNhOoszRXSrBLFaEhVTKkYbRtiAfogbjbexQ@mail.gmail.com \
    --to=gnurou@gmail.com \
    --cc=galak@codeaurora.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-gpio@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).