From: Christoph Hellwig <hch@lst.de> To: Sagi Grimberg <sagi@grimberg.me> Cc: linux-nvme@lists.infradead.org, linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>, Keith Busch <keith.busch@intel.com>, Jens Axboe <axboe@kernel.dk> Subject: Re: [PATCH v4 0/6] restore nvme-rdma polling Date: Tue, 18 Dec 2018 17:48:21 +0100 [thread overview] Message-ID: <20181218164821.GA13193@lst.de> (raw) In-Reply-To: <20181214190610.20086-1-sagi@grimberg.me> Thanks, applied to nvme-4.21.
WARNING: multiple messages have this Message-ID (diff)
From: hch@lst.de (Christoph Hellwig) Subject: [PATCH v4 0/6] restore nvme-rdma polling Date: Tue, 18 Dec 2018 17:48:21 +0100 [thread overview] Message-ID: <20181218164821.GA13193@lst.de> (raw) In-Reply-To: <20181214190610.20086-1-sagi@grimberg.me> Thanks, applied to nvme-4.21.
next prev parent reply other threads:[~2018-12-18 16:48 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-12-14 19:06 [PATCH v4 0/6] restore nvme-rdma polling Sagi Grimberg 2018-12-14 19:06 ` Sagi Grimberg 2018-12-14 19:06 ` [PATCH v4 1/6] block: clear REQ_HIPRI if polling is not supported Sagi Grimberg 2018-12-14 19:06 ` Sagi Grimberg 2018-12-14 19:06 ` [PATCH v4 2/6] block: make request_to_qc_t public Sagi Grimberg 2018-12-14 19:06 ` Sagi Grimberg 2018-12-14 19:06 ` [PATCH v4 3/6] nvme-core: optionally poll sync commands Sagi Grimberg 2018-12-14 19:06 ` Sagi Grimberg 2018-12-14 19:06 ` [PATCH v4 4/6] nvme-fabrics: allow nvmf_connect_io_queue to poll Sagi Grimberg 2018-12-14 19:06 ` Sagi Grimberg 2018-12-14 19:06 ` [PATCH v4 5/6] nvme-fabrics: allow user to pass in nr_poll_queues Sagi Grimberg 2018-12-14 19:06 ` Sagi Grimberg 2018-12-14 19:06 ` [PATCH v4 6/6] nvme-rdma: implement polling queue map Sagi Grimberg 2018-12-14 19:06 ` Sagi Grimberg 2018-12-18 16:48 ` Christoph Hellwig [this message] 2018-12-18 16:48 ` [PATCH v4 0/6] restore nvme-rdma polling 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=20181218164821.GA13193@lst.de \ --to=hch@lst.de \ --cc=axboe@kernel.dk \ --cc=keith.busch@intel.com \ --cc=linux-block@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.