diff options
| author |   Dan Williams <dan.j.williams@intel.com> | 2016-12-17 14:50:04 -0800 |
|---|---|---|
| committer | Dan Williams <dan.j.williams@intel.com> | 2016-12-17 14:50:04 -0800 |
| commit | d7fe1a67f658b50ec98ee1afb86df7b35c2b2593 (patch) | |
| tree | 2831af61dca813ce22e362528adee7d037d0c80f /tools/testing | |
| parent | libnvdimm: fix mishandled nvdimm_clear_poison() return value (diff) | |
| download | linux-dev-d7fe1a67f658b50ec98ee1afb86df7b35c2b2593.tar.xz linux-dev-d7fe1a67f658b50ec98ee1afb86df7b35c2b2593.zip | |
dax: add region 'id', 'size', and 'align' attributes
While this information is available by looking at the nvdimm parent
device that may not always be the case when/if we add support for other
memory regions. Tooling should not depend on walking a given ancestor
topology that is not guaranteed by the device's class. For example, a
device-dax instance will always have a dax_region parent, but it may not
always have a libnvdimm "dax" device as a grandparent.
Reported-by: Johannes Thumshirn <jthumshirn@suse.de>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Diffstat (limited to 'tools/testing')
0 files changed, 0 insertions, 0 deletions