From: Greg KH <gregkh@linuxfoundation.org>
To: Pavel Machek <pavel@denx.de>
Cc: kernel list <linux-kernel@vger.kernel.org>,
stable@kernel.org, matthias.bgg@gmail.com, neil@brown.name,
thirtythreeforty@gmail.com, christian@lkamp.de,
nishadkamdar@gmail.com, ser.perschin@gmail.com,
blogic@openwrt.org, jan.kiszka@siemens.com
Subject: Re: [stable] Deleting "mt7621-mmc" with "interesting" license?
Date: Thu, 15 Aug 2019 10:44:06 +0200 [thread overview]
Message-ID: <20190815084406.GC3512@kroah.com> (raw)
In-Reply-To: <20190815075927.GC3669@amd>
On Thu, Aug 15, 2019 at 09:59:27AM +0200, Pavel Machek wrote:
> On Thu 2019-08-15 09:51:32, Greg KH wrote:
> > On Thu, Aug 15, 2019 at 09:13:50AM +0200, Pavel Machek wrote:
> > > Hi!
> > >
> > > I realize that "interesting" license is not on a list of bugs suitable
> > > for -stable, but on the other hand, this tends to scare corporate
> > > lawyers... so perhaps we should remove the driver in -stable, too?
> > >
> > > Upstream commit id is 441bf7332d55c4d34afae9ffc3bbec621093f4d1.
> > >
> > > 4.19 has the problematic driver, 4.4 does not.
> >
> > If a lawyer has issues with this, please just upgrade to the latest
> > kernel release :)
>
> We are talking this project:
> https://wiki.linuxfoundation.org/civilinfrastructureplatform/start .
> Upgrading is not an option, but I can take the patch locally.
It does not meet the stable rules, sorry, I'm not going to take it.
> If someone has confirmation that "interesting" license is a mistake
> and it is indeed GPL, that would be nice, too.
Feel free to discus it with the company who wrote the driver :)
good luck!
greg k-h
next prev parent reply other threads:[~2019-08-15 8:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 7:13 [stable] Deleting "mt7621-mmc" with "interesting" license? Pavel Machek
2019-08-15 7:51 ` Greg KH
2019-08-15 7:59 ` Pavel Machek
2019-08-15 8:44 ` Greg KH [this message]
2019-08-15 8:56 ` Pavel Machek
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=20190815084406.GC3512@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=blogic@openwrt.org \
--cc=christian@lkamp.de \
--cc=jan.kiszka@siemens.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=neil@brown.name \
--cc=nishadkamdar@gmail.com \
--cc=pavel@denx.de \
--cc=ser.perschin@gmail.com \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.