From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: omap: introduce OMAP MCOP board file
Date: Tue, 5 Apr 2011 08:46:32 -0700 [thread overview]
Message-ID: <20110405154632.GC17376@atomide.com> (raw)
In-Reply-To: <20110405095119.GD4699@n2100.arm.linux.org.uk>
* Russell King - ARM Linux <linux@arm.linux.org.uk> [110405 02:48]:
>
> I'd suggest holding fire on new stuff.
>
> We *absolutely* *must* show that we're taking Linus' complaint seriously
> and make headway towards consolidating some of the code. I don't see that
> activity as optional.
I agree.
> I've now made the decision (as I mentioned I may do in the thread) that
> for the next merge window I'm only taking consolidations and bug fixes
> through my tree, and I encourage everyone else to do the same. At the
> moment, I'm planning for this up until the next merge window, but if
> sufficient progress hasn't been done, I'll extend it thereafter.
OK
> In other words, no new platform code and no new platform class code.
>
> The longer it takes to get the consolidation effort producing results, the
> longer we will have to keep the restriction in place, and the more painful
> it'll be for people who want to have their platforms merged.
>
> So I hope *no* one is thinking "this isn't my problem, someone else will
> solve it" - if you're thinking that then we're doomed.
Yes we need more people to pitch in to the consolidation process,
so everybody please help where possible.
Regards,
Tony
prev parent reply other threads:[~2011-04-05 15:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 9:32 [PATCH] arm: omap: introduce OMAP MCOP board file Felipe Balbi
2011-04-05 9:36 ` Felipe Balbi
2011-04-05 9:47 ` Fillinger, Michael
2011-04-05 9:51 ` Russell King - ARM Linux
2011-04-05 9:54 ` Felipe Balbi
2011-04-05 15:46 ` Tony Lindgren [this message]
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=20110405154632.GC17376@atomide.com \
--to=tony@atomide.com \
--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).