On Tue, Sep 20, 2022 at 07:24:54AM +0200, Mauro Carvalho Chehab wrote: > Hi Luis, > > On Mon, 9 May 2022 13:38:28 -0700 > Luis Chamberlain <mcgrof@xxxxxxxxxx> wrote: > > > On Mon, May 09, 2022 at 06:23:35PM +0200, Mauro Carvalho Chehab wrote: > > > Currently, kernel/module annotates module dependencies when > > > request_symbol is used, but it doesn't cover more complex inter-driver > > > dependencies that are subsystem and/or driver-specific. > > > > > > > At this pount v5.18-rc7 is out and so it is too late to soak this > > in for the proper level of testing I'd like to see for modules-next. > > So I can review this after the next merge window. I'd want to beat > > the hell out of this and if possible I'd like to see if we can have > > some test coverage for the intended goal and how to break it. > > Any news with regards to this patch series? 0-day had a rant about a bug with it, it would be wonderful if you can fix that bug and rebase. Yet again we're now on v6.0-rc7 but it doesn't mean we can't start testing all this on linux-next. I can just get this merged to linux-next as soon as this is ready for a new spin, but we certainly will have to wait until 6.2 as we haven't yet gotten proper coverage for this on v6.1. Is there any testing situations you can think of using which can demo this a bit more separately from existing drivers, perhaps a new selftests or something? Luis
