From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Updated mach-types update
Date: Sun, 20 Mar 2011 11:41:37 +0000 [thread overview]
Message-ID: <20110320114137.GD16646@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20110320110322.GC16646@n2100.arm.linux.org.uk>
On Sun, Mar 20, 2011 at 11:03:22AM +0000, Russell King - ARM Linux wrote:
> Some may notice that the mach-types update in my tree has been replaced
> by a new update to the file, but with a difference:
>
> arch/arm/tools/mach-types | 2406 ++-------------------------------------------
> 1 files changed, 89 insertions(+), 2317 deletions(-)
>
> It deletes a lot of entries.
>
> For a while now, I've been running a script each day after a pull from
> mainline which updates a flag in the machine database indicating whether
> an entry has existed in mainline at any point in time. The database also
> tracks the time which the last change made to any entry.
>
> Coupling these two bits of data together means that we can select entries
> from the machine database which are or have been in mainline, and which
> have been updated within the last twelve months. The above file reflects
> that, and reduces the file down to 1090 lines (including header).
>
> What this means is that any platform in the machine database which has not
> been submitted to mainline for 12 months since it was registered will be
> automatically dropped from the file, and the platform maintainer will need
> to either talk to me to get it reinstated before submission, or update the
> entry in some way to 'freshen' it.
>
> This does have the potential to go wrong if people start randomly changing
> the format of how they write the MACHINE_START() macro. If it's not found
> by:
>
> grep -rh --exclude=include --include='*.c' MACHINE_START arch/arm |
> grep -v '^#' | sed "s@[^(]*(\([^,]*\).*@ ('\1')@;2,\$s@^@,@"
>
> (which generates a subset of SQL) then it won't be kept. In other words,
> one line containing _at least_ this is the safest way:
>
> MACHINE_START(NAME,
>
> but this definitely won't work:
>
> MACHINE_START(
> NAME,
> "Gobovision's Funky Platform")
Note that OMAP references machine_is_omap2evm() yet this has never been
merged.
arch/arm/plat-omap/include/plat/uncompress.h:
DEBUG_LL_OMAP2(1, omap2evm);
so this entry needs to be removed.
next prev parent reply other threads:[~2011-03-20 11:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-20 11:03 Updated mach-types update Russell King - ARM Linux
2011-03-20 11:41 ` Russell King - ARM Linux [this message]
2011-03-24 17:59 ` Tony Lindgren
2011-05-13 11:54 ` Tony Lindgren
2011-05-13 12:19 ` Jarkko Nikula
2011-05-13 14:40 ` [PATCH] omap: Remove support for omap2evm (Re: Updated mach-types update) Tony Lindgren
2011-05-14 16:30 ` Mark Brown
2011-05-16 13:45 ` Liam Girdwood
2011-05-13 14:53 ` Updated mach-types update Tomi Valkeinen
2011-03-21 22:41 ` Detlef Vollmann
2011-03-21 23:10 ` Russell King - ARM Linux
2011-03-21 23:33 ` Detlef Vollmann
2011-03-22 13:19 ` Domenico Andreoli
2011-03-22 19:30 ` Russell King - ARM Linux
2011-03-23 9:31 ` Domenico Andreoli
2011-03-23 16:37 ` H Hartley Sweeten
2011-03-26 22:52 ` Colin Cross
2011-03-26 23:14 ` Russell King - ARM Linux
2011-03-28 18:00 ` Russell King - ARM Linux
2011-03-28 18:02 ` Russell King - ARM Linux
2011-05-21 1:35 ` Jaya Kumar
2011-05-22 9:11 ` Russell King - ARM Linux
2011-05-23 14:52 ` Arnd Bergmann
2011-05-23 14:59 ` Russell King - ARM Linux
2011-05-23 15:10 ` Mark Brown
2011-05-23 15:33 ` Russell King - ARM Linux
2011-05-23 16:39 ` Arnd Bergmann
2011-05-24 11:00 ` Jaya Kumar
2011-05-24 11:51 ` Arnd Bergmann
2011-07-27 12:20 ` Mark Brown
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=20110320114137.GD16646@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).