All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
	jyescas@google.com, Ming Lei <ming.lei@redhat.com>,
	Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH v5 3/9] block: Support configuring limits below the page size
Date: Tue, 30 May 2023 22:40:30 -0700	[thread overview]
Message-ID: <ZHbdzvz3HElrrOL6@bombadil.infradead.org> (raw)
In-Reply-To: <8cc92543-8d3b-6ec5-86a0-349c55a46e37@acm.org>

On Sun, May 28, 2023 at 03:32:45PM -0700, Bart Van Assche wrote:
> On 5/28/23 13:33, Luis Chamberlain wrote:
> > That's right, so the question is, is there a way to make simpler
> > modifications which might be sensible for this situation for stable
> > first, and then enhancements which don't go to stable on top ?
> > 
> > What would the minimum fix look like for stable?
> 
> Let's follow the usual process: work integrating these changes in the
> upstream kernel first and deal with backporting these changes to stable
> kernels after agreement has been achieved about what the upstream
> patches should look like.

I'm not talking about deviating away from that process.

Sometimes backporting a large chunk of changes cannot be done due the
size or other things. So one way to address this proactively is
to see if perhaps some compromises can be made for stable, while
upstream carries the rest.

I can't see a way to do this though...

So at least as-is, for the rest of the patches in this series:

Reviewed-by: Luis Chamberlain <mcgrof@kernel.org>

  Luis

  reply	other threads:[~2023-05-31  5:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-22 22:25 [PATCH v5 0/9] Support limits below the page size Bart Van Assche
2023-05-22 22:25 ` [PATCH v5 1/9] block: Use pr_info() instead of printk(KERN_INFO ...) Bart Van Assche
2023-05-22 23:10   ` Luis Chamberlain
2023-05-27 16:09     ` Bart Van Assche
2023-05-22 22:25 ` [PATCH v5 2/9] block: Prepare for supporting sub-page limits Bart Van Assche
2023-05-22 23:26   ` Luis Chamberlain
2023-05-22 22:25 ` [PATCH v5 3/9] block: Support configuring limits below the page size Bart Van Assche
2023-05-27  3:16   ` Luis Chamberlain
2023-05-27 16:20     ` Bart Van Assche
2023-05-28 20:33       ` Luis Chamberlain
2023-05-28 22:32         ` Bart Van Assche
2023-05-31  5:40           ` Luis Chamberlain [this message]
2023-05-22 22:25 ` [PATCH v5 4/9] block: Make sub_page_limit_queues available in debugfs Bart Van Assche
2023-05-27  3:17   ` Luis Chamberlain
2023-05-22 22:25 ` [PATCH v5 5/9] block: Support submitting passthrough requests with small segments Bart Van Assche
2023-05-22 22:25 ` [PATCH v5 6/9] block: Add support for filesystem requests and " Bart Van Assche
2023-05-22 22:25 ` [PATCH v5 7/9] block: Add support for small segments in blk_rq_map_user_iov() Bart Van Assche
2023-05-22 22:25 ` [PATCH v5 8/9] scsi_debug: Support configuring the maximum segment size Bart Van Assche
2023-05-24 20:50   ` Douglas Gilbert
2023-05-22 22:25 ` [PATCH v5 9/9] null_blk: " Bart Van Assche
2023-06-09 17:14 ` [PATCH v5 0/9] Support limits below the page size Sandeep Dhavale
2023-06-12 18:15   ` Bart Van Assche
2023-06-12 18:34     ` Sandeep Dhavale

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=ZHbdzvz3HElrrOL6@bombadil.infradead.org \
    --to=mcgrof@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=hch@lst.de \
    --cc=jyescas@google.com \
    --cc=kbusch@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=ming.lei@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.