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]
Message-ID: <CACRpkdaVyLwOC-b2mKDRAfCQPzFZKEAm8OZxvHtbpc1koeUz-w@mail.gmail.com>
Date:	Mon, 14 Oct 2013 08:58:05 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Alexandre Courbot <gnurou@...il.com>
Cc:	Mika Westerberg <mika.westerberg@...ux.intel.com>,
	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	Grant Likely <grant.likely@...retlab.ca>,
	Mathias Nyman <mathias.nyman@...ux.intel.com>,
	Alexandre Courbot <acourbot@...dia.com>,
	Rob Landley <rob@...dley.net>,
	ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 1/5] gpiolib / ACPI: move acpi_gpiochip_free_interrupts
 next to the request function

On Fri, Oct 11, 2013 at 6:42 PM, Alexandre Courbot <gnurou@...il.com> wrote:
> On Fri, Oct 11, 2013 at 4:00 AM, Linus Walleij <linus.walleij@...aro.org> wrote:
>> On Thu, Oct 10, 2013 at 10:01 AM, Mika Westerberg
>> <mika.westerberg@...ux.intel.com> wrote:
>>
>>> It makes more sense to have these functions close to each other. No
>>> functional changes.
>>>
>>> Signed-off-by: Mika Westerberg <mika.westerberg@...ux.intel.com>
>>> Acked-by: Rafael J. Wysocki <rafael.j.wysocki@...el.com>
>>
>> So I've applied this first patch, and I'm just waiting for Alexandre's
>> ACK on the remaining patches concerning gpiod so we get this
>> 100% right.
>
> I think I'm ok with Mika's patches, however I need to send you a new
> version of gpiod. I wanted to finish documentation first, but maybe
> that can come slightly after so you can at least go ahead with both
> series?

The important thing right now is to get it in a testable form I think?
So that I can throw it at the autobuilder and it gets included into
linux-next as that comes back online.

So give me whatever you have ... BTW is this series dependent on
yours to go in first? Sorry for not seeing the details here...

Yours,
Linus Walleij
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ