linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: Christoph Hellwig <hch@lst.de>,
	linux-scsi@vger.kernel.org, schmitzmic@gmail.com,
	linux@rainbow-software.org
Subject: Re: [PATCH 5/7] pas16: remove from tree
Date: Tue, 20 Sep 2016 18:09:10 +0200	[thread overview]
Message-ID: <20160920160910.GA28528@lst.de> (raw)
In-Reply-To: <alpine.LNX.2.00.1609200955490.3516@nippy.intranet>

On Tue, Sep 20, 2016 at 10:12:28AM +1000, Finn Thain wrote:
> On that basis, I would remove these drivers along with scsi_register() 
> itself. Is there some reason to remove them earlier? It messes up my patch 
> queue.

Mostly to make the later patches less painless by moving the easy removals
out of the way first.  This also means we have time ahead to resurrect
them properly for the unlikely case that someone cares.

That beeing said I certainly don't want to mess up your patch queue
with this.  How about you pick up the pas16, t128 and dtc patches and
add them to the end of your queue?

  reply	other threads:[~2016-09-20 16:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-19 15:50 remove old and unmaintained ISA driver Christoph Hellwig
2016-09-19 15:50 ` [PATCH 1/7] wd7000: remove from tree Christoph Hellwig
2016-09-19 15:50 ` [PATCH 2/7] in2000: " Christoph Hellwig
2016-09-19 15:50 ` [PATCH 3/7] ultrastor: " Christoph Hellwig
2016-09-19 15:50 ` [PATCH 4/7] u14-34f: " Christoph Hellwig
2016-09-19 15:50 ` [PATCH 5/7] pas16: " Christoph Hellwig
2016-09-20  0:12   ` Finn Thain
2016-09-20 16:09     ` Christoph Hellwig [this message]
2016-09-19 15:50 ` [PATCH 6/7] t128: " Christoph Hellwig
2016-09-19 15:50 ` [PATCH 7/7] dtc: " Christoph Hellwig
2016-09-20  9:53 ` remove old and unmaintained ISA driver Hannes Reinecke
2016-09-27  0:52 ` Martin K. Petersen

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=20160920160910.GA28528@lst.de \
    --to=hch@lst.de \
    --cc=fthain@telegraphics.com.au \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux@rainbow-software.org \
    --cc=schmitzmic@gmail.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;
as well as URLs for NNTP newsgroup(s).