From mboxrd@z Thu Jan  1 00:00:00 1970
From: pavel@ucw.cz (Pavel Machek)
Date: Wed, 3 Mar 2010 10:17:28 +0100
Subject: board/device file names, and machine names
In-Reply-To: <20100303084244.GD29715@n2100.arm.linux.org.uk>
References: <1267565398.8759.77.camel@c-dwalke-linux.qualcomm.com>
	<20100302235137.GC29715@n2100.arm.linux.org.uk>
	<1267576760.8759.164.camel@c-dwalke-linux.qualcomm.com>
	<20100303084244.GD29715@n2100.arm.linux.org.uk>
Message-ID: <20100303091728.GA31740@atrey.karlin.mff.cuni.cz>
To: linux-arm-kernel@lists.infradead.org
List-Id: linux-arm-kernel.lists.infradead.org

Hi!

> > However, we need some future direction ..
> 
> Given the amount of discussion there's already been, I'm going to come
> down hard on this issue to kill the discussion.
> 
> Stick with Google's existing naming for files and interally within files.
> Put a comment in the files giving all the names.  Use the common name in
> the Kconfig text, and either put the internal names in the help text or
> in brackets in the main option text.
> 
> 
> Don't like it?  I'm sure there's always going to be someone who doesn't
> like whatever is decided upon, so get over it.  The important thing is
> that the decision is made, and that there's no further dithering over
> this issue.

Does not seem to be your decision. At least you should have cc-ed l-k.

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html