[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4D67AEEE.30000@ru.mvista.com>
Date: Fri, 25 Feb 2011 16:30:22 +0300
From: Sergei Shtylyov <sshtylyov@...sta.com>
To: Grant Likely <grant.likely@...retlab.ca>
CC: Sergei Shtylyov <sshtylyov@...sta.com>,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Nicolas Pitre <nicolas.pitre@...aro.org>,
Russell King <linux@....linux.org.uk>
Subject: Re: [PATCH v4 6/7] arm/dt: Basic tegra devicetree support
Hello.
On 24-02-2011 0:36, Grant Likely wrote:
>>> This patch adds adds very basic support for booting tegra with a
>>> device tree. It simply allows the existing machine_descs to match
>>> against the tegra compatible values so that the kernel can boot.
>>> Kernel parameters and the initrd pointer is read out of the tree
>>> instead of atags.
>>> This is not complete device tree support. This change will be
>>> reverted when a new machine_desc is added that can populate the
>>> device registrations directly from data in the tree instead of using
>>> hard coded data. That change will be made in a future patch.
>>> v2: Fixed cut-and-paste error in commit text
>> Shouldn't this sentence follow the --- tearline?
> Nope! It is actually quite useful for the version information to show
> up in the commit text. That way you know *exactly* which version got
> merged. dwmw2 pointed that out to me a few months back.
Well, I think that depends on the patch. If you have say 9 revisions with
significant changes (that's what I actually had) and the revision history far
exceeds the original patch description, then this will just become too ugly I
think...
WBR, Sergei
--
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