From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Sergei Shtylyov <sshtylyov@mvista.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Nicolas Pitre <nicolas.pitre@linaro.org>,
Russell King <linux@arm.linux.org.uk>
Subject: Re: [PATCH v4 6/7] arm/dt: Basic tegra devicetree support
Date: Fri, 25 Feb 2011 16:30:22 +0300 [thread overview]
Message-ID: <4D67AEEE.30000@ru.mvista.com> (raw)
In-Reply-To: <20110223213601.GA5404@angua.secretlab.ca>
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
next prev parent reply other threads:[~2011-02-25 13:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 2:22 [PATCH v4 0/7] Basic ARM " Grant Likely
2011-02-23 2:22 ` [PATCH v4 1/7] arm/dt: Make __vet_atags also accept a dtb image Grant Likely
2011-02-23 2:22 ` [PATCH v4 2/7] arm/dt: Allow CONFIG_OF on ARM Grant Likely
2011-02-23 2:22 ` [PATCH v4 3/7] arm/dt: consolidate atags setup into setup_machine_atags Grant Likely
2011-02-26 15:27 ` Shawn Guo
2011-03-26 6:44 ` Grant Likely
2011-02-23 2:22 ` [PATCH v4 4/7] arm/dt: probe for platforms via the device tree Grant Likely
2011-02-23 2:22 ` [PATCH v4 5/7] arm/dt: Basic versatile devicetree support Grant Likely
2011-02-23 2:22 ` [PATCH v4 6/7] arm/dt: Basic tegra " Grant Likely
2011-02-23 21:13 ` Sergei Shtylyov
2011-02-23 21:36 ` Grant Likely
2011-02-25 13:30 ` Sergei Shtylyov [this message]
2011-02-25 15:54 ` Grant Likely
2011-02-23 2:22 ` [PATCH v4 7/7] dt: add documentation of ARM dt boot interface Grant Likely
2011-02-23 2:55 ` Nicolas Pitre
2011-02-23 4:35 ` Grant Likely
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D67AEEE.30000@ru.mvista.com \
--to=sshtylyov@mvista.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nicolas.pitre@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®