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:11:00 +0000 [thread overview]
Message-ID: <20110228151100.GB1937@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <0812376c-ea4b-4185-aa6e-6fb582dce21f@VA3EHSMHS032.ehs.local>
On Mon, Feb 28, 2011 at 07:35:57AM -0700, John Linn wrote:
> What is your suggestion to people with regards to patches that need the
> update?
The only suggestion I can make is: don't wait until the last minute before
putting something into the machine registry, because you will get into
these kinds of problems.
If I do an update now, it'll be the second time it's happened in February.
It's likely it will need another update just before the merge window too
in 3-4 weeks time.
So really all that I can say is that people need to ensure that they get
stuff from the machine registry earlier rather than later.
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.)
> I'm open to suggestions, just trying to work with everyone the best way
> to get Xilinx patches into the system.
The only thing I can think is to wait a couple more weeks and I'll see
about doing an update mid-March. Maybe by then we can have a smaller
file...
next prev parent reply other threads:[~2011-02-28 15:11 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 [this message]
2011-02-28 15:34 ` John Linn
2011-02-28 15:49 ` Russell King - ARM Linux
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=20110228151100.GB1937@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).