linux-kernel - Re: [PATCH v3 0/3] New descriptor-based GPIO interface

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 18 Oct 2013 10:37:21 -0700
From:	Alexandre Courbot <gnurou@...il.com>
To:	Linus Walleij <linus.walleij@...aro.org>
Cc:	Alexandre Courbot <acourbot@...dia.com>,
	Arnd Bergmann <arnd@...db.de>,
	Grant Likely <grant.likely@...aro.org>,
	Mika Westerberg <mika.westerberg@...ux.intel.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
	Mathias Nyman <mathias.nyman@...ux.intel.com>,
	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [PATCH v3 0/3] New descriptor-based GPIO interface

On Fri, Oct 18, 2013 at 4:23 AM, Linus Walleij <linus.walleij@...aro.org> wrote:
> On Thu, Oct 17, 2013 at 7:21 PM, Alexandre Courbot <acourbot@...dia.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/