From: Bart Van Assche <bvanassche@acm.org>
To: "牛志国 (Zhiguo Niu)" <Zhiguo.Niu@unisoc.com>,
"Jens Axboe" <axboe@kernel.dk>
Cc: "Christoph Hellwig" <hch@lst.de>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"Damien Le Moal" <dlemoal@kernel.org>,
"王科 (Ke Wang)" <Ke.Wang@unisoc.com>
Subject: Re: 答复: [PATCH 1/2] block: Call .limit_depth() after .hctx has been set
Date: Tue, 7 May 2024 21:52:22 -0700 [thread overview]
Message-ID: <b2de558e-5d2b-4e13-b43f-f0aabf99b29e@acm.org> (raw)
In-Reply-To: <8fe8624ac50d49ef9a8aea9de92e93af@BJMBX02.spreadtrum.com>
On 5/7/24 19:28, 牛志国 (Zhiguo Niu) wrote:
> Excuse me, do you have any comments about this patch set from Bart
> Van Assche, We meet this "warning issue" about async_depth, more
> detail info is in:
> https://lore.kernel.org/all/CAHJ8P3KEOC_DXQmZK3u7PHgZFmWpMVzPa6pgkOgpyoH7wgT5nw@mail.gmail.com/
> please help consider it and it can solve the above warning issue.
Since Christoph posted a comment I think it's up to me to address his
comment. I plan to repost this patch series next week. I'm currently OoO.
Thanks,
Bart.
next prev parent reply other threads:[~2024-05-08 4:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 21:23 [PATCH 0/2] Fix the mq-deadline async_depth implementation Bart Van Assche
2024-04-03 21:23 ` [PATCH 1/2] block: Call .limit_depth() after .hctx has been set Bart Van Assche
2024-04-05 8:46 ` Christoph Hellwig
2024-04-05 20:05 ` Bart Van Assche
2024-05-08 2:28 ` 答复: " 牛志国 (Zhiguo Niu)
2024-05-08 4:52 ` Bart Van Assche [this message]
2024-04-03 21:23 ` [PATCH 2/2] block/mq-deadline: Fix the tag reservation code Bart Van Assche
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=b2de558e-5d2b-4e13-b43f-f0aabf99b29e@acm.org \
--to=bvanassche@acm.org \
--cc=Ke.Wang@unisoc.com \
--cc=Zhiguo.Niu@unisoc.com \
--cc=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=hch@lst.de \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).