From: Christoph Hellwig <hch@lst.de>
To: Tianxianting <tian.xianting@h3c.com>
Cc: "sagi@grimberg.me" <sagi@grimberg.me>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"axboe@fb.com" <axboe@fb.com>, Keith Busch <kbusch@kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] [v2] nvme: replace meaningless judgement by checking whether req is null
Date: Wed, 23 Sep 2020 07:29:56 +0200 [thread overview]
Message-ID: <20200923052956.GA15063@lst.de> (raw)
In-Reply-To: <53ae0341e62346f985ca289c6325078d@h3c.com>
On Tue, Sep 22, 2020 at 03:47:40PM +0000, Tianxianting wrote:
> Finally, it applied:)
> Thanks again for all your kindly guides to me.
Thanks a lot for the patch!
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Tianxianting <tian.xianting@h3c.com>
Cc: Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@kernel.org>,
"axboe@fb.com" <axboe@fb.com>,
"sagi@grimberg.me" <sagi@grimberg.me>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [v2] nvme: replace meaningless judgement by checking whether req is null
Date: Wed, 23 Sep 2020 07:29:56 +0200 [thread overview]
Message-ID: <20200923052956.GA15063@lst.de> (raw)
In-Reply-To: <53ae0341e62346f985ca289c6325078d@h3c.com>
On Tue, Sep 22, 2020 at 03:47:40PM +0000, Tianxianting wrote:
> Finally, it applied:)
> Thanks again for all your kindly guides to me.
Thanks a lot for the patch!
next prev parent reply other threads:[~2020-09-23 5:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 6:25 [PATCH] [v2] nvme: replace meaningless judgement by checking whether req is null Xianting Tian
2020-09-22 6:25 ` Xianting Tian
2020-09-22 14:57 ` Keith Busch
2020-09-22 14:57 ` Keith Busch
2020-09-22 14:58 ` Christoph Hellwig
2020-09-22 14:58 ` Christoph Hellwig
2020-09-22 15:27 ` Tianxianting
2020-09-22 15:27 ` Tianxianting
2020-09-22 15:41 ` Christoph Hellwig
2020-09-22 15:41 ` Christoph Hellwig
2020-09-22 15:47 ` Tianxianting
2020-09-22 15:47 ` Tianxianting
2020-09-23 5:29 ` Christoph Hellwig [this message]
2020-09-23 5:29 ` Christoph Hellwig
2020-09-29 8:14 ` Sagi Grimberg
2020-09-29 8:14 ` Sagi Grimberg
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=20200923052956.GA15063@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: link
Be 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.