From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: When does mach-types get updated in a tree?
Date: Mon, 28 Feb 2011 15:49:13 +0000 [thread overview]
Message-ID: <20110228154913.GC1937@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <d2617607-dfa2-4f72-9a42-4345b4a43307@VA3EHSMHS027.ehs.local>
On Mon, Feb 28, 2011 at 08:34:38AM -0700, John Linn wrote:
> > I do think we're heading for a major problem with the mach-types file
> > becoming too big inspite of its brevity. I think I may start marking
> > entries as 'inactive' and therefore omitted from the kernel's tree if
> > they don't appear in mainline within one year of being allocated (or
> > some similar rule.)
> >
>
> Wouldn't device tree help with this problem?
We'll just end up with a string-space problem instead of a number space
problem.
I don't know how many clashing names we end up with today (because the
machine number allocator explicitly prevents it happening) but I would
not be surprised if there weren't clashes occuring with 3500 names
registered.
Having now done some investigations, this is silly. About 86% of the
entries in the machine registry are not merged into the kernel. 48%
of the contents of the machine registry refer to platforms registered
more than two years ago but are not merged into mainline. For four
years, that figure drops to 27%. For one year, it's 64%.
So, merely implmenting a rule which says that entries which haven't
been merged into mainline within 12 months from the date they were last
updated would cut the file down to about 48K, almost 90K smaller. I
think that's worth doing.
next prev parent reply other threads:[~2011-02-28 15:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-26 15:40 When does mach-types get updated in a tree? John Linn
2011-02-28 10:10 ` Russell King - ARM Linux
2011-02-28 14:35 ` John Linn
2011-02-28 15:11 ` Russell King - ARM Linux
2011-02-28 15:34 ` John Linn
2011-02-28 15:49 ` Russell King - ARM Linux [this message]
2011-02-28 16:29 ` Detlef Vollmann
2011-03-15 14:31 ` John Linn
2011-03-15 21:26 ` Russell King - ARM Linux
2011-03-15 21:30 ` John Linn
-- strict thread matches above, loose matches on Subject: below --
2011-02-23 19:06 John Linn
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=20110228154913.GC1937@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).