Skip to contentSkip to conversation

staging: Remove the drivers for the Unisys s-Par

PATCH Superseded Fabio M. De Francesco 3 participants 7 messages Apr 12, 2022 – Apr 13, 2022 Staging

v1 of 3 Superseded Latest is v3 →

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 staging: Remove the drivers for the Unisys s-Par

The Unisys sub-tree contains three drivers for the "Unisys Secure Partition" (s-Par(R)): visorhba, visorinput, visornic.

They have no maintainers, in fact the only one that is listed in MAINTAINERS has an unreacheable email address. During 2021 and 2022 several patches have been submitted to these drivers but nobody at Unisys cared of reviewing the changes. Probably, also the "sparmaintainer" internal list of unisys.com is not anymore read by interested Unisys' engineers.

Therefore, remove the ./unisys subdirectory of staging and delete the related entries in the MAINTAINERS, Kconfig, Makefile files.

---
 MAINTAINERS                                   |    8 -
 drivers/staging/Kconfig                       |    2 -
 drivers/staging/Makefile                      |    1 -
 .../ABI/sysfs-platform-visorchipset           |   89 -
 .../staging/unisys/Documentation/overview.txt |  337 ---
 drivers/staging/unisys/Kconfig                |   16 -
 drivers/staging/unisys/MAINTAINERS            |    5 -
 drivers/staging/unisys/Makefile               |    7 -
 drivers/staging/unisys/TODO                   |   16 -
 drivers/staging/unisys/include/iochannel.h    |  571 -----
 drivers/staging/unisys/visorhba/Kconfig       |   15 -
 drivers/staging/unisys/visorhba/Makefile      |   10 -
 .../staging/unisys/visorhba/visorhba_main.c   | 1142 ---------
 drivers/staging/unisys/visorinput/Kconfig     |   16 -
 drivers/staging/unisys/visorinput/Makefile    |    7 -
 .../staging/unisys/visorinput/visorinput.c    |  788 ------
 drivers/staging/unisys/visornic/Kconfig       |   16 -
 drivers/staging/unisys/visornic/Makefile      |   10 -
 .../staging/unisys/visornic/visornic_main.c   | 2131 -----------------
 19 files changed, 5187 deletions(-)
 delete mode 100644 drivers/staging/unisys/Documentation/ABI/sysfs-platform-visorchipset
 delete mode 100644 drivers/staging/unisys/Documentation/overview.txt
 delete mode 100644 drivers/staging/unisys/Kconfig
 delete mode 100644 drivers/staging/unisys/MAINTAINERS
 delete mode 100644 drivers/staging/unisys/Makefile
 delete mode 100644 drivers/staging/unisys/TODO
 delete mode 100644 drivers/staging/unisys/include/iochannel.h
 delete mode 100644 drivers/staging/unisys/visorhba/Kconfig
 delete mode 100644 drivers/staging/unisys/visorhba/Makefile
 delete mode 100644 drivers/staging/unisys/visorhba/visorhba_main.c
 delete mode 100644 drivers/staging/unisys/visorinput/Kconfig
 delete mode 100644 drivers/staging/unisys/visorinput/Makefile
 delete mode 100644 drivers/staging/unisys/visorinput/visorinput.c
 delete mode 100644 drivers/staging/unisys/visornic/Kconfig
 delete mode 100644 drivers/staging/unisys/visornic/Makefile
 delete mode 100644 drivers/staging/unisys/visornic/visornic_main.c
MAINTAINERS +0 -8
index 3ed62dcd144e..a62da6d0f943 100644
@@ -20183,14 +20183,6 @@ F:	drivers/cdrom/cdrom.c
 F:	include/linux/cdrom.h
 F:	include/uapi/linux/cdrom.h
 
-UNISYS S-PAR DRIVERS
-M:	David Kershner <[email protected]>
-L:	[email protected] (Unisys internal)
-S:	Supported
-F:	drivers/staging/unisys/
-F:	drivers/visorbus/
-F:	include/linux/visorbus.h
-
 UNIVERSAL FLASH STORAGE HOST CONTROLLER DRIVER
 R:	Alim Akhtar <[email protected]>
 R:	Avri Altman <[email protected]>
drivers/staging/Kconfig +0 -2
index fc274737053d..a4d9f39dde90 100644
@@ -64,8 +64,6 @@ source "drivers/staging/gdm724x/Kconfig"
 
 source "drivers/staging/fwserial/Kconfig"
 
-source "drivers/staging/unisys/Kconfig"
-
 source "drivers/staging/clocking-wizard/Kconfig"
 
 source "drivers/staging/fbtft/Kconfig"
drivers/staging/Makefile +0 -1
index 65e317922e3f..a17a2aeaceba 100644
@@ -22,7 +22,6 @@ obj-$(CONFIG_MFD_NVEC)		+= nvec/
 obj-$(CONFIG_STAGING_BOARD)	+= board/
 obj-$(CONFIG_LTE_GDM724X)	+= gdm724x/
 obj-$(CONFIG_FIREWIRE_SERIAL)	+= fwserial/
-obj-$(CONFIG_UNISYSSPAR)	+= unisys/
 obj-$(CONFIG_COMMON_CLK_XLNX_CLKWZRD)	+= clocking-wizard/
 obj-$(CONFIG_FB_TFT)		+= fbtft/
 obj-$(CONFIG_MOST)		+= most/
drivers/staging/unisys/Documentation/ABI/sysfs-platform-visorchipset deleted +0 -89

89 lines not on this page · raw message

drivers/staging/unisys/Documentation/overview.txt deleted +0 -337

337 lines not on this page · raw message

drivers/staging/unisys/Kconfig deleted +0 -16
deleted file mode 100644
index 43fe1ce538e1..000000000000
@@ -1,16 +0,0 @@
-# SPDX-License-Identifier: GPL-2.0
-#
-# Unisys SPAR driver configuration
-#
-menuconfig UNISYSSPAR
-	bool "Unisys SPAR driver support"
-	help
-	  Support for the Unisys SPAR drivers
-
-if UNISYSSPAR
-
-source "drivers/staging/unisys/visornic/Kconfig"
-source "drivers/staging/unisys/visorinput/Kconfig"
-source "drivers/staging/unisys/visorhba/Kconfig"
-
-endif # UNISYSSPAR
drivers/staging/unisys/MAINTAINERS deleted +0 -5
deleted file mode 100644
index aaddc619c329..000000000000
@@ -1,5 +0,0 @@
-Unisys s-Par drivers
-M:	David Kershner <[email protected]>
-S:	Maintained
-F:	drivers/staging/unisys/Documentation/overview.txt
-F:	drivers/staging/unisys/
drivers/staging/unisys/Makefile deleted +0 -7
deleted file mode 100644
index c0f76cc196a6..000000000000
@@ -1,7 +0,0 @@
-# SPDX-License-Identifier: GPL-2.0
-#
-# Makefile for Unisys SPAR drivers
-#
-obj-$(CONFIG_UNISYS_VISORNIC)		+= visornic/
-obj-$(CONFIG_UNISYS_VISORINPUT)		+= visorinput/
-obj-$(CONFIG_UNISYS_VISORHBA)		+= visorhba/
drivers/staging/unisys/TODO deleted +0 -16
deleted file mode 100644
index d863f266bf76..000000000000
@@ -1,16 +0,0 @@
-TODO:
-	- enhance visornic to use channel_interrupt() hook instead of a
-	  kernel thread
-	- enhance visorhba to use channel_interrupt() hook instead of a
-	  kernel thread
-	- teach visorbus to handle virtual interrupts triggered by s-Par
-	  back-end, and call function driver's channel_interrupt() function
-	  when they occur
-	- enhance debugfs interfaces (e.g., per device, etc.)
-	- upgrade/remove deprecated workqueue operations
-	- move individual drivers into proper driver subsystems
-
-Patches to:
-	Greg Kroah-Hartman <[email protected]>
-	Ken Cox <[email protected]>
-	Unisys s-Par maintainer mailing list <[email protected]>
drivers/staging/unisys/include/iochannel.h deleted +0 -571

571 lines not on this page · raw message

drivers/staging/unisys/visorhba/Kconfig deleted +0 -15
deleted file mode 100644
index ed59ac11c322..000000000000
@@ -1,15 +0,0 @@
-# SPDX-License-Identifier: GPL-2.0
-#
-# Unisys visorhba configuration
-#
-
-config UNISYS_VISORHBA
-	tristate "Unisys visorhba driver"
-	depends on UNISYSSPAR && UNISYS_VISORBUS && SCSI
-	help
-		The Unisys visorhba driver provides support for s-Par HBA
-		devices exposed on the s-Par visorbus. When a message is sent
-		to visorbus to create a HBA device, the probe function of
-		visorhba is called to create the scsi device.
-		If you say Y here, you will enable the Unisys visorhba driver.
-
drivers/staging/unisys/visorhba/Makefile deleted +0 -10
deleted file mode 100644
index b613a7dcdae9..000000000000
@@ -1,10 +0,0 @@
-# SPDX-License-Identifier: GPL-2.0
-#
-# Makefile for Unisys channel
-#
-
-obj-$(CONFIG_UNISYS_VISORHBA)	+= visorhba.o
-
-visorhba-y := visorhba_main.o
-
-ccflags-y += -I $(srctree)/$(src)/../include
drivers/staging/unisys/visorhba/visorhba_main.c deleted +0 -1142

1,142 lines not on this page · raw message

drivers/staging/unisys/visorinput/Kconfig deleted +0 -16
deleted file mode 100644
index 5f036393aee9..000000000000
@@ -1,16 +0,0 @@
-# SPDX-License-Identifier: GPL-2.0
-#
-# Unisys visorinput configuration
-#
-
-config UNISYS_VISORINPUT
-	tristate "Unisys visorinput driver"
-	depends on UNISYSSPAR && UNISYS_VISORBUS && INPUT
-	help
-		The Unisys s-Par visorinput driver provides a virtualized system
-		console (keyboard and mouse) that is accessible through the
-		s-Par firmware's user interface. s-Par provides video using the EFI
-		GOP protocol, so If this driver is not present, the Linux guest should
-		still boot with visible output in the partition desktop, but keyboard
-		and mouse interaction will not be available.
-
drivers/staging/unisys/visorinput/Makefile deleted +0 -7
deleted file mode 100644
index 68ced7c8a65f..000000000000
@@ -1,7 +0,0 @@
-# SPDX-License-Identifier: GPL-2.0
-#
-# Makefile for Unisys visorinput
-#
-
-obj-$(CONFIG_UNISYS_VISORINPUT)	+= visorinput.o
-
drivers/staging/unisys/visorinput/visorinput.c deleted +0 -788

740 lines not on this page · raw message

drivers/staging/unisys/visornic/Kconfig deleted +0 -16
deleted file mode 100644
index 3f8f5570821b..000000000000

Lines of this file are not shown. View the raw message.

drivers/staging/unisys/visornic/Makefile deleted +0 -10
deleted file mode 100644
index f2984880c340..000000000000

Lines of this file are not shown. View the raw message.

drivers/staging/unisys/visornic/visornic_main.c deleted +0 -2131

2,131 lines not on this page · raw message

The rest of this diff is not shown. View the raw message.

Signature · 1 line
2.34.1

Part of the diff is not shown here. View the raw message.

#1 lore raw
Quoted 9 lines · Fabio M. De Francesco

The Unisys sub-tree contains three drivers for the "Unisys Secure Partition" (s-Par(R)): visorhba, visorinput, visornic.

They have no maintainers, in fact the only one that is listed in MAINTAINERS has an unreacheable email address. During 2021 and 2022 several patches have been submitted to these drivers but nobody at Unisys cared of reviewing the changes. Probably, also the "sparmaintainer" internal list of unisys.com is not anymore read by interested Unisys' engineers.

Quoted 7 lines

Therefore, remove the ./unisys subdirectory of staging and delete the related entries in the MAINTAINERS, Kconfig, Makefile files.

---
 MAINTAINERS                                   |    8 -

You forgot to at least cc: the people/list on the MAINTAINERS entry that you are removing here, to give them a hint that this is happening in case they want to speak up here (and to give us the ability to point to that years later when they complain they were never notified...)

Also, if you are in the "delete code" mood, I think drivers/staging/vme/ and drivers/vme/ can probably also be deleted given that the maintainer for that has moved on to other jobs. Ask them and see!

thanks,

greg k-h

#2 lore raw
Quoted 2 lines · On mercoled? 13 aprile 2022 08:52:47 CEST Greg Kroah-Hartman wrote:
Quoted 1 line · Fabio M. De Francesco

The Unisys sub-tree contains three drivers for the "Unisys Secure

Partition"

Quoted 3 lines
Quoted 3 lines

(s-Par(R)): visorhba, visorinput, visornic.

They have no maintainers, in fact the only one that is listed in

MAINTAINERS

Quoted 1 line
Quoted 1 line

has an unreacheable email address. During 2021 and 2022 several patches

have

Quoted 1 line
Quoted 1 line

been submitted to these drivers but nobody at Unisys cared of reviewing

the

Quoted 1 line
Quoted 1 line

changes. Probably, also the "sparmaintainer" internal list of

unisys.com is

Quoted 3 lines
Quoted 3 lines

not anymore read by interested Unisys' engineers.

Therefore, remove the ./unisys subdirectory of staging and delete the

related

Quoted 11 lines
Quoted 6 lines

entries in the MAINTAINERS, Kconfig, Makefile files.

---
 MAINTAINERS                                   |    8 -

You forgot to at least cc: the people/list on the MAINTAINERS entry that you are removing here, to give them a hint that this is happening in case they want to speak up here (and to give us the ability to point to that years later when they complain they were never notified...)

Yes, this is a good idea. I'll submit a v2 and add two "Cc:" lines, one to David Kershner and the other to the "sparmaintainer" list at unisys.com.

Quoted 3 lines

Also, if you are in the "delete code" mood, I think drivers/staging/vme/ and drivers/vme/ can probably also be deleted given that the maintainer for that has moved on to other jobs. Ask them and see!

I can and will do exactly as you just suggested, but only after April 22nd (unless others want to do these tasks sooner, and in that case they are welcome :)).

Thanks,

Fabio M. De Francesco

#3 lore raw
Quoted 25 lines · Fabio M. De Francesco
Quoted 2 lines · On mercoled? 13 aprile 2022 08:52:47 CEST Greg Kroah-Hartman wrote:
Quoted 1 line · Fabio M. De Francesco

The Unisys sub-tree contains three drivers for the "Unisys Secure

Partition"

Quoted 3 lines
Quoted 3 lines

(s-Par(R)): visorhba, visorinput, visornic.

They have no maintainers, in fact the only one that is listed in

MAINTAINERS

Quoted 1 line
Quoted 1 line

has an unreacheable email address. During 2021 and 2022 several patches

have

Quoted 1 line
Quoted 1 line

been submitted to these drivers but nobody at Unisys cared of reviewing

the

Quoted 1 line
Quoted 1 line

changes. Probably, also the "sparmaintainer" internal list of

unisys.com is

Quoted 3 lines
Quoted 3 lines

not anymore read by interested Unisys' engineers.

Therefore, remove the ./unisys subdirectory of staging and delete the

related

Quoted 7 lines
Quoted 6 lines

entries in the MAINTAINERS, Kconfig, Makefile files.

---
 MAINTAINERS                                   |    8 -
Quoted 7 lines
Quoted 4 lines

You forgot to at least cc: the people/list on the MAINTAINERS entry that you are removing here, to give them a hint that this is happening in case they want to speak up here (and to give us the ability to point to that years later when they complain they were never notified...)

Yes, this is a good idea. I'll submit a v2 and add two "Cc:" lines, one to David Kershner and the other to the "sparmaintainer" list at unisys.com.

There is another contact in the TODO file (last updated 2015 though ;)) Ken Cox <[email protected]>

Quoted 15 lines
Quoted 4 lines

Also, if you are in the "delete code" mood, I think drivers/staging/vme/ and drivers/vme/ can probably also be deleted given that the maintainer for that has moved on to other jobs. Ask them and see!

I can and will do exactly as you just suggested, but only after April 22nd (unless others want to do these tasks sooner, and in that case they are welcome :)).

Thanks,

Fabio M. De Francesco

#4 lore raw
Quoted 3 lines · On mercoled? 13 aprile 2022 17:38:24 CEST Alison Schofield wrote:
Quoted 2 lines · Fabio M. De Francesco
Quoted 1 line · On mercoled? 13 aprile 2022 08:52:47 CEST Greg Kroah-Hartman wrote:

On Tue, Apr 12, 2022 at 11:59:01PM +0200, Fabio M. De Francesco

Quoted 7 lines · wrote:
Quoted 7 lines
Quoted 1 line
Quoted 1 line

The Unisys sub-tree contains three drivers for the "Unisys Secure

Partition"

Quoted 3 lines
Quoted 3 lines

(s-Par(R)): visorhba, visorinput, visornic.

They have no maintainers, in fact the only one that is listed in

MAINTAINERS

Quoted 1 line
Quoted 1 line

has an unreacheable email address. During 2021 and 2022 several

patches

Quoted 2 lines
Quoted 2 lines

have

Quoted 1 line
Quoted 1 line

been submitted to these drivers but nobody at Unisys cared of

reviewing

Quoted 6 lines
Quoted 6 lines

the

Quoted 1 line
Quoted 1 line

changes. Probably, also the "sparmaintainer" internal list of

unisys.com is

Quoted 3 lines
Quoted 3 lines

not anymore read by interested Unisys' engineers.

Therefore, remove the ./unisys subdirectory of staging and delete

the

Quoted 9 lines
Quoted 9 lines

related

Quoted 8 lines
Quoted 6 lines

entries in the MAINTAINERS, Kconfig, Makefile files.

---
 MAINTAINERS                                   |    8 -

You forgot to at least cc: the people/list on the MAINTAINERS entry

that

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

you are removing here, to give them a hint that this is happening in case they want to speak up here (and to give us the ability to point

to

Quoted 3 lines
Quoted 3 lines
Quoted 1 line

that years later when they complain they were never notified...)

Yes, this is a good idea. I'll submit a v2 and add two "Cc:" lines, one

to

Quoted 1 line
Quoted 1 line

David Kershner and the other to the "sparmaintainer" list at

unisys.com.

Quoted 3 lines

There is another contact in the TODO file (last updated 2015 though ;)) Ken Cox <[email protected]>

Hi Alison, Greg,

Thank you very much for noticing that other contact :)

In the last 12 months I have sent several patches for Unisys s-Par drivers but I never noticed that other contact simply because I only ever use scripts / get_maintainer.pl to find out who and to which lists to send my works.

@Greg:

Do you think that we should care of a contact that is no more active since 2015 and resubmit a v3 with one more "Cc:" line? I have no problems to resubmit, I just want to be sure that this is the right thing to do.

Thanks,

Fabio M. De Francesco

#5 lore raw
Quoted 55 lines · Fabio M. De Francesco
Quoted 3 lines · On mercoled? 13 aprile 2022 17:38:24 CEST Alison Schofield wrote:
Quoted 2 lines · Fabio M. De Francesco
Quoted 1 line · On mercoled? 13 aprile 2022 08:52:47 CEST Greg Kroah-Hartman wrote:

On Tue, Apr 12, 2022 at 11:59:01PM +0200, Fabio M. De Francesco

Quoted 7 lines · wrote:
Quoted 7 lines
Quoted 1 line
Quoted 1 line

The Unisys sub-tree contains three drivers for the "Unisys Secure

Partition"

Quoted 3 lines
Quoted 3 lines

(s-Par(R)): visorhba, visorinput, visornic.

They have no maintainers, in fact the only one that is listed in

MAINTAINERS

Quoted 1 line
Quoted 1 line

has an unreacheable email address. During 2021 and 2022 several

patches

Quoted 2 lines
Quoted 2 lines

have

Quoted 1 line
Quoted 1 line

been submitted to these drivers but nobody at Unisys cared of

reviewing

Quoted 6 lines
Quoted 6 lines

the

Quoted 1 line
Quoted 1 line

changes. Probably, also the "sparmaintainer" internal list of

unisys.com is

Quoted 3 lines
Quoted 3 lines

not anymore read by interested Unisys' engineers.

Therefore, remove the ./unisys subdirectory of staging and delete

the

Quoted 9 lines
Quoted 9 lines

related

Quoted 8 lines
Quoted 6 lines

entries in the MAINTAINERS, Kconfig, Makefile files.

---
 MAINTAINERS                                   |    8 -

You forgot to at least cc: the people/list on the MAINTAINERS entry

that

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

you are removing here, to give them a hint that this is happening in case they want to speak up here (and to give us the ability to point

to

Quoted 3 lines
Quoted 3 lines
Quoted 1 line

that years later when they complain they were never notified...)

Yes, this is a good idea. I'll submit a v2 and add two "Cc:" lines, one

to

Quoted 1 line
Quoted 1 line

David Kershner and the other to the "sparmaintainer" list at

unisys.com.

Quoted 3 lines

There is another contact in the TODO file (last updated 2015 though ;)) Ken Cox <[email protected]>

Hi Alison, Greg,

Thank you very much for noticing that other contact :)

In the last 12 months I have sent several patches for Unisys s-Par drivers but I never noticed that other contact simply because I only ever use scripts / get_maintainer.pl to find out who and to which lists to send my works.

Quoted 5 lines

@Greg:

Do you think that we should care of a contact that is no more active since 2015 and resubmit a v3 with one more "Cc:" line? I have no problems to resubmit, I just want to be sure that this is the right thing to do.

I didn't see a v2, so confused about a v3. You could simply do a group reply and add the contact, that'll put a trail in lore. Not my call. Guessing Greg has a protocol for such removals.

Quoted 7 lines

Thanks,

Fabio M. De Francesco

#6 lore raw
Quoted 3 lines · On mercoled? 13 aprile 2022 21:31:52 CEST Alison Schofield wrote:
Quoted 2 lines · Fabio M. De Francesco
Quoted 1 line · On mercoled? 13 aprile 2022 17:38:24 CEST Alison Schofield wrote:

On Wed, Apr 13, 2022 at 09:35:53AM +0200, Fabio M. De Francesco

Quoted 4 lines · wrote:
Quoted 4 lines
Quoted 2 lines
Quoted 2 lines · On mercoled? 13 aprile 2022 08:52:47 CEST Greg Kroah-Hartman wrote:
Quoted 1 line

On Tue, Apr 12, 2022 at 11:59:01PM +0200, Fabio M. De Francesco

Quoted 1 line · wrote:
Quoted 1 line
Quoted 1 line
Quoted 1 line

The Unisys sub-tree contains three drivers for the "Unisys

Secure

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

Partition"

Quoted 3 lines
Quoted 3 lines

(s-Par(R)): visorhba, visorinput, visornic.

They have no maintainers, in fact the only one that is listed

in

Quoted 4 lines
Quoted 4 lines
Quoted 2 lines
Quoted 2 lines

MAINTAINERS

Quoted 1 line
Quoted 1 line

has an unreacheable email address. During 2021 and 2022 several

patches

Quoted 1 line
Quoted 1 line

have

Quoted 8 lines
Quoted 8 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

been submitted to these drivers but nobody at Unisys cared of

reviewing

Quoted 6 lines
Quoted 6 lines

the

Quoted 1 line
Quoted 1 line

changes. Probably, also the "sparmaintainer" internal list of

unisys.com is

Quoted 3 lines
Quoted 3 lines

not anymore read by interested Unisys' engineers.

Therefore, remove the ./unisys subdirectory of staging and

delete

Quoted 10 lines
Quoted 10 lines

the

Quoted 9 lines
Quoted 9 lines

related

Quoted 8 lines
Quoted 6 lines

entries in the MAINTAINERS, Kconfig, Makefile files.

---
 MAINTAINERS                                   |    8 -

You forgot to at least cc: the people/list on the MAINTAINERS

entry

Quoted 2 lines
Quoted 2 lines

that

Quoted 1 line
Quoted 1 line
Quoted 1 line

you are removing here, to give them a hint that this is happening

in

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

case they want to speak up here (and to give us the ability to

point

Quoted 4 lines
Quoted 4 lines

to

Quoted 3 lines
Quoted 3 lines
Quoted 1 line

that years later when they complain they were never notified...)

Yes, this is a good idea. I'll submit a v2 and add two "Cc:" lines,

one

Quoted 5 lines
Quoted 5 lines

to

Quoted 1 line
Quoted 1 line

David Kershner and the other to the "sparmaintainer" list at

unisys.com.

Quoted 2 lines

There is another contact in the TODO file (last updated 2015 though

;))

Quoted 7 lines
Quoted 7 lines
Quoted 1 line

Ken Cox <[email protected]>

Hi Alison, Greg,

Thank you very much for noticing that other contact :)

In the last 12 months I have sent several patches for Unisys s-Par

drivers

Quoted 2 lines
Quoted 2 lines

but I never noticed that other contact simply because I only ever use scripts / get_maintainer.pl to find out who and to which lists to send

my

Quoted 5 lines
Quoted 5 lines

works.

@Greg:

Do you think that we should care of a contact that is no more active

since

Quoted 6 lines
Quoted 2 lines

2015 and resubmit a v3 with one more "Cc:" line? I have no problems to resubmit, I just want to be sure that this is the right thing to do.

I didn't see a v2, so confused about a v3. You could simply do a group reply and add the contact, that'll put a trail in lore. Not my call. Guessing Greg has a protocol for such removals.

Hi Alison,

The patch v2 is at https://lore.kernel.org/outreachy/
[email protected]/T/#u

Greg required me to send that v2 because I forgot to Cc the David Kershner and the Unisys internal list.

I don't yet know if Greg's protocol for such removals requires to Cc random people taken from a TODO file, people who didn't even care to add themselves to MAINTAINERS, but I'm pretty sure that, if it is so, the only option is to send a v3.

In order to make things as Greg requires, I'd better wait for him to respond to my previous email.

Again, thanks,

Fabio