From: Bart Van Assche <bvanassche@acm.org>
To: Chengming Zhou <zhouchengming@bytedance.com>,
chengming.zhou@linux.dev, axboe@kernel.dk, ming.lei@redhat.com,
hch@lst.de
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/6] blk-mq-tag: remove bt_for_each()
Date: Sun, 3 Sep 2023 16:51:36 -0700 [thread overview]
Message-ID: <13c27994-e372-674f-d265-dc623fae26ce@acm.org> (raw)
In-Reply-To: <a84b5ccb-151a-2de1-c213-de68a6f81f29@bytedance.com>
On 9/2/23 07:58, Chengming Zhou wrote:
> Hello, gentle ping.
According to
https://lore.kernel.org/linux-kernel/CAHk-=wgmKhCrdrOCjp=5v9NO6C=PJ8ZTZcCXj09piHzsZ7qqmw@mail.gmail.com/,
the merge window opened on August 27 (one week ago). Since we are now
in the middle of the merge window and since maintainers typically do
not merge patch series during the merge window, it's probably the wrong
time to send a ping.
Thanks,
Bart.
next prev parent reply other threads:[~2023-09-03 23:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 15:17 [PATCH v3 0/6] blk-mq-tag: remove bt_for_each() chengming.zhou
2023-08-23 15:17 ` [PATCH v3 1/6] blk-mq-tag: support queue filter in bt_tags_iter() chengming.zhou
2023-08-23 15:17 ` [PATCH v3 2/6] blk-mq-tag: introduce __blk_mq_tagset_busy_iter() chengming.zhou
2023-08-23 15:18 ` [PATCH v3 3/6] blk-mq-tag: remove bt_for_each() chengming.zhou
2023-08-23 15:18 ` [PATCH v3 4/6] blk-mq: delete superfluous check in iterate callback chengming.zhou
2023-08-23 15:18 ` [PATCH v3 5/6] blk-mq-tag: fix functions documentation chengming.zhou
2023-08-23 15:18 ` [PATCH v3 6/6] blk-mq-tag: fix blk_mq_queue_tag_busy_iter() documentation chengming.zhou
2023-08-23 15:26 ` Bart Van Assche
2023-09-02 14:58 ` [PATCH v3 0/6] blk-mq-tag: remove bt_for_each() Chengming Zhou
2023-09-03 23:51 ` Bart Van Assche [this message]
2023-09-04 2:25 ` Chengming Zhou
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=13c27994-e372-674f-d265-dc623fae26ce@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=chengming.zhou@linux.dev \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=zhouchengming@bytedance.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