On Thu, 8 Jan 2015, Catalin Marinas wrote: > On Thu, Jan 08, 2015 at 04:57:05PM +0000, Russell King - ARM Linux wrote: > > On Thu, Jan 08, 2015 at 04:41:12PM +0000, Catalin Marinas wrote: > > > On Thu, Jan 08, 2015 at 04:34:50PM +0000, Russell King - ARM Linux wrote: > > > > On Thu, Jan 08, 2015 at 04:19:08PM +0000, Catalin Marinas wrote: > > > > > I really think we should stop this thread. User ABI breakage fixed > > > > > now. > > > > > > > > No. Vince's email shows a more serious problem. > > > > > > > > The ABI breakage issue was reported before the patches were apparently > > > > merged, but that information seems to have been lost. We need to > > > > understand how that happened so similar instances don't happen in the > > > > future. > > > > > > FYI, searching for "Vince Weaver" and "bogomips" found this: > > > > > > https://lkml.org/lkml/2013/7/11/454 > > > > Gah. > > > > It looks like the report was made by hanging it into a totally different > > thread to the patches which caused the problem, and which went nowhere > > near the ARM kernel mailing lists. > > > > At least that explains why people like me who really need to know this > > stuff were not aware of the issue. > > > > One thing I still can't get my head around though is... Vince reported > > the breakage on 11 July 2013, but the patch is dated 30 August and I > > merged it 2 September. So, how did Vince know about it to report the > > ABI breakage? Had it been sitting somewhere else? > > Well, the patch may have been on the list, acked, before July but it > only went to the patch system on the 30th of August. Vince probably > concluded that it will go in once acked on the list.
Yes, it looks like it went out on the linux-arm-kernel list on 3 May 2013. http://lists.infradead.org/pipermail/linux-arm-kernel/2013-May/166728.html I don't follow that list though, so someone must have pointed me to the posting. Though there must have been something else too, I definitely recall reading a long rant about how annoying it was that everyone was reporting bogomips value errors and this was the best way to handle things. All of the postings of the patch I can find are much more laid back. Mostly why I didn't push the issue though was all the pushback I've gotten over the years for trying to get perf_event ABI breaks reverted (I've never successfully managed to get that to happen). Vince -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
