From: Jens Axboe <axboe@kernel.dk>
To: Bart Van Assche <bvanassche@acm.org>, Ming Lei <ming.lei@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>,
linux-block@vger.kernel.org, Yi Zhang <yi.zhang@redhat.com>
Subject: Re: [PATCH] blk-mq: don't create hctx debugfs dir until q->debugfs_dir is created
Date: Tue, 12 Jul 2022 14:00:06 -0600 [thread overview]
Message-ID: <f88ba06b-4d4b-ffc4-362f-e00198ecc242@kernel.dk> (raw)
In-Reply-To: <3240717a-bec8-0681-1c78-c2b06a2346f3@acm.org>
On 7/12/22 1:52 PM, Bart Van Assche wrote:
> On 7/11/22 18:50, Ming Lei wrote:
>> On Mon, Jul 11, 2022 at 10:20:39AM -0700, Bart Van Assche wrote:
>>> Does this patch need a Fixes: tag?
>>
>> Yeah,
>>
>> Fixes: 6cfc0081b046 ("blk-mq: no need to check return value of debugfs_create functions")
>>
>>>
>>> Additionally, as one can see here, I reported this bug before Yi:
>>> https://bugzilla.kernel.org/show_bug.cgi?id=216191
>>
>> Sorry for missing your report, and I am fine to add your reported-by.
>
> Hi Ming,
>
> Since this patch is already in Jens' tree I will let Jens decide how
> to proceed.
It was top of that branch, I did amend it this morning with the Fixes
tag. I missed the reported-by, however... Sorry.
--
Jens Axboe
prev parent reply other threads:[~2022-07-12 20:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 9:08 [PATCH] blk-mq: don't create hctx debugfs dir until q->debugfs_dir is created Ming Lei
2022-07-11 10:10 ` Christoph Hellwig
2022-07-11 10:44 ` Yi Zhang
2022-07-11 13:57 ` Jens Axboe
2022-07-11 17:20 ` Bart Van Assche
2022-07-12 1:50 ` Ming Lei
2022-07-12 19:52 ` Bart Van Assche
2022-07-12 20:00 ` Jens Axboe [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=f88ba06b-4d4b-ffc4-362f-e00198ecc242@kernel.dk \
--to=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=yi.zhang@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).