From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: qla2xxx-upstream@qlogic.com, QLogic-Storage-Upstream@qlogic.com,
GR-Linux-NIC-Dev@marvell.com, Nilesh Javali <njavali@marvell.com>,
Shahed Shaikh <shshaikh@marvell.com>,
Manish Chopra <manishc@marvell.com>
Cc: linux-spdx@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>
Subject: SECOND REMINDER on Qlogic driver license conversion
Date: Thu, 27 Aug 2020 08:00:17 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.2008270740140.31123@felia> (raw)
Dear Qlogic driver maintainers, dear Nilesh, deat Shahed, dear Manish,
during an unrelated kernel clean-up task, I noticed some LICENSE files for
the qlogic drivers hanging around in Documentation.
Thomas Gleixner has provided you a patch series in June 2019 to pick up or
simply add a Reviewed-by tag here:
https://lore.kernel.org/linux-spdx/20190606205526.447558989@linutronix.de
As it seems from the public mailing list archive, you have never responded
to Thomas' request. If you could indicate that the change is fine for you,
I am happy to rebase the patch series to the current next tree, so that
Thomas can pick that up and let it travel through the spdx tree to Linus
for the next release.
See first reminder here:
https://lore.kernel.org/linux-spdx/alpine.DEB.2.21.2006300644130.4919@felia/
Just to let you know, I will send a third reminder in a few months, and
if there is no response to that, I will just send a patch to mark those
drivers where QLogic-Storage-Upstream@qlogic.com or
GR-Linux-NIC-Dev@marvell.com are maintainers as Orphaned, just to keep
MAINTAINERS reflect the actual state.
Best regards,
Lukas
next reply other threads:[~2020-08-27 6:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 6:00 Lukas Bulwahn [this message]
2020-08-27 12:18 ` SECOND REMINDER on Qlogic driver license conversion Greg KH
2020-08-31 11:53 ` [EXT] " Nilesh Javali
2020-09-04 8:30 ` Igor Russkikh
2020-09-09 5:19 ` Nilesh Javali
2020-09-09 6:37 ` Lukas Bulwahn
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=alpine.DEB.2.21.2008270740140.31123@felia \
--to=lukas.bulwahn@gmail.com \
--cc=GR-Linux-NIC-Dev@marvell.com \
--cc=QLogic-Storage-Upstream@qlogic.com \
--cc=linux-spdx@vger.kernel.org \
--cc=manishc@marvell.com \
--cc=njavali@marvell.com \
--cc=qla2xxx-upstream@qlogic.com \
--cc=shshaikh@marvell.com \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).