linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Jens Axboe <axboe@kernel.dk>, Ming Lei <ming.lei@redhat.com>,
	Greg KH <gregkh@linuxfoundation.org>
Cc: linux-block@vger.kernel.org, Guangwu Zhang <guazhang@redhat.com>,
	Christoph Hellwig <hch@lst.de>,
	Jianchao Wang <jianchao.w.wang@oracle.com>
Subject: Re: [PATCH] block: fix single range discard merge
Date: Fri, 30 Nov 2018 09:30:56 -0800	[thread overview]
Message-ID: <1543599056.4347.11.camel@acm.org> (raw)
In-Reply-To: <9ebec24a-103c-2ea8-49e1-2f927eb8a4f8@kernel.dk>

On Fri, 2018-11-30 at 10:20 -0700, Jens Axboe wrote:
> On 11/30/18 10:18 AM, Bart Van Assche wrote:
> > On Sat, 2018-12-01 at 00:38 +0800, Ming Lei wrote:
> > > Fixes: 445251d0f4d329a ("blk-mq: fix discard merge with scheduler attached")
> > 
> > Since this patch fixes a bug introduced in kernel v4.16, does it need
> > a "Cc: stable" tag?
> 
> Like the other one, isn't stable implied with Fixes in there? You'd want
> a stable backport for any kernel that has that patchset. I think that's
> a stronger hint than stable cc.

(+Greg KH)

Hi Greg,

Would it be possible to clarify what your preferences are for adding a
"Cc: stable" tag?

Thanks,

Bart.

  reply	other threads:[~2018-11-30 17:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-30 16:38 [PATCH] block: fix single range discard merge Ming Lei
2018-11-30 17:10 ` Jens Axboe
2018-11-30 17:18 ` Bart Van Assche
2018-11-30 17:20   ` Jens Axboe
2018-11-30 17:30     ` Bart Van Assche [this message]
2018-12-02  7:32       ` Greg KH
2018-11-30 17:28 ` Christoph Hellwig

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=1543599056.4347.11.camel@acm.org \
    --to=bvanassche@acm.org \
    --cc=axboe@kernel.dk \
    --cc=gregkh@linuxfoundation.org \
    --cc=guazhang@redhat.com \
    --cc=hch@lst.de \
    --cc=jianchao.w.wang@oracle.com \
    --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 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).