From: Christoph Hellwig <hch@lst.de> To: Xianting Tian <tian.xianting@h3c.com> Cc: kbusch@kernel.org, axboe@fb.com, hch@lst.de, sagi@grimberg.me, linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] nvme: replace meaningless judgement by checking whether req is null Date: Mon, 21 Sep 2020 08:34:13 +0200 [thread overview] Message-ID: <20200921063413.GA18298@lst.de> (raw) In-Reply-To: <20200921021052.10462-1-tian.xianting@h3c.com> Thanks, this looks much more sensible than the previous versions.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de> To: Xianting Tian <tian.xianting@h3c.com> Cc: sagi@grimberg.me, linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org, axboe@fb.com, kbusch@kernel.org, hch@lst.de Subject: Re: [PATCH] nvme: replace meaningless judgement by checking whether req is null Date: Mon, 21 Sep 2020 08:34:13 +0200 [thread overview] Message-ID: <20200921063413.GA18298@lst.de> (raw) In-Reply-To: <20200921021052.10462-1-tian.xianting@h3c.com> Thanks, this looks much more sensible than the previous versions. _______________________________________________ Linux-nvme mailing list Linux-nvme@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-09-21 6:34 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-21 2:10 [PATCH] nvme: replace meaningless judgement by checking whether req is null Xianting Tian 2020-09-21 2:10 ` Xianting Tian 2020-09-21 6:34 ` Christoph Hellwig [this message] 2020-09-21 6:34 ` Christoph Hellwig 2020-09-21 15:08 ` Keith Busch 2020-09-21 15:08 ` Keith Busch 2020-09-21 15:49 ` Tianxianting 2020-09-21 15:49 ` Tianxianting 2020-09-21 15:59 ` Keith Busch 2020-09-21 15:59 ` Keith Busch 2020-09-21 16:08 ` Tianxianting 2020-09-21 16:08 ` Tianxianting
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=20200921063413.GA18298@lst.de \ --to=hch@lst.de \ --cc=axboe@fb.com \ --cc=kbusch@kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-nvme@lists.infradead.org \ --cc=sagi@grimberg.me \ --cc=tian.xianting@h3c.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.