From: jonathan.derrick@intel.com (Jon Derrick)
Subject: [PATCH 2/3] NVMe: Generate resource tree for CMB
Date: Wed, 30 Dec 2015 13:59:41 -0700 [thread overview]
Message-ID: <20151230205941.GA5808@localhost.localdomain> (raw)
In-Reply-To: <1451497679-1195-3-git-send-email-jonathan.derrick@intel.com>
> Maintains a resource tree for CMB resources. A sysfs file is exposed
> which is similar to a pci_dev resources file. The top entry is the
> range of the whole CMB resource, and the entries below that are the
> driver-reserved regions (currently only used by SQes).
>
2 & 3's logs got mixed up when I split them.
If the patches look fine I will resend with better logs.
next prev parent reply other threads:[~2015-12-30 20:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 17:47 [PATCH 0/3] NVMe: Introduce CMB allocation scheme Jon Derrick
2015-12-30 17:47 ` [PATCH 1/3] NVMe: Introduce sysfs entries for submission queues in CMB Jon Derrick
2015-12-30 17:47 ` [PATCH 2/3] NVMe: Generate resource tree for CMB Jon Derrick
2015-12-30 20:59 ` Jon Derrick [this message]
2015-12-30 17:47 ` [PATCH 3/3] NVMe: Create CMB resource sysfs file Jon Derrick
2016-01-06 20:13 ` [PATCH 0/3] NVMe: Introduce CMB allocation scheme Keith Busch
2016-01-06 21:24 ` Stephen Bates
2016-01-13 0:08 ` Keith Busch
2016-01-13 0:27 ` Jon Derrick
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=20151230205941.GA5808@localhost.localdomain \
--to=jonathan.derrick@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox