On Thu, 06 Dec 2007 11:38:43 PST, Greg KH said: > > Would I be remiss in hypothesising that something in gregkh-driver-kobject-* > > changed something, and now we need a agk-dm-dm-kobject-fixupage.patch? > > I don't know, it all depends on what is in the dm patches. Hopefully > everything that I have changed will manifest with a build breakage to > obviously detect that something needs to be fixed up. > > But I've been known to mess things up that I didn't intend to :) Given that it *didn't* totally break the build, it's likely a fencepost error or some similar issue... > If there's anything that I can do to test this, please let me know. I wanted to give a heads-up, in case there was a D'Oh! patch hiding. At worst, I just need another 6 or 7 bisects to figure out which of those 120-ish patches is the culprit. With luck I'll end up stopped on a patch that in retrospect was obviously busticated. If not, we'll have to apply the usual more drastic measures. If you don't have a box that's already demonstrating it, and you don't have any obvious candidates, it's likely that the most productive use of everybody's time is for you to chase down any other kobject issues while I bisect the problem down further...
Attachment:
pgpTjKk0uYsti.pgp
Description: PGP signature
-- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
