On Fri, Apr 28, 2023 at 1:50 AM Christian König <christian.koenig@xxxxxxx> wrote: > > Am 27.04.23 um 19:53 schrieb Rob Clark: > > From: Rob Clark <robdclark@xxxxxxxxxxxx> > > > > Fix a couple missing ':'s. > > > > Signed-off-by: Rob Clark <robdclark@xxxxxxxxxxxx> > > Reviewed-by: Rodrigo Vivi <rodrigo.vivi@xxxxxxxxx> > > Reviewed-by: Christian König <christian.koenig@xxxxxxx> > > Since this is a pretty clear fix I suggest to get this pushed to reduce > the number of patches in the set. Thanks, this is fine by me if someone wants to push it for me. Note that the later .rst updates in this series depend on this so if/when they are merged it probably should be the same tree BR, -R > Christian. > > > --- > > Documentation/gpu/drm-usage-stats.rst | 4 ++-- > > 1 file changed, 2 insertions(+), 2 deletions(-) > > > > diff --git a/Documentation/gpu/drm-usage-stats.rst b/Documentation/gpu/drm-usage-stats.rst > > index b46327356e80..72d069e5dacb 100644 > > --- a/Documentation/gpu/drm-usage-stats.rst > > +++ b/Documentation/gpu/drm-usage-stats.rst > > @@ -105,7 +105,7 @@ object belong to this client, in the respective memory region. > > Default unit shall be bytes with optional unit specifiers of 'KiB' or 'MiB' > > indicating kibi- or mebi-bytes. > > > > -- drm-cycles-<str> <uint> > > +- drm-cycles-<str>: <uint> > > > > Engine identifier string must be the same as the one specified in the > > drm-engine-<str> tag and shall contain the number of busy cycles for the given > > @@ -117,7 +117,7 @@ larger value within a reasonable period. Upon observing a value lower than what > > was previously read, userspace is expected to stay with that larger previous > > value until a monotonic update is seen. > > > > -- drm-maxfreq-<str> <uint> [Hz|MHz|KHz] > > +- drm-maxfreq-<str>: <uint> [Hz|MHz|KHz] > > > > Engine identifier string must be the same as the one specified in the > > drm-engine-<str> tag and shall contain the maximum frequency for the given >
