summaryrefslogtreecommitdiffstats
path: root/Documentation/driver-api/loop-file-fmt.rst
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/driver-api/loop-file-fmt.rst')
-rw-r--r--Documentation/driver-api/loop-file-fmt.rst6
1 files changed, 4 insertions, 2 deletions
diff --git a/Documentation/driver-api/loop-file-fmt.rst b/Documentation/driver-api/loop-file-fmt.rst
index 335fde30f364..b666b19a6e39 100644
--- a/Documentation/driver-api/loop-file-fmt.rst
+++ b/Documentation/driver-api/loop-file-fmt.rst
@@ -1,3 +1,5 @@
+.. SPDX-License-Identifier: GPL-2.0
+
===========================================
Loopback block device file format subsystem
===========================================
@@ -48,7 +50,7 @@ Finite state machine
To prevent a misuse of the internal file format API, the file format subsystem
implements an finite state machine. The state machine consists of two states
-and a transition for each internal API function. The state
+and a transition for each internal API function. The state
*file_fmt_uninitialized* of a loop file format denotes that the file format is
already allocated but not initialized. After the initialization, the file
format's state is set to *file_fmt_initialized*. In this state, all IO related
@@ -66,7 +68,7 @@ The entire implemented finite state machine looks like the following:
digraph file_fmt_states {
rankdir = LR;
- node [ shape = point, label = "" ] ENTRY, EXIT;
+ node [ shape = point, label = "" ] ENTRY, EXIT;
node [ shape = circle, label = "file_fmt_uninitialized" ] UN;
node [ shape = doublecircle, label = "file_fmt_initialized" ] IN;
subgraph helper {