From: Justin Tee <justintee8345@gmail.com>
To: "Ewan D. Milne" <emilne@redhat.com>, linux-nvme@lists.infradead.org
Cc: Johannes.Thumshirn@wdc.com,
"paul.ely@broadcom.com" <paul.ely@broadcom.com>,
james.smart@broadcom.com, justin.tee@broadcom.com
Subject: Re: [PATCH] nvme: nvme-fc: Fix nvme_fc_create_hw_io_queues() queue deletion in error path
Date: Wed, 13 May 2026 14:48:03 -0700 [thread overview]
Message-ID: <33611e88-e4fb-4848-8569-c4a1f3040990@gmail.com> (raw)
In-Reply-To: <20260513192551.892309-1-emilne@redhat.com>
Reviewed-by: Justin Tee <justin.tee@broadcom.com>
Regards,
Justin
prev parent reply other threads:[~2026-05-13 21:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 19:25 [PATCH] nvme: nvme-fc: Fix nvme_fc_create_hw_io_queues() queue deletion in error path Ewan D. Milne
2026-05-13 21:48 ` Justin Tee [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=33611e88-e4fb-4848-8569-c4a1f3040990@gmail.com \
--to=justintee8345@gmail.com \
--cc=Johannes.Thumshirn@wdc.com \
--cc=emilne@redhat.com \
--cc=james.smart@broadcom.com \
--cc=justin.tee@broadcom.com \
--cc=linux-nvme@lists.infradead.org \
--cc=paul.ely@broadcom.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