linux-spdx.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <jejb@linux.ibm.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Roman Bolshakov <r.bolshakov@yadro.com>,
	"Martin K . Petersen" <martin.petersen@oracle.com>,
	linux-scsi@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Anil Gurumurthy <anil.gurumurthy@qlogic.com>,
	Sudarsana Kalluru <sudarsana.kalluru@qlogic.com>,
	linux-spdx@vger.kernel.org, linux-kernel@vger.kernel.org,
	GR-QLogic-Storage-Upstream@marvell.com,
	Arun Easi <aeasi@marvell.com>
Subject: Re: [PATCH] MAINTAINERS: orphan sections with qlogic.com group alias
Date: Fri, 28 Aug 2020 08:38:08 -0700	[thread overview]
Message-ID: <1598629088.3883.27.camel@linux.ibm.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2008281719290.11677@felia>

On Fri, 2020-08-28 at 17:28 +0200, Lukas Bulwahn wrote:
> 
> On Fri, 28 Aug 2020, James Bottomley wrote:
> 
> > On Fri, 2020-08-28 at 15:30 +0200, Lukas Bulwahn wrote:
> > > 
> > > On Fri, 28 Aug 2020, Roman Bolshakov wrote:
> > > 
> > > > On Fri, Aug 28, 2020 at 09:08:24AM +0200, Lukas Bulwahn wrote:
> > > > > Previous attempts of getting an answer from the qlogic.com
> > > > > group alias, i.e., QLogic-Storage-Upstream@qlogic.com, have
> > > > > remained unanswered; see links below.
> > > > > 
> > > > > Mark those sections Orphan to prepare their deletion or give
> > > > > an actual person a chance to step up to maintain those
> > > > > drivers.
> > > > > 
> > > > > Link: https://lore.kernel.org/linux-spdx/20190606205526.44755
> > > > > 8989
> > > > > @linutronix.de
> > > > > Link: https://lore.kernel.org/linux-spdx/alpine.DEB.2.21.2006
> > > > > 3006
> > > > > 44130.4919@felia
> > > > > Link: https://lore.kernel.org/linux-spdx/alpine.DEB.2.21.2008
> > > > > 2707
> > > > > 40140.31123@felia
> > > > > 
> > > > 
> > > > CC'd Arun,
> > > > 
> > > > I think it's worth to update the alias to:
> > > > 
> > > > GR-QLogic-Storage-Upstream@marvell.com
> > > > 
> > > 
> > > So, if these drivers are not orphans, you can answer Thomas
> > > Gleixner's original email from 2019. If you can quickly ack that
> > > patch set, I am happy to do the donkey work to get this apply
> > > nicely on the current master (please CC me on that response).
> > 
> > I have to wonder what the object is here: to get the problem fixed
> > or to make a public spectacle?
> > 
> 
> Let us get the problem fixed; no spectacle here.
> 
> > Because if the object had been to get the issue fixed, waiting a
> > year before escalating to the SCSI list isn't the best way to
> > achieve outcomes, nor is now demanding that the drivers be orphaned
> > for lack of response to you ... particularly as you've seen the
> > drivers updated over that time if you actually follow kernel
> > releases.
> > 
> 
> I just followed Greg KH's advice; spdx licensing clean-up is not the
> top most priority thing; so it just happened to be laying around for
> a year.  Feel free to ignore this patch and we solve the problem
> instead.

OK, that's the plan then.

> > Qlogic or now Marvell tends to rely somewhat heavily on outsourcing
> > for driver maintenance and support.  Outsourcers, fairly obviously,
> > aren't going to respond to legal issues like this which are outside
> > of their remit.  What needs to happen is that someone needs to find
> > a person
> > within the Qlogic org who can get this fixed ... possibly involving
> > explaining the actual issue along the way.  Would you like us to
> > use
> > our contacts to do that?
> > 
> 
> Yes, I (and I will bet the licensing clean-up janitors) welcome if
> that legal question can be resolved and the kernel can be cleaned up
> from unneeded files.

OK, because of the high turn over at the Qlogic division due to the
takeover, this will take us some time, but we'll try to find the right
people at least to explain the issue to.

James


  reply	other threads:[~2020-08-28 15:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-28  7:08 [PATCH] MAINTAINERS: orphan sections with qlogic.com group alias Lukas Bulwahn
2020-08-28  9:17 ` Roman Bolshakov
2020-08-28 10:00   ` Greg Kroah-Hartman
2020-08-28 13:30   ` Lukas Bulwahn
2020-08-28 15:02     ` James Bottomley
2020-08-28 15:28       ` Lukas Bulwahn
2020-08-28 15:38         ` James Bottomley [this message]
2020-08-28 15:39     ` Martin K. Petersen
2020-08-28 15:46       ` Lukas Bulwahn
2020-09-08  6:58       ` [EXT] " Arun Easi

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=1598629088.3883.27.camel@linux.ibm.com \
    --to=jejb@linux.ibm.com \
    --cc=GR-QLogic-Storage-Upstream@marvell.com \
    --cc=aeasi@marvell.com \
    --cc=anil.gurumurthy@qlogic.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-spdx@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=martin.petersen@oracle.com \
    --cc=r.bolshakov@yadro.com \
    --cc=sudarsana.kalluru@qlogic.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;
as well as URLs for NNTP newsgroup(s).