From: dv@vollmann.ch (Detlef Vollmann)
To: linux-arm-kernel@lists.infradead.org
Subject: When does mach-types get updated in a tree?
Date: Mon, 28 Feb 2011 17:29:07 +0100 [thread overview]
Message-ID: <4D6BCD53.5070106@vollmann.ch> (raw)
In-Reply-To: <20110228154913.GC1937@n2100.arm.linux.org.uk>
On 02/28/11 16:49, Russell King - ARM Linux 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.)
> 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.
Hmmm, we have currently two entries registered for CPU modules we
use in a number of internal projects. Though we're happy to
share the code for these modules, we never intended to propose it
for mainline (as nobody alse can use these modules).
What do you propose for such cases?
Do you have a block of numbers for "private use"?
Detlef
next prev parent reply other threads:[~2011-02-28 16:29 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
2011-02-28 16:29 ` Detlef Vollmann [this message]
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=4D6BCD53.5070106@vollmann.ch \
--to=dv@vollmann.ch \
--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).