summaryrefslogtreecommitdiffstats
path: root/drivers/zorro
diff options
context:
space:
mode:
authorJan Höppner <hoeppner@linux.vnet.ibm.com>2017-05-23 16:17:30 +0200
committerMartin Schwidefsky <schwidefsky@de.ibm.com>2017-06-12 16:26:00 +0200
commitb487a914f853545842a0899329b6b72fe56c4081 (patch)
treed66b22092f9f816f5c752edc525e1fbf149a1101 /drivers/zorro
parent7e9710af2301e76421a6a8f2655937651279f5c4 (diff)
downloadop-kernel-dev-b487a914f853545842a0899329b6b72fe56c4081.zip
op-kernel-dev-b487a914f853545842a0899329b6b72fe56c4081.tar.gz
s390/dasd: Display read-only attribute correctly
We have two flags, DASD_FLAG_DEVICE_RO and DASD_FEATURE_READONLY, that tell us whether a device is read-only. DASD_FLAG_DEVICE_RO is set when a device is attached as read-only to z/VM and DASD_FEATURE_READONLY is set when either the corresponding kernel parameter is configured, or the read-only state is changed via sysfs. This is valuable information in any case. However, only the feature flag is being checked at the moment when we display the current state. Fix this by checking both flags. Reviewed-by: Stefan Haberland <sth@linux.vnet.ibm.com> Signed-off-by: Jan Höppner <hoeppner@linux.vnet.ibm.com> Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'drivers/zorro')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud