From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvme-loop: fix kernel oops in case of unhandled command
Date: Wed, 28 Mar 2018 10:08:13 +0200 [thread overview]
Message-ID: <20180328080813.GD20373@lst.de> (raw)
In-Reply-To: <20180326033937.7866-1-ming.lei@redhat.com>
The patch looks good:
Reviewed-by: Christoph Hellwig <hch at lst.de>
Buy can you trim the long but not very useful trace from the commit log?
next prev parent reply other threads:[~2018-03-28 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 3:39 [PATCH] nvme-loop: fix kernel oops in case of unhandled command Ming Lei
2018-03-28 8:08 ` Christoph Hellwig [this message]
2018-03-28 15:07 ` Keith Busch
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=20180328080813.GD20373@lst.de \
--to=hch@lst.de \
/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.