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:	Tue, 7 Apr 2015 15:24:24 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Andrew Bresticker <abrestic@...omium.org>
Cc:	Ralf Baechle <ralf@...ux-mips.org>,
	Alexandre Courbot <gnurou@...il.com>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
	Linux-MIPS <linux-mips@...ux-mips.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Ezequiel Garcia <ezequiel.garcia@...tec.com>,
	James Hartley <james.hartley@...tec.com>,
	James Hogan <james.hogan@...tec.com>
Subject: Re: [PATCH V2 0/3] pinctrl: Support for IMG Pistachio

On Tue, Mar 31, 2015 at 7:20 PM, Andrew Bresticker
<abrestic@...omium.org> wrote:
> On Tue, Mar 31, 2015 at 7:00 AM, Ralf Baechle <ralf@...ux-mips.org> wrote:
>> On Mon, Mar 30, 2015 at 04:16:53PM -0700, Andrew Bresticker wrote:
>>
>>> This series adds support for the system pin and GPIO controller on the IMG
>>> Pistachio SoC.  Pistachio's system pin controller manages 99 pins, 90 of
>>> which are MFIOs which can be muxed between multiple functions or used
>>> as GPIOs.  The GPIO control for the 90 MFIOs is broken up into banks
>>> of 16.  Pistachio also has a second pin controller, the RPU pin controller,
>>> which will be supported by a future patchset through an extension to this
>>> driver.
>>>
>>> Test on an IMG Pistachio BuB.  Based on mips-for-linux-next which inluces my
>>> series adding Pistachio platform support [1].  A branch with this series is
>>> available at [2].
>>
>> Does this mean you want me to funnel this through the MIPS tree?  If so,
>> could I have an Ack from the maintainers?
>
> Linus mentioned in v1 that if the only dependency was a Kconfig symbol
> that he could take it through his tree.  I'm fine either way, though
> it would be slightly more convenient for it to go through the MIPS
> tree.  Linus?

I took 1/3 into pinctrl since it touched my core documentation and
actually even had to be slightly rebased.

I will look at 2/3 and 3/3 and provide ACK if I think they are
all right.

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