devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre Courbot <gnurou@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Alexandre Courbot <acourbot@nvidia.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Grant Likely <grant.likely@linaro.org>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Mathias Nyman <mathias.nyman@linux.intel.com>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v3 0/3] New descriptor-based GPIO interface
Date: Fri, 18 Oct 2013 10:37:21 -0700	[thread overview]
Message-ID: <CAAVeFu+rj6AtKgfig6ZrYUzW9HZTg5qLyw4aGozyD31P_pEKAQ@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdYx07Kfs6zOQmTg2cTSmEmsGgP=7wMCSG_30NW=dfYRPQ@mail.gmail.com>

On Fri, Oct 18, 2013 at 4:23 AM, Linus Walleij <linus.walleij@linaro.org> wrote:
> On Thu, Oct 17, 2013 at 7:21 PM, Alexandre Courbot <acourbot@nvidia.com> wrote:
>
>> Hi Linus,
>>
>> This version should merge as-is in your tree (I hope!). A patch for
>> documentation will follow soon.
>>
>> Changes since v2:
>> - rebased on top of Linus' for-next branch
>> - exported new gpiod_(un)lock_as_irq() functions in driver.h
>> - squashed a fix for a compilation error
>
> Thanks, let's see if I can get this into v3.13, right now it's
> unclear if I'll dare to do this. These do not apply right off
> as it requires the late fixes to the gpiod code which currently
> are in Torvalds' tree and on my fixes branch, so I'll merge in
> v3.12-rc6 as it arrives, and then attempt to apply this on
> top, but I don't know if I dare to do this so late.
>
> The outage of linux-next also contributes to this situation.
>
> We might have to take this as the first thing after the merge
> window and targeted for v3.14.

No particular pressure from my side to get this in 3.13. Do for the
best, and don't hesitate to delay them to 3.14 if you feel they are
not tested enough. I'll already feel better once I know they are under
your tree. ;)

Thanks,
Alex.

  reply	other threads:[~2013-10-18 17:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-17 17:21 [PATCH v3 0/3] New descriptor-based GPIO interface Alexandre Courbot
2013-10-17 17:21 ` [PATCH v3 1/3] gpiolib: export " Alexandre Courbot
2013-10-17 17:21 ` [PATCH v3 2/3] gpiolib: port of_ functions to use gpiod Alexandre Courbot
2013-10-17 17:21 ` [PATCH v3 3/3] gpiolib: add gpiod_get() and gpiod_put() functions Alexandre Courbot
2013-10-18 11:23 ` [PATCH v3 0/3] New descriptor-based GPIO interface Linus Walleij
2013-10-18 17:37   ` Alexandre Courbot [this message]
2013-10-19 21:26     ` Linus Walleij
2013-10-20 22:18       ` Alexandre Courbot
2013-10-23  8:17         ` 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=CAAVeFu+rj6AtKgfig6ZrYUzW9HZTg5qLyw4aGozyD31P_pEKAQ@mail.gmail.com \
    --to=gnurou@gmail.com \
    --cc=acourbot@nvidia.com \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=grant.likely@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathias.nyman@linux.intel.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rafael.j.wysocki@intel.com \
    /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).