| Message ID | 20210209021843.GP7193@magnolia (mailing list archive) |
|---|---|
| State | Accepted |
| Headers | show |
| Series | xfs: fix rst syntax error in admin guide | expand |
On 2/8/21 8:18 PM, Darrick J. Wong wrote: > From: Darrick J. Wong <djwong@kernel.org> > > Tables are supposed to have a matching line of "===" to signal the end > of a table. The rst compiler gets grouchy if it encounters EOF instead, > so fix this warning. > > Reported-by: Stephen Rothwell <sfr@canb.auug.org.au> > Signed-off-by: Darrick J. Wong <djwong@kernel.org> <cuts and pastes the prior "============ ===========" next to the new one, yup pretty, pretty good> Reviewed-by: Eric Sandeen <sandeen@redhat.com> > --- > Documentation/admin-guide/xfs.rst | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/Documentation/admin-guide/xfs.rst b/Documentation/admin-guide/xfs.rst > index d2064a52811b..6178153d3320 100644 > --- a/Documentation/admin-guide/xfs.rst > +++ b/Documentation/admin-guide/xfs.rst > @@ -536,3 +536,4 @@ The interesting knobs for XFS workqueues are as follows: > cpumask CPUs upon which the threads are allowed to run. > nice Relative priority of scheduling the threads. These are the > same nice levels that can be applied to userspace processes. > +============ =========== >
On 2/8/21 18:20, Darrick J. Wong wrote: > From: Darrick J. Wong <djwong@kernel.org> > > Tables are supposed to have a matching line of "===" to signal the end > of a table. The rst compiler gets grouchy if it encounters EOF instead, > so fix this warning. > > Reported-by: Stephen Rothwell <sfr@canb.auug.org.au> > Signed-off-by: Darrick J. Wong <djwong@kernel.org> Indeed the last line "===" is missing from xfs/for-next branch. Looks good. Reviewed-by: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
diff --git a/Documentation/admin-guide/xfs.rst b/Documentation/admin-guide/xfs.rst index d2064a52811b..6178153d3320 100644 --- a/Documentation/admin-guide/xfs.rst +++ b/Documentation/admin-guide/xfs.rst @@ -536,3 +536,4 @@ The interesting knobs for XFS workqueues are as follows: cpumask CPUs upon which the threads are allowed to run. nice Relative priority of scheduling the threads. These are the same nice levels that can be applied to userspace processes. +============ ===========