linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@infradead.org>,
	JeffleXu <jefflexu@linux.alibaba.com>,
	joseph.qi@linux.alibaba.com, linux-block@vger.kernel.org
Subject: Re: [PATCH v2] block: fix inflight statistics of part0
Date: Wed, 2 Dec 2020 19:05:15 +0000	[thread overview]
Message-ID: <20201202190515.GA19811@infradead.org> (raw)
In-Reply-To: <699798e0-6b38-105f-aacc-938f3ecd6ce4@kernel.dk>

On Wed, Dec 02, 2020 at 09:48:03AM -0700, Jens Axboe wrote:
> On 12/2/20 4:20 AM, Christoph Hellwig wrote:
> > On Wed, Dec 02, 2020 at 07:17:55PM +0800, JeffleXu wrote:
> >>> Fixes: bf0ddaba65dd ("blk-mq: fix sysfs inflight counter")
> >>> Fixes: f299b7c7a9de ("blk-mq: provide internal in-flight variant")
> >>> Reviewed-by: Christoph Hellwig <hch@lst.de>
> >>> Signed-off-by: Jeffle Xu <jefflexu@linux.alibaba.com>
> >>> ---
> >>> v2: update the commit log, adding 'Fixes' tag
> >>
> >> Forgot to add 'stable' tag.
> > 
> > The fixes tags take care of that automatically.
> > 
> > Note that this patch will cause a merge conflict with my work in
> > linux-next, but the resolution is pretty trivial.
> 
> Might be better to handle on the stable side, and just apply this to
> 5.11. It's not a new regression.

If you apply it to for-5.11/block it won't compile.  It'll need a quick
s/partno/bd_partno/ there.

  reply	other threads:[~2020-12-02 19:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-02 11:11 [PATCH v2] block: fix inflight statistics of part0 Jeffle Xu
2020-12-02 11:17 ` JeffleXu
2020-12-02 11:20   ` Christoph Hellwig
2020-12-02 16:48     ` Jens Axboe
2020-12-02 19:05       ` Christoph Hellwig [this message]
2020-12-03  1:46         ` JeffleXu

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=20201202190515.GA19811@infradead.org \
    --to=hch@infradead.org \
    --cc=axboe@kernel.dk \
    --cc=jefflexu@linux.alibaba.com \
    --cc=joseph.qi@linux.alibaba.com \
    --cc=linux-block@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).