linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Finn Thain <fthain@telegraphics.com.au>, Chris Boot <bootc@boo.tc>
Cc: linuxppc-dev@lists.ozlabs.org, target-devel@vger.kernel.org,
	linux-scsi@vger.kernel.org,
	linux1394-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, Chuhong Yuan <hslester96@gmail.com>,
	"Martin K . Petersen" <martin.petersen@oracle.com>,
	Nicholas Bellinger <nab@linux-iscsi.org>,
	Stefan Richter <stefanr@s5r6.in-berlin.de>
Subject: Re: [PATCH] scsi: target/sbp: remove firewire SBP target driver
Date: Tue, 16 Jun 2020 07:08:40 -0700	[thread overview]
Message-ID: <8cbab988-fba7-8e27-7faf-9f7aa36ca235@acm.org> (raw)
In-Reply-To: <alpine.LNX.2.22.394.2006161929380.8@nippy.intranet>

On 2020-06-16 02:42, Finn Thain wrote:
> Martin said, "I'd appreciate a patch to remove it"
> 
> And Bart said, "do you want to keep this driver in the kernel tree?"
> 
> AFAICT both comments are quite ambiguous. I don't see an actionable 
> request, just an expression of interest from people doing their jobs.
> 
> Note well: there is no pay check associated with having a MAINTAINERS file 
> entry.

Hi Finn,

As far as I know the sbp driver only has had one user ever and that user
is no longer user the sbp driver. So why to keep it in the kernel tree?
Restoring a kernel driver can be easy - the first step is a "git revert".

Thanks,

Bart.



  reply	other threads:[~2020-06-16 14:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-13  8:37 [PATCH] scsi: target/sbp: remove SBP target driver Chris Boot
2020-06-14  0:03 ` [PATCH] scsi: target/sbp: remove firewire " Finn Thain
2020-06-14 10:34   ` Chris Boot
2020-06-14 23:28     ` Finn Thain
2020-06-15 15:00       ` Chris Boot
2020-06-16  9:42         ` Finn Thain
2020-06-16 14:08           ` Bart Van Assche [this message]
2020-06-16 14:13             ` Johannes Thumshirn
2020-06-16 15:34               ` James Bottomley
2020-06-16 17:59                 ` Chris Boot
2020-06-17  3:09                   ` Martin K. Petersen
2020-06-18  0:40                     ` Finn Thain
2020-06-17  2:07             ` Finn Thain
2021-01-04 17:43               ` Bart Van Assche
2021-01-04 22:50                 ` Finn Thain
2021-01-05  1:48                   ` Bart Van Assche
2020-06-17  2:35   ` Martin K. Petersen
2020-06-17  4:21     ` Finn Thain

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=8cbab988-fba7-8e27-7faf-9f7aa36ca235@acm.org \
    --to=bvanassche@acm.org \
    --cc=bootc@boo.tc \
    --cc=fthain@telegraphics.com.au \
    --cc=hslester96@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=martin.petersen@oracle.com \
    --cc=nab@linux-iscsi.org \
    --cc=stefanr@s5r6.in-berlin.de \
    --cc=target-devel@vger.kernel.org \
    /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).