On Thu, Mar 25, 2021 at 03:46:10PM +0100, Jan Kiszka wrote: > On 15.03.21 17:10, Rob Springer wrote: > > Acked-by: Rob Springer <rspringer@xxxxxxxxxx> > > > > > > On Mon, Mar 15, 2021 at 8:44 AM <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > >> > >> From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> > >> > >> As none of the proposed things that need to be changed in the gasket > >> drivers have ever been done, and there has not been any forward progress > >> to get this out of staging, it seems totally abandonded so remove the > >> code entirely so that people do not spend their time doing tiny cleanups > >> for code that will never get out of staging. > >> > >> If this code is actually being used, it can be reverted simply and then > >> cleaned up properly, but as it is abandoned, let's just get rid of it. > >> > >> Cc: Rob Springer <rspringer@xxxxxxxxxx> > >> Cc: Todd Poynor <toddpoynor@xxxxxxxxxx> > >> Cc: Ben Chan <benchan@xxxxxxxxxxxx> > >> Cc: Richard Yeh <rcy@xxxxxxxxxx> > >> Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> > > OK, so is there a plan of the HW vendor to improve the user experience > for this hardware? Is there a different software architecture in sight > which will not need a kernel driver? What hardware vendor makes this thing? What systems require it? And why can't you use UIO instead? > Just wondering loudly while fiddling with dkms packages and starring at > the code diffs between what was removed here and what I still have to > install manually from remote sources. Where are the remote sources for this thing and why didn't they ever get synced into the kernel tree? thanks, greg k-h
