From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: READ THIS: the next mach-types update
Date: Sat, 17 Sep 2011 15:34:27 +0100 [thread overview]
Message-ID: <20110917143427.GA16591@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <2A3DCF3DA181AD40BDE86A3150B27B6B03B4C80171@dbde02.ent.ti.com>
On Sat, Sep 17, 2011 at 07:58:20PM +0530, Pedanekar, Hemant wrote:
> But since I had submitted v1 (see [1]) and am working on v2 post review, can you
> please suggest how to go about it as I will need the above for adding support
> for TI8148 EVM?
The answer you require is in this statement:
# This is a cut-down version of the file; it contains only machines that
# are merged into mainline or have been edited in the machine database
# within the last 12 months. References to machine_is_NAME() do not count!
which highlights the policy. The key thing there is "edited".
next prev parent reply other threads:[~2011-09-17 14:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 10:25 READ THIS: the next mach-types update Russell King - ARM Linux
2011-09-15 14:50 ` Jean-Christophe PLAGNIOL-VILLARD
2011-09-16 7:31 ` Russell King - ARM Linux
2011-09-17 2:51 ` Jean-Christophe PLAGNIOL-VILLARD
2011-09-15 15:26 ` Arnd Bergmann
2011-09-15 19:11 ` Russell King - ARM Linux
2011-09-15 19:32 ` Nicolas Pitre
2011-09-15 18:05 ` Olof Johansson
2011-09-16 10:27 ` Richard Cochran
2011-09-18 15:44 ` Arnd Bergmann
2011-09-19 15:51 ` Richard Cochran
2011-09-17 14:28 ` Pedanekar, Hemant
2011-09-17 14:34 ` Russell King - ARM Linux [this message]
2011-09-19 14:51 ` Pedanekar, Hemant
2011-09-19 23:13 ` H Hartley Sweeten
2011-10-17 10:56 ` Russell King - ARM Linux
2011-10-17 11:22 ` Arnd Bergmann
2011-10-17 16:57 ` H Hartley Sweeten
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=20110917143427.GA16591@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).