public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Alison Schofield <alison.schofield@intel.com>
To: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"linux-staging@lists.linux.dev" <linux-staging@lists.linux.dev>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"outreachy@lists.linux.dev" <outreachy@lists.linux.dev>
Subject: Re: [PATCH] staging: Remove the drivers for the Unisys s-Par
Date: Wed, 13 Apr 2022 12:31:52 -0700	[thread overview]
Message-ID: <20220413193152.GA1242449@alison-desk> (raw)
In-Reply-To: <7390243.EvYhyI6sBW@leap>

On Wed, Apr 13, 2022 at 11:57:20AM -0700, Fabio M. De Francesco wrote:
> 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 wrote:
> > > 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 
> wrote:
> > > > > 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.
> > > > > 
> > > > > Suggested-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > > > Signed-off-by: Fabio M. De Francesco <fmdefrancesco@gmail.com>
> > > > > ---
> > > > >  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.
> > 
> > There is another contact in the TODO file (last updated 2015 though ;))
> > Ken Cox <jkc@redhat.com>
> 
> 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.

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. 

> 
> Thanks,
> 
> Fabio M. De Francesco
>  
> 
> 

  reply	other threads:[~2022-04-13 19:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12 21:59 [PATCH] staging: Remove the drivers for the Unisys s-Par Fabio M. De Francesco
2022-04-13  6:52 ` Greg Kroah-Hartman
2022-04-13  7:35   ` Fabio M. De Francesco
2022-04-13 15:38     ` Alison Schofield
2022-04-13 18:57       ` Fabio M. De Francesco
2022-04-13 19:31         ` Alison Schofield [this message]
2022-04-13 20:25           ` Fabio M. De Francesco

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=20220413193152.GA1242449@alison-desk \
    --to=alison.schofield@intel.com \
    --cc=fmdefrancesco@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=outreachy@lists.linux.dev \
    /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