Skip to contentSkip to conversation

MAINTAINERS: orphan sections with qlogic.com group alias

PATCH In review Lukas Bulwahn 6 participants 10 messages Aug 28, 2020 – Sep 8, 2020

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 MAINTAINERS: orphan sections with qlogic.com group alias

Previous attempts of getting an answer from the qlogic.com group alias, i.e., [email protected], 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.

---
applies cleanly on current master and next-20200828

James, Martin, please pick this minor non-urgent patch.

Anil, Sudarsana, if these drivers are still maintained by qlogic, please provide actual names of people that maintain these drivers.

 MAINTAINERS | 9 +++------
 1 file changed, 3 insertions(+), 6 deletions(-)
MAINTAINERS +3 -6
index 3b186ade3597..415058b48a2e 100644
@@ -3507,15 +3507,13 @@ F:	drivers/net/ethernet/broadcom/bnx2.*
 F:	drivers/net/ethernet/broadcom/bnx2_*
 
 BROADCOM BNX2FC 10 GIGABIT FCOE DRIVER
-M:	[email protected]
 L:	[email protected]
-S:	Supported
+S:	Orphan
 F:	drivers/scsi/bnx2fc/
 
 BROADCOM BNX2I 1/10 GIGABIT iSCSI DRIVER
-M:	[email protected]
 L:	[email protected]
-S:	Supported
+S:	Orphan
 F:	drivers/scsi/bnx2i/
 
 BROADCOM BNX2X 10 GIGABIT ETHERNET DRIVER
@@ -14212,9 +14210,8 @@ F:	Documentation/networking/device_drivers/ethernet/qlogic/LICENSE.qla3xxx
 F:	drivers/net/ethernet/qlogic/qla3xxx.*
 
 QLOGIC QLA4XXX iSCSI DRIVER
-M:	[email protected]
 L:	[email protected]
-S:	Supported
+S:	Orphan
 F:	Documentation/scsi/LICENSE.qla4xxx
 F:	drivers/scsi/qla4xxx/
 
Signature · 1 line
2.17.1
#1 lore raw
Quoted 60 lines · Lukas Bulwahn

Previous attempts of getting an answer from the qlogic.com group alias, i.e., [email protected], 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.

---
applies cleanly on current master and next-20200828

James, Martin, please pick this minor non-urgent patch.

Anil, Sudarsana, if these drivers are still maintained by qlogic, please provide actual names of people that maintain these drivers.

 MAINTAINERS | 9 +++------
 1 file changed, 3 insertions(+), 6 deletions(-)
MAINTAINERS +3 -6
index 3b186ade3597..415058b48a2e 100644
@@ -3507,15 +3507,13 @@ F:	drivers/net/ethernet/broadcom/bnx2.*
 F:	drivers/net/ethernet/broadcom/bnx2_*
 
 BROADCOM BNX2FC 10 GIGABIT FCOE DRIVER
-M:	[email protected]
 L:	[email protected]
-S:	Supported
+S:	Orphan
 F:	drivers/scsi/bnx2fc/
 
 BROADCOM BNX2I 1/10 GIGABIT iSCSI DRIVER
-M:	[email protected]
 L:	[email protected]
-S:	Supported
+S:	Orphan
 F:	drivers/scsi/bnx2i/
 
 BROADCOM BNX2X 10 GIGABIT ETHERNET DRIVER
@@ -14212,9 +14210,8 @@ F:	Documentation/networking/device_drivers/ethernet/qlogic/LICENSE.qla3xxx
 F:	drivers/net/ethernet/qlogic/qla3xxx.*
 
 QLOGIC QLA4XXX iSCSI DRIVER
-M:	[email protected]
 L:	[email protected]
-S:	Supported
+S:	Orphan
 F:	Documentation/scsi/LICENSE.qla4xxx
 F:	drivers/scsi/qla4xxx/
 
Signature · 1 line
2.17.1

CC'd Arun,

I think it's worth to update the alias to:

[email protected]

#2 lore raw
Quoted 64 lines · Roman Bolshakov
Quoted 60 lines · Lukas Bulwahn

Previous attempts of getting an answer from the qlogic.com group alias, i.e., [email protected], 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.

---
applies cleanly on current master and next-20200828

James, Martin, please pick this minor non-urgent patch.

Anil, Sudarsana, if these drivers are still maintained by qlogic, please provide actual names of people that maintain these drivers.

 MAINTAINERS | 9 +++------
 1 file changed, 3 insertions(+), 6 deletions(-)
MAINTAINERS +3 -6
index 3b186ade3597..415058b48a2e 100644
@@ -3507,15 +3507,13 @@ F:	drivers/net/ethernet/broadcom/bnx2.*
 F:	drivers/net/ethernet/broadcom/bnx2_*
 
 BROADCOM BNX2FC 10 GIGABIT FCOE DRIVER
-M:	[email protected]
 L:	[email protected]
-S:	Supported
+S:	Orphan
 F:	drivers/scsi/bnx2fc/
 
 BROADCOM BNX2I 1/10 GIGABIT iSCSI DRIVER
-M:	[email protected]
 L:	[email protected]
-S:	Supported
+S:	Orphan
 F:	drivers/scsi/bnx2i/
 
 BROADCOM BNX2X 10 GIGABIT ETHERNET DRIVER
@@ -14212,9 +14210,8 @@ F:	Documentation/networking/device_drivers/ethernet/qlogic/LICENSE.qla3xxx
 F:	drivers/net/ethernet/qlogic/qla3xxx.*
 
 QLOGIC QLA4XXX iSCSI DRIVER
-M:	[email protected]
 L:	[email protected]
-S:	Supported
+S:	Orphan
 F:	Documentation/scsi/LICENSE.qla4xxx
 F:	drivers/scsi/qla4xxx/
 
Signature · 1 line
2.17.1

CC'd Arun,

Quoted 3 lines

I think it's worth to update the alias to:

[email protected]

Again, no, please remove aliases and use real names and email addresses, otherwise accountability is lost over time, as we have seen constantly.

thanks,

greg k-h

#3 lore raw
In reply to Roman Bolshakov
Quoted 13 lines · Roman Bolshakov
Quoted 11 lines · Lukas Bulwahn

Previous attempts of getting an answer from the qlogic.com group alias, i.e., [email protected], 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.

Quoted 6 lines

CC'd Arun,

I think it's worth to update the alias to:

[email protected]

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).

Lukas

#4 lore raw
Quoted 23 lines · Lukas Bulwahn
Quoted 20 lines · Roman Bolshakov
Quoted 7 lines · Lukas Bulwahn

Previous attempts of getting an answer from the qlogic.com group alias, i.e., [email protected], 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.

Quoted 7 lines

@linutronix.de

44130.4919@felia

40140.31123@felia

CC'd Arun,

I think it's worth to update the alias to:

Quoted 7 lines
Quoted 2 lines

[email protected]

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?

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.

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?

James

#5 lore raw
Quoted 27 lines · James Bottomley
Quoted 26 lines · Lukas Bulwahn
Quoted 22 lines · Roman Bolshakov
Quoted 7 lines · Lukas Bulwahn

Previous attempts of getting an answer from the qlogic.com group alias, i.e., [email protected], 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.

Quoted 7 lines

@linutronix.de

44130.4919@felia

40140.31123@felia

CC'd Arun,

I think it's worth to update the alias to:

[email protected]

Quoted 8 lines
Quoted 4 lines

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.

Quoted 6 lines

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.

Quoted 8 lines

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.

Lukas

#6 lore raw
Quoted 53 lines · Lukas Bulwahn
Quoted 31 lines · James Bottomley
Quoted 30 lines · Lukas Bulwahn
Quoted 26 lines · Roman Bolshakov
Quoted 9 lines · Lukas Bulwahn

Previous attempts of getting an answer from the qlogic.com group alias, i.e., [email protected], 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.

Quoted 9 lines

8989
@linutronix.de

3006
44130.4919@felia

2707
40140.31123@felia

CC'd Arun,

I think it's worth to update the alias to:

[email protected]

Quoted 8 lines
Quoted 4 lines

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.

Quoted 7 lines

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.

Quoted 4 lines

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.

Quoted 11 lines
Quoted 10 lines

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?

Quoted 3 lines

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

#7 lore raw
In reply to Lukas Bulwahn

Lukas,

Quoted 4 lines

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).

This is the first I hear of this since the patches weren't CC:ed to linux-scsi. And not all of these changes pertain to storage drivers but to networking so I am also not sure that mails sent to the above Storage alias would have ended up in the right place.

But we'll get this fixed up. Reaching out to our contacts at Marvell.

Signature · 1 line
Martin K. Petersen	Oracle Linux Engineering
#8 lore raw
Quoted 8 lines · Martin K. Petersen

Lukas,

Quoted 4 lines

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).

Quoted 7 lines

This is the first I hear of this since the patches weren't CC:ed to linux-scsi. And not all of these changes pertain to storage drivers but to networking so I am also not sure that mails sent to the above Storage alias would have ended up in the right place.

But we'll get this fixed up. Reaching out to our contacts at Marvell.

Thanks, Martin, it is appreciated.

Lukas

#9 lore raw
In reply to Martin K. Petersen
Quoted 8 lines · Martin K. Petersen

Lukas,

Quoted 4 lines

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).

Quoted 7 lines

This is the first I hear of this since the patches weren't CC:ed to linux-scsi. And not all of these changes pertain to storage drivers but to networking so I am also not sure that mails sent to the above Storage alias would have ended up in the right place.

But we'll get this fixed up. Reaching out to our contacts at Marvell.

Just to keep this thread updated, we are checking with the legal before ack-ing the change on spdx. Nilesh has already updated Thomas G. about this on the orignal spdx thread.

Regards,
-Arun
PS: Thanks Roman for the CC. These days our spam filters are a little
unfriendly towards the linux-* e-mails.