From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Error for machine_is_m28evk
Date: Tue, 8 Nov 2011 13:37:44 +0000 [thread overview]
Message-ID: <20111108133744.GE12913@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20111108125346.GA7563@S2100-06.ap.freescale.net>
On Tue, Nov 08, 2011 at 08:53:47PM +0800, Shawn Guo wrote:
> On Tue, Nov 08, 2011 at 08:53:50AM +0000, Russell King - ARM Linux wrote:
> [...]
> >
> > Maybe the answer is to just update the file anyway, and ignore peoples
> > complaints that their entries aren't present until they come to their
> > senses and start COMMUNICATING properly about issues they have with
> > their fscked up entry in the database.
> >
> So I assume that you will update mach-types for -rc2. Otherwise,
> please let me know, and I will send a patch to disable m28evk build
> from mxs_defconfig for -rc2.
Well, I chickened out of doing it in September. We're now in November,
and even more entries will be deleted (because they've been lost off
the back end of the 12 month rule.)
Maybe it would be much easier to reduce the 12 month rule down to 4
months (to cover one kernel cycle and a little bit more) so that people
then know that they _have_ to talk to me. Or maybe we just don't include
anything at all which doesn't appear in mainline.
Or maybe I get Arnd to run a script over the arm-soc tree regularly and
send me an email, which'll mean I'll have to _manually_ update the
database with what's in mainline. (With the new security arrangements
with kernel.org, I can't even get *easy* access to the arm-soc tree to
just run a script over it to find what's been added.)
This task was soo much easier when most stuff was flowing through my
tree, because I'd then have the majority of new platforms, and therefore
know what was required.
Whatever way you look at it, this is a hard problem to solve given the
distributed nature of git trees.
Well, I guess we're at -rc1, and _now_ would be a good time to delete
the entries and stuff it in to linux-next. That will give people a chance
to notice that they're gone - though:
(a) I have _ZERO_ confidence that people still won't shout at me for not
telling them personally that I've deleted their entry.
(b) with the loss of facilities like kautobuild (no one noticed for six
months that simtec had shut it down...), we have lost any kind of
automated detection for these kinds of issues.
So, I guess I'm just going to not give a damn about stuff which gets
removed. Which includes ALSA using machine_is_xxx() for platforms which
aren't currently merged.
next prev parent reply other threads:[~2011-11-08 13:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 1:49 Error for machine_is_m28evk Fabio Estevam
2011-11-08 5:16 ` Shawn Guo
2011-11-08 6:30 ` Stefano Babic
2011-11-08 7:53 ` Uwe Kleine-König
2011-11-08 8:09 ` Jason Liu
2011-11-08 8:53 ` Russell King - ARM Linux
2011-11-08 12:53 ` Shawn Guo
2011-11-08 13:37 ` Russell King - ARM Linux [this message]
2011-11-08 14:05 ` Will Deacon
2011-11-08 14:36 ` Arnaud Patard (Rtp)
2011-11-08 14:45 ` Russell King - ARM Linux
2011-11-08 14:53 ` Vincent Sanders
2011-11-16 5:59 ` Shawn Guo
2011-11-16 8:42 ` Russell King - ARM Linux
2011-11-16 13:58 ` Shawn Guo
2011-11-16 18:48 ` Uwe Kleine-König
2011-11-16 22:28 ` Shawn Guo
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=20111108133744.GE12913@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