All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Alexandre Courbot <gnurou@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Grant Likely <grant.likely@secretlab.ca>,
	Linus Walleij <linus.walleij@linaro.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"christian.ruppert@abilis.com" <christian.ruppert@abilis.com>
Subject: Re: [git pull] GENERIC_GPIO removal
Date: Fri, 10 May 2013 09:55:18 +0530	[thread overview]
Message-ID: <518C76AE.2000909@synopsys.com> (raw)
In-Reply-To: <CAAVeFuKBn0oyZSJ50pchTwOCsSdyP5ofx3gaf4h_02xYuZDGSg@mail.gmail.com>

On 05/10/2013 05:21 AM, Alexandre Courbot wrote:
>
> /me likes regexps. You should see my workaround to using the -i option.
>
> Thanks for the merge, it clears the path for more GPIO stuff. arch/arc
> introduced a new dangling definition of GENERIC_GPIO in -next that now
> appears in your tree, the following patch by Vineet takes care of it.
> Either you can merge it directly or Vineet will make sure this patch
> is in his next pull request.
>
> Alex.
>
> -----8<-----8<-----8<
> From: Vineet Gupta <vgupta@synopsys.com>
> Date: Wed, 17 Apr 2013 17:33:02 +0530
> Subject: [PATCH] ARC: [TB10x] Remove GENERIC_GPIO
>
> This tracks Alexandre Courbot's mainline GPIO rework
>
> Signed-off-by: Vineet Gupta <vgupta@synopsys.com>
> Acked-by: Alexandre Courbot <acourbot@nvidia.com>
> ---

With both the prerequisites (ARC-TB10x && GENERIC_GPIO) now in Linus' tree, I've
added it to my for-curr to be sent to Linus later today.

Thx,
-Vineet

      reply	other threads:[~2013-05-10  4:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-08 13:48 [git pull] GENERIC_GPIO removal Grant Likely
2013-05-09 17:08 ` Linus Torvalds
2013-05-09 18:11   ` Grant Likely
2013-05-09 23:51     ` Alexandre Courbot
2013-05-10  4:25       ` Vineet Gupta [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=518C76AE.2000909@synopsys.com \
    --to=vineet.gupta1@synopsys.com \
    --cc=christian.ruppert@abilis.com \
    --cc=gnurou@gmail.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.