From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvme/pci: Check segement valid for SGL use
Date: Mon, 15 Jan 2018 17:01:48 +0100 [thread overview]
Message-ID: <20180115160148.GA9749@lst.de> (raw)
In-Reply-To: <20180115130723.31469-1-keith.busch@intel.com>
Actually this needs to go into nvme-4.15. The offending commit is
only in 4.15-rc, and not in nvme-4.16 or Jens' for-4.16 tree.
next prev parent reply other threads:[~2018-01-15 16:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 13:07 [PATCH] nvme/pci: Check segement valid for SGL use Keith Busch
2018-01-15 13:11 ` Paul Menzel
2018-01-15 15:21 ` Christoph Hellwig
2018-01-15 16:01 ` Christoph Hellwig [this message]
2018-01-15 16:20 ` Jens Axboe
2018-01-15 17:22 ` Christoph Hellwig
2018-01-15 17:25 ` Jens Axboe
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=20180115160148.GA9749@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.