"Backport" of 441bf7332d55 ("staging: m57621-mmc: delete driver from the tree.") as well for older stable series still supported?

Hi Greg, Sasha, all,

Prompted by https://bugs.debian.org/986949 it looks that files with prolematic license are present in stable series in drivers/staging/mt7621-mmc/ prior to 441bf7332d55 ("staging:
m57621-mmc: delete driver from the tree.") where those were removed in 5.2-rc1.

As the license text at it is presented is problematic at best, would this removal make sense as well in the current other stable series which contain it? The files goes back to it's addition in 4.17-rc1.

So it would remain v4.19.y where the files should/can be removed as well from the staging area?

Quoted 12 lines · Salvatore Bonaccorso

Hi Greg, Sasha, all,

Prompted by https://bugs.debian.org/986949 it looks that files with prolematic license are present in stable series in drivers/staging/mt7621-mmc/ prior to 441bf7332d55 ("staging:
m57621-mmc: delete driver from the tree.") where those were removed in 5.2-rc1.

As the license text at it is presented is problematic at best, would this removal make sense as well in the current other stable series which contain it? The files goes back to it's addition in 4.17-rc1.

Quoted 2 lines

So it would remain v4.19.y where the files should/can be removed as well from the staging area?

Yeah, it is odd, and we probably should not continue to distribute new updates with it in the tree.

As the commit does not backport cleanly, can you provide a working backport that I can apply?

Quoted 16 lines · Greg Kroah-Hartman

Quoted 14 lines · Salvatore Bonaccorso

Hi Greg, Sasha, all,

Prompted by https://bugs.debian.org/986949 it looks that files with prolematic license are present in stable series in drivers/staging/mt7621-mmc/ prior to 441bf7332d55 ("staging:
m57621-mmc: delete driver from the tree.") where those were removed in 5.2-rc1.

As the license text at it is presented is problematic at best, would this removal make sense as well in the current other stable series which contain it? The files goes back to it's addition in 4.17-rc1.

So it would remain v4.19.y where the files should/can be removed as well from the staging area?

Quoted 5 lines

Yeah, it is odd, and we probably should not continue to distribute new updates with it in the tree.

As the commit does not backport cleanly, can you provide a working backport that I can apply?

I killed it :) Thanks for the heads up!