public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Liu Junqi <liujunqi@pku.edu.cn>,
	Bart Van Assche <bvanassche@acm.org>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	"Gustavo A. R. Silva" <gustavoars@kernel.org>,
	Jakub Kicinski <kuba@kernel.org>,
	Colin Ian King <colin.king@intel.com>,
	sparmaintainer@unisys.com, linux-staging@lists.linux.dev,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] MAINTAINERS: Remove D. Kershner from Unisys S-PAR maintainers
Date: Tue, 12 Apr 2022 18:21:39 +0200	[thread overview]
Message-ID: <1683735.QkHrqEjB74@leap> (raw)
In-Reply-To: <CAMhs-H_JJ7JVccYjdoj5opTt6R5CHRBwQ05tXPuFgenpCuyy4w@mail.gmail.com>

Hi Sergio,

On martedì 12 aprile 2022 13:30:43 CEST Sergio Paracuellos wrote:
> Hi Fabio,
> 
> Check this patchset [0] I sent a bit time ago removing two drivers from staging,
> 
> Hope this helps.
> 
> Regards,
>     Sergio Paracuellos
> 
> [0]: https://lore.kernel.org/all/20211113192045.32153-4-sergio.paracuellos@gmail.com/T/

Thank you very much for the link to your patchset :)

I have just taken a look at it. I'm pretty sure that it will be very useful
for accomplishing the task of removing the unisys sub-tree. I've planned to
do this work by the end of the current week.

Regards,

Fabio M. De Francesco



  reply	other threads:[~2022-04-12 16:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12 10:36 [PATCH v2] MAINTAINERS: Remove D. Kershner from Unisys S-PAR maintainers Fabio M. De Francesco
2022-04-12 10:41 ` Greg Kroah-Hartman
2022-04-12 11:08   ` Fabio M. De Francesco
2022-04-12 11:30     ` Sergio Paracuellos
2022-04-12 16:21       ` Fabio M. De Francesco [this message]
2022-04-12 12:02     ` Greg Kroah-Hartman

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=1683735.QkHrqEjB74@leap \
    --to=fmdefrancesco@gmail.com \
    --cc=bvanassche@acm.org \
    --cc=colin.king@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=gustavoars@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=liujunqi@pku.edu.cn \
    --cc=martin.petersen@oracle.com \
    --cc=sergio.paracuellos@gmail.com \
    --cc=sparmaintainer@unisys.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