You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/source/yaml-specs.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -324,7 +324,7 @@ A WARL csr/field has the following skeleton in the riscv-config:
324
324
1. No legal value must exceed the maximum value which can be supported (based on the width of the field).
325
325
2. Functions should be exhaustive with respect to every possible combination of the dependency values.
326
326
3. within a string for `legal` all bits of the csr/field should be covered. No bits must be left undefined.
327
-
4. A legal string should not be a combination ranges split into parts or a simple bitmask function for the entire field. mixing bitmask and ranges it allowed. The following example is an invalid spec:
327
+
4. A legal string should be a combination of ranges split into parts or a simple bitmask function for the entire field. Mixing bitmask and ranges is not allowed. The following example is an invalid spec:
0 commit comments