On Tue, 12 May 2015 23:38:43 +0200 Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote: > > What happens quite frequently is that we do something for x86 with the > > expectation that other architectures will follow along, but this > > doesn't happen. The arch maintainers simply didn't know about it or > > nobody nags them. Nothing happens and inconsistencies hang around for > > years. eg, http://lkml.iu.edu/hypermail/linux/kernel/1504.2/04993.html > > > > I'm thinking we should find a way to do this better. One way might be > > to maintain a Documentation/arch-todo which identifies each item, has a > > little list of what-to-do instructions and perhaps a list of the > > not-yet-done architectures. Basically a way for everyone to > > communicate at the arch maintainers. > > If only there was a linux-arch list to which arch maintainers should > subscribe... oh wait :-) It was I who got linux-arch established, so I'm fairly familiar with it. (12 years ago, gad). I don't think it's been very successful, particularly for this purpose. A whole pile of randomly cc'ed lkml overflow which we're relying on each individual maintainer to sift through and pluck out particular action items then later remember to implement them. It's disorganized and has too many cracks for things to fall through. -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
