From: hch@lst.de (Christoph Hellwig)
Subject: small CMB cleanups
Date: Mon, 15 Jan 2018 16:33:46 +0100 [thread overview]
Message-ID: <20180115153348.13105-1-hch@lst.de> (raw)
Hi all,
these two CMB cleanups were part of the p2p support series, but really
are nvme specific. Given that we're running out of time for the 4.16
merge window, what about pulling them in through the nvme tree?
next reply other threads:[~2018-01-15 15:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 15:33 Christoph Hellwig [this message]
2018-01-15 15:33 ` [PATCH 1/2] nvme-pci: clean up CMB initialization Christoph Hellwig
2018-01-16 1:51 ` Keith Busch
2018-01-17 8:31 ` Sagi Grimberg
2018-01-15 15:33 ` [PATCH 2/2] nvme-pci: clean up SMBSZ bit definitions Christoph Hellwig
2018-01-16 1:53 ` Keith Busch
2018-01-17 8:31 ` Sagi Grimberg
2018-01-15 20:04 ` small CMB cleanups Logan Gunthorpe
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=20180115153348.13105-1-hch@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.