Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Yao Sang <sangyao@kylinos.cn>
Cc: kbusch@kernel.org, axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
	linux-nvme@lists.infradead.org
Subject: Re: [PATCH v1 1/2] nvme: factor namespace-head queue-limit update
Date: Mon, 20 Jul 2026 16:42:39 +0200	[thread overview]
Message-ID: <20260720144239.GB16699@lst.de> (raw)
In-Reply-To: <20260720022205.1798805-2-sangyao@kylinos.cn>

Looks good:

Reviewed-by: Christoph Hellwig <hch@lst.de>



  reply	other threads:[~2026-07-20 14:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20  2:22 [PATCH v1 0/2] nvme: use local limits for namespace heads Yao Sang
2026-07-20  2:22 ` [PATCH v1 1/2] nvme: factor namespace-head queue-limit update Yao Sang
2026-07-20 14:42   ` Christoph Hellwig [this message]
2026-07-20  2:22 ` [PATCH v1 2/2] nvme: stop using queue_limits_stack_bdev for namespace heads Yao Sang
2026-07-20 14:46   ` 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=20260720144239.GB16699@lst.de \
    --to=hch@lst.de \
    --cc=axboe@kernel.dk \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    --cc=sangyao@kylinos.cn \
    /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