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:	Wed, 15 Jan 2014 19:34:01 +0530
From:	Sekhar Nori <nsekhar@...com>
To:	Linus Walleij <linus.walleij@...aro.org>,
	Wolfram Sang <wsa@...-dreams.de>
CC:	Kevin Hilman <khilman@...aro.org>,
	Santosh Shilimkar <santosh.shilimkar@...com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Alexandre Courbot <gnurou@...il.com>,
	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>
Subject: Re: [PATCH 7/7] drivers/gpio: don't check resource with devm_ioremap_resource

On Wednesday 15 January 2014 07:21 PM, Linus Walleij wrote:
> On Wed, Jan 15, 2014 at 1:54 PM, Sekhar Nori <nsekhar@...com> wrote:
>> On Wednesday 15 January 2014 02:58 PM, Linus Walleij wrote:
> 
>>> Acked-by: Linus Walleij <linus.walleij@...aro.org>
>>>
>>> The DaVinci maintainers are queuing GPIO patches for their driver
>>> for this merge window, so requesting them to apply this patch.
>>
>> I wont be sending any more pull requests for v3.14. Even if I send, the
>> ARM-SoC maintainers will not take it anyway.
> 
> But as it is a fix I believe the ARM SoC maintainers will apply it
> directly to the davinci branch.

Sorry I did not realize this is a fix.

> 
> Wolfram: I suggest you send this patch with my ACK directly
> to arm@...nel.org and ask it to be applied to the davinci branch
> in the ARM SoC tree.

This would work too, I guess. Wolfram, can you please keep me in CC too
in case questions/actions come up?

Thanks,
Sekhar
--
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