public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Carlos Bilbao <carlos.bilbao.osdev@gmail.com>,
	sergio.collado@gmail.com, peterz@infradead.org,
	rdunlap@infradead.org
Cc: bilbao@vt.edu, jembid@ucm.es, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org,
	Carlos Bilbao <carlos.bilbao.osdev@gmail.com>
Subject: Re: [PATCH v3 0/1] docs: scheduler: Start documenting the EEVDF scheduler
Date: Wed, 07 Aug 2024 13:41:36 -0600	[thread overview]
Message-ID: <87v80cqfwv.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20240720002207.444286-1-carlos.bilbao.osdev@gmail.com>

Carlos Bilbao <carlos.bilbao.osdev@gmail.com> writes:

> I was in the process of updating the CFS documentation, as Sergio proposed,
> when I realized we don't have any EEVDF documentation to point to. I have
> started it. I know it isn't a lot of info about EEVDF in the doc, but (1) I
> wanted to get the ball rolling, and (2) I prefer to keep it light until we
> have a solid idea of how EEVDF will actually end up. This could take a
> while. When or if it stops being an option, we can revisit it.
>
> Sergio, if you’d like to update the Spanish translations of CFS and add one
> for this new EEVDF doc, please go for it! ;)
>
> Thanks,
> Carlos
>
> P.S.: Jon, I have triple-checked for compilation warnings, but if you
>       encounter any, please LMK the versions of your tools so I can match
>       them moving forward.
>
> Carlos:
>   docs: scheduler: Start documenting the EEVDF scheduler
>
> ---
> Changelog:
>   v3: Removed labels and used instead paths to documents.
>   v2: Move file within scheduler index. Remove incorrect subsection
>       numbering.
>
> ---
>  Documentation/scheduler/index.rst            |  1 +
>  Documentation/scheduler/sched-design-CFS.rst | 10 +++--
>  Documentation/scheduler/sched-eevdf.rst      | 43 ++++++++++++++++++++
>  3 files changed, 50 insertions(+), 4 deletions(-)
>  create mode 100644 Documentation/scheduler/sched-eevdf.rst

So, nobody has screamed, so I went ahead and applied this.

Thanks,

jon

      parent reply	other threads:[~2024-08-07 19:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-20  0:22 [PATCH v3 0/1] docs: scheduler: Start documenting the EEVDF scheduler Carlos Bilbao
2024-07-20  0:22 ` [PATCH v3 1/1] " Carlos Bilbao
2024-08-07 19:41 ` Jonathan Corbet [this message]

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=87v80cqfwv.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=bilbao@vt.edu \
    --cc=carlos.bilbao.osdev@gmail.com \
    --cc=jembid@ucm.es \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rdunlap@infradead.org \
    --cc=sergio.collado@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