From: Christoph Hellwig <hch@lst.de>
To: taochiu <taochiu@synology.com>
Cc: hch@lst.de, chaitanya.kulkarni@wdc.com, kbusch@kernel.org,
axboe@fb.com, sagi@grimberg.me, james.smart@broadcom.com,
linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
Cody Wong <codywong@synology.com>,
Leon Chien <leonchien@synology.com>
Subject: Re: [PATCH v2 1/2] nvme-core: Move nvmf queue ready check routines to core
Date: Wed, 28 Apr 2021 08:44:58 +0200 [thread overview]
Message-ID: <20210428064458.GB5988@lst.de> (raw)
In-Reply-To: <20210426025310.3005573-1-taochiu@synology.com>
Thanks,
applied the series to nvme-5.13.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: taochiu <taochiu@synology.com>
Cc: hch@lst.de, chaitanya.kulkarni@wdc.com, kbusch@kernel.org,
axboe@fb.com, sagi@grimberg.me, james.smart@broadcom.com,
linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
Cody Wong <codywong@synology.com>,
Leon Chien <leonchien@synology.com>
Subject: Re: [PATCH v2 1/2] nvme-core: Move nvmf queue ready check routines to core
Date: Wed, 28 Apr 2021 08:44:58 +0200 [thread overview]
Message-ID: <20210428064458.GB5988@lst.de> (raw)
In-Reply-To: <20210426025310.3005573-1-taochiu@synology.com>
Thanks,
applied the series to nvme-5.13.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-04-28 6:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 2:53 [PATCH v2 1/2] nvme-core: Move nvmf queue ready check routines to core taochiu
2021-04-26 2:53 ` taochiu
2021-04-26 15:16 ` Keith Busch
2021-04-26 15:16 ` Keith Busch
2021-04-28 6:44 ` Christoph Hellwig [this message]
2021-04-28 6:44 ` 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=20210428064458.GB5988@lst.de \
--to=hch@lst.de \
--cc=axboe@fb.com \
--cc=chaitanya.kulkarni@wdc.com \
--cc=codywong@synology.com \
--cc=james.smart@broadcom.com \
--cc=kbusch@kernel.org \
--cc=leonchien@synology.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=taochiu@synology.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.