public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Salvatore Bonaccorso <carnil@debian.org>
To: stable <stable@vger.kernel.org>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Sasha Levin" <sashal@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: "Backport" of 441bf7332d55 ("staging: m57621-mmc: delete driver from the tree.") as well for older stable series still supported?
Date: Wed, 14 Apr 2021 21:44:06 +0200	[thread overview]
Message-ID: <YHdGBm2WHb5I8FFW@eldamar.lan> (raw)

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?

Regards,
Salvatore

             reply	other threads:[~2021-04-14 19:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-14 19:44 Salvatore Bonaccorso [this message]
2021-04-15  9:32 ` "Backport" of 441bf7332d55 ("staging: m57621-mmc: delete driver from the tree.") as well for older stable series still supported? Greg Kroah-Hartman
2021-04-15 11:20   ` Sasha Levin
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=YHdGBm2WHb5I8FFW@eldamar.lan \
    --to=carnil@debian.org \
    --cc=blogic@openwrt.org \
    --cc=christian@lkamp.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=matthias.bgg@gmail.com \
    --cc=neil@brown.name \
    --cc=nishadkamdar@gmail.com \
    --cc=sashal@kernel.org \
    --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