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: <54BE805A.3060300@wwwdotorg.org>
Date:	Tue, 20 Jan 2015 09:20:42 -0700
From:	Stephen Warren <swarren@...dotorg.org>
To:	Tomeu Vizoso <tomeu.vizoso@...labora.com>
CC:	"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
	Javier Martinez Canillas <javier.martinez@...labora.co.uk>,
	Dylan Reid <dgreid@...omium.org>,
	Simon Glass <sjg@...omium.org>,
	Ulf Hansson <ulf.hansson@...aro.org>,
	Rob Herring <robh+dt@...nel.org>,
	Pawel Moll <pawel.moll@....com>,
	Mark Rutland <mark.rutland@....com>,
	Ian Campbell <ijc+devicetree@...lion.org.uk>,
	Kumar Gala <galak@...eaurora.org>,
	Russell King <linux@....linux.org.uk>,
	Thierry Reding <thierry.reding@...il.com>,
	Alexandre Courbot <gnurou@...il.com>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 02/11] ARM: tegra: Use the generated pinmux data

On 01/20/2015 06:59 AM, Tomeu Vizoso wrote:
> On 15 January 2015 at 18:25, Stephen Warren <swarren@...dotorg.org> wrote:
>> On 01/15/2015 09:12 AM, Tomeu Vizoso wrote:
>>>
>>> Google has submitted a board config for the pinmux programming of the
>>> Nyan Big board. Use the whole of it as it's generated to make it easier
>>> to update as the configuration gets fixed in the future.
>>
>>
>> Submitted to where? I assume you mean tegra-pinmux-scripts. I don't see a
>> Nyan/Nyan-big configuration there yet. IIRC (and I might not) one was
>> posted, but there were some review comments that aren't yet addressed?
>
> Yeah, that's what I meant by submitted. TTBOMK the v2 doesn't have any
> comments pending of being addressed?

There's a thread where you and Andrew are discussing the settings for a 
bunch of the pins, and the differences between Big and Blaze. It didn't 
seem to me that the resolution was that the V2 patch was fine as is, but 
perhaps that's what the thread meant!

Either way, it'd be nice if Andrew or someone else from ChromeOS could 
give an acked-by/reviewed-by for the patch if it's OK as is. That way, 
I'll know it's good without any doubts.
--
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