linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>,
	Ming Lei <ming.lei@redhat.com>, Hannes Reinecke <hare@suse.com>,
	Paul Mackerras <paulus@ozlabs.org>,
	Juergen Gross <jgross@suse.com>,
	linux-scsi@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: remove the "clustering" flag V2
Date: Tue, 18 Dec 2018 23:28:20 -0800	[thread overview]
Message-ID: <20181219072820.GA1798@infradead.org> (raw)
In-Reply-To: <yq136qui1q3.fsf@oracle.com>

On Tue, Dec 18, 2018 at 11:23:32PM -0500, Martin K. Petersen wrote:
> 
> Christoph,
> 
> > can we get this reviewed and merge before the end of the merge window?
> > That gets the clustering put of the way for the multipage-biovec work
> > from Ming which we want to land in the block tree early in the next
> > merge window.
> 
> I have been somewhat hesitant to apply this just before the merge
> window.  However, I did go through it fairly carefully and since it's a
> mostly mechanical change, I did apply it.
> 
> There were a few things I needed to tweak by hand and patch 9 forgot to
> update myrs and myrb.

Hmm, there should have been two patches to drop these flags entirely
for those, given that the DAC960 driver didn't have any such
limitations.  Not sure why those got skipped.  But I'll send follow ons
for that.

      parent reply	other threads:[~2018-12-19  7:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-13 15:17 remove the "clustering" flag V2 Christoph Hellwig
2018-12-13 15:17 ` [PATCH 01/10] scsi: make sure all drivers set the use_clustering flag Christoph Hellwig
2018-12-13 15:17 ` [PATCH 02/10] scsi: flip the default on use_clustering Christoph Hellwig
2018-12-13 15:17 ` [PATCH 03/10] scsi: introduce a max_segment_size host_template parameters Christoph Hellwig
2018-12-13 15:17 ` [PATCH 04/10] cumana_2: remove the explicit use_clustering setting Christoph Hellwig
2018-12-13 15:17 ` [PATCH 05/10] powertec: " Christoph Hellwig
2018-12-13 15:17 ` [PATCH 06/10] xen-scsifront: remove DISABLE_CLUSTERING Christoph Hellwig
2018-12-18  8:23   ` Juergen Gross
2018-12-13 15:17 ` [PATCH 07/10] mesh: " Christoph Hellwig
2018-12-13 15:17 ` [PATCH 08/10] mac53c94: " Christoph Hellwig
2018-12-13 15:17 ` [PATCH 09/10] scsi: remove the use_clustering flag Christoph Hellwig
2018-12-13 15:17 ` [PATCH 10/10] block: remove the cluster flag Christoph Hellwig
2018-12-18  7:08 ` remove the "clustering" flag V2 Christoph Hellwig
2018-12-18  7:47   ` Hannes Reinecke
2018-12-18 16:29     ` Christoph Hellwig
2018-12-19  4:23   ` Martin K. Petersen
2018-12-19  4:31     ` Jens Axboe
2018-12-19  4:39       ` Martin K. Petersen
2018-12-19  7:28     ` Christoph Hellwig [this message]

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=20181219072820.GA1798@infradead.org \
    --to=hch@infradead.org \
    --cc=axboe@kernel.dk \
    --cc=hare@suse.com \
    --cc=hch@lst.de \
    --cc=jgross@suse.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=ming.lei@redhat.com \
    --cc=paulus@ozlabs.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).