From: Sasha Levin <sashal@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Salvatore Bonaccorso" <carnil@debian.org>,
stable <stable@vger.kernel.org>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
NeilBrown <neil@brown.name>,
"George Hilliard" <thirtythreeforty@gmail.com>,
"Christian Lütke-Stetzkamp" <christian@lkamp.de>,
"Nishad Kamdar" <nishadkamdar@gmail.com>,
"Sergej Perschin" <ser.perschin@gmail.com>,
"John Crispin" <blogic@openwrt.org>
Subject: Re: "Backport" of 441bf7332d55 ("staging: m57621-mmc: delete driver from the tree.") as well for older stable series still supported?
Date: Thu, 15 Apr 2021 07:20:53 -0400 [thread overview]
Message-ID: <YHghlaftXxH49lUy@sashalap> (raw)
In-Reply-To: <YHgIEbn1UqhXHdzr@kroah.com>
On Thu, Apr 15, 2021 at 11:32:01AM +0200, Greg Kroah-Hartman wrote:
>On Wed, Apr 14, 2021 at 09:44:06PM +0200, Salvatore Bonaccorso wrote:
>> 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?
>
>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!
--
Thanks,
Sasha
next prev parent reply other threads:[~2021-04-15 11:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 19:44 "Backport" of 441bf7332d55 ("staging: m57621-mmc: delete driver from the tree.") as well for older stable series still supported? Salvatore Bonaccorso
2021-04-15 9:32 ` Greg Kroah-Hartman
2021-04-15 11:20 ` Sasha Levin [this message]
2021-04-15 13:57 ` Salvatore Bonaccorso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YHghlaftXxH49lUy@sashalap \
--to=sashal@kernel.org \
--cc=blogic@openwrt.org \
--cc=carnil@debian.org \
--cc=christian@lkamp.de \
--cc=gregkh@linuxfoundation.org \
--cc=matthias.bgg@gmail.com \
--cc=neil@brown.name \
--cc=nishadkamdar@gmail.com \
--cc=ser.perschin@gmail.com \
--cc=stable@vger.kernel.org \
--cc=thirtythreeforty@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox