From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Qais Yousef <qyousef@layalina.io>
Cc: kernel test robot <lkp@intel.com>, Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Lukasz Luba <lukasz.luba@arm.com>,
Xuewen Yan <xuewen.yan94@gmail.com>, Wei Wang <wvw@google.com>,
Jonathan JMChen <Jonathan.JMChen@mediatek.com>,
Hank <han.lin@mediatek.com>, Paul Bone <pbone@mozilla.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation: sched: Add a new sched-util-clamp.rst
Date: Wed, 16 Nov 2022 15:36:19 +0700 [thread overview]
Message-ID: <Y3ShA8SGM4PTYPLJ@debian.me> (raw)
In-Reply-To: <20221115205547.3f4kzig5r44ipv3b@airbuntu>
[-- Attachment #1: Type: text/plain, Size: 2947 bytes --]
On Tue, Nov 15, 2022 at 08:55:47PM +0000, Qais Yousef wrote:
> > > 2.1 BUCKETS:
> > > -------------
> > >
> > > +.. code-block:: c
> > > +
> > > [struct rq]
> > >
> > > -(bottom) (top)
> > > + (bottom) (top)
> > >
> > > - 0 1024
> > > - | |
> > > - +-----------+-----------+-----------+---- ----+-----------+
> > > - | Bucket 0 | Bucket 1 | Bucket 2 | ... | Bucket N |
> > > - +-----------+-----------+-----------+---- ----+-----------+
> > > - : : :
> > > - +- p0 +- p3 +- p4
> > > - : :
> > > - +- p1 +- p5
> > > - :
> > > - +- p2
> > > + 0 1024
> > > + | |
> > > + +-----------+-----------+-----------+---- ----+-----------+
> > > + | Bucket 0 | Bucket 1 | Bucket 2 | ... | Bucket N |
> > > + +-----------+-----------+-----------+---- ----+-----------+
> > > + : : :
> > > + +- p0 +- p3 +- p4
> > > + : :
> > > + +- p1 +- p5
> > > + :
> > > + +- p2
> >
> > The code block above is diagram, isn't it? Thus specifying language for
> > syntax highlighting (in this case ``c``) isn't appropriate.
>
> I could do with a helping hand here actually. I am a text only person but
> trying to follow the new rst docs; but I don't have a clue to be honest.
>
> I did try to find the right directive, but I couldn't find it. What should be
> specified for this diagram?
Just leave ..code-block:: directive alone or use simpler double colon
(::). The highlighting will not be applied to the code snippet.
> > > @@ -200,6 +203,8 @@ The rq has a bucket for each uclamp_id: [UCLAMP_MIN, UCLAMP_MAX].
> > > The range of each bucket is 1024/N. For example for the default value of 5 we
> > > will have 5 buckets, each of which will cover the following range:
> > >
> > > +.. code-block:: c
> > > +
> >
> > Again, why ``c`` syntax highlighting?
>
> This is a C code snippet. What would be better to use? I think I was getting
> errors if I don't specify something. But again; I was touching my way around in
> the dark here trying to figure it out.
>
Yup, that's the correct language for highlighting.
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-11-16 8:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221113152629.3wbyeejsj5v33rvu@airbuntu>
2022-11-14 8:55 ` [PATCH] Documentation: sched: Add a new sched-util-clamp.rst Bagas Sanjaya
2022-11-15 20:55 ` Qais Yousef
2022-11-16 8:36 ` Bagas Sanjaya [this message]
2022-11-20 20:52 ` Qais Yousef
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y3ShA8SGM4PTYPLJ@debian.me \
--to=bagasdotme@gmail.com \
--cc=Jonathan.JMChen@mediatek.com \
--cc=corbet@lwn.net \
--cc=dietmar.eggemann@arm.com \
--cc=han.lin@mediatek.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lukasz.luba@arm.com \
--cc=mingo@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pbone@mozilla.com \
--cc=peterz@infradead.org \
--cc=qyousef@layalina.io \
--cc=vincent.guittot@linaro.org \
--cc=wvw@google.com \
--cc=xuewen.yan94@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).