diff options
| author | Dan Williams <[email protected]> | 2016-12-17 22:50:04 +0000 |
|---|---|---|
| committer | Dan Williams <[email protected]> | 2016-12-17 22:50:04 +0000 |
| commit | d7fe1a67f658b50ec98ee1afb86df7b35c2b2593 (patch) | |
| tree | 2831af61dca813ce22e362528adee7d037d0c80f /drivers/nvdimm/namespace_devs.c | |
| parent | libnvdimm: fix mishandled nvdimm_clear_poison() return value (diff) | |
| download | kernel-d7fe1a67f658b50ec98ee1afb86df7b35c2b2593.tar.gz kernel-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 <[email protected]>
Signed-off-by: Dan Williams <[email protected]>
Diffstat (limited to 'drivers/nvdimm/namespace_devs.c')
0 files changed, 0 insertions, 0 deletions