From: Christoph Hellwig <hch@lst.de> To: Dan Carpenter <dan.carpenter@oracle.com> Cc: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@fb.com>, Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>, Max Gurtovoy <mgurtovoy@nvidia.com>, Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>, Roy Shterman <roys@lightbitslabs.com>, Solganik Alexander <sashas@lightbitslabs.com>, linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org Subject: Re: [PATCH] nvme-tcp: fix error codes in nvme_tcp_setup_ctrl() Date: Tue, 8 Jun 2021 18:43:28 +0200 [thread overview] Message-ID: <20210608164328.GB12661@lst.de> (raw) In-Reply-To: <YLtykIn+Or0l08oV@mwanda> Thanks, applied to nvme-5.14.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de> To: Dan Carpenter <dan.carpenter@oracle.com> Cc: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@fb.com>, Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>, Max Gurtovoy <mgurtovoy@nvidia.com>, Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>, Roy Shterman <roys@lightbitslabs.com>, Solganik Alexander <sashas@lightbitslabs.com>, linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org Subject: Re: [PATCH] nvme-tcp: fix error codes in nvme_tcp_setup_ctrl() Date: Tue, 8 Jun 2021 18:43:28 +0200 [thread overview] Message-ID: <20210608164328.GB12661@lst.de> (raw) In-Reply-To: <YLtykIn+Or0l08oV@mwanda> Thanks, applied to nvme-5.14. _______________________________________________ Linux-nvme mailing list Linux-nvme@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-06-08 16:43 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-05 12:48 [PATCH] nvme-tcp: fix error codes in nvme_tcp_setup_ctrl() Dan Carpenter 2021-06-05 12:48 ` Dan Carpenter 2021-06-05 18:38 ` Chaitanya Kulkarni 2021-06-05 18:38 ` Chaitanya Kulkarni 2021-06-08 16:43 ` Christoph Hellwig [this message] 2021-06-08 16:43 ` 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=20210608164328.GB12661@lst.de \ --to=hch@lst.de \ --cc=axboe@fb.com \ --cc=chaitanya.kulkarni@wdc.com \ --cc=dan.carpenter@oracle.com \ --cc=kbusch@kernel.org \ --cc=kernel-janitors@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-nvme@lists.infradead.org \ --cc=mgurtovoy@nvidia.com \ --cc=roys@lightbitslabs.com \ --cc=sagi@grimberg.me \ --cc=sashas@lightbitslabs.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: 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.