From: Christoph Hellwig <hch@lst.de> To: Dongli Zhang <dongli.zhang@oracle.com> Cc: linux-nvme@lists.infradead.org, james.smart@broadcom.com, hch@lst.de, sagi@grimberg.me, chaitanya.kulkarni@wdc.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/1] nvme-fcloop: verify wwnn and wwpn format Date: Wed, 17 Jun 2020 10:06:49 +0200 [thread overview] Message-ID: <20200617080649.GB14863@lst.de> (raw) In-Reply-To: <20200526042118.17836-1-dongli.zhang@oracle.com> Applied to nvme-5.9.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de> To: Dongli Zhang <dongli.zhang@oracle.com> Cc: sagi@grimberg.me, chaitanya.kulkarni@wdc.com, linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org, james.smart@broadcom.com, hch@lst.de Subject: Re: [PATCH 1/1] nvme-fcloop: verify wwnn and wwpn format Date: Wed, 17 Jun 2020 10:06:49 +0200 [thread overview] Message-ID: <20200617080649.GB14863@lst.de> (raw) In-Reply-To: <20200526042118.17836-1-dongli.zhang@oracle.com> Applied to nvme-5.9. _______________________________________________ linux-nvme mailing list linux-nvme@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-06-17 8:06 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-26 4:21 [PATCH 1/1] nvme-fcloop: verify wwnn and wwpn format Dongli Zhang 2020-05-26 4:21 ` Dongli Zhang 2020-06-04 6:43 ` Dongli Zhang 2020-06-04 6:43 ` Dongli Zhang 2020-06-04 6:54 ` Chaitanya Kulkarni 2020-06-04 6:54 ` Chaitanya Kulkarni 2020-06-04 14:03 ` Hannes Reinecke 2020-06-04 14:03 ` Hannes Reinecke 2020-06-04 15:20 ` James Smart 2020-06-04 15:20 ` James Smart 2020-06-10 14:53 ` Dongli Zhang 2020-06-10 14:53 ` Dongli Zhang 2020-06-04 17:27 ` Sagi Grimberg 2020-06-04 17:27 ` Sagi Grimberg 2020-06-17 8:06 ` Christoph Hellwig [this message] 2020-06-17 8:06 ` 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=20200617080649.GB14863@lst.de \ --to=hch@lst.de \ --cc=chaitanya.kulkarni@wdc.com \ --cc=dongli.zhang@oracle.com \ --cc=james.smart@broadcom.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-nvme@lists.infradead.org \ --cc=sagi@grimberg.me \ /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: linkBe 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.