public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: "Sergio González Collado" <sergio.collado@gmail.com>,
	"Carlos Bilbao" <carlos.bilbao.osdev@gmail.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-kernel-mentees@lists.linuxfoundation.org,
	"Sergio González Collado" <sergio.collado@gmail.com>
Subject: Re: [PATCH v3] docs/sp_Sp: Add translation to spanish of the documentation related to EEVDF
Date: Mon, 26 Aug 2024 15:33:03 -0600	[thread overview]
Message-ID: <87a5gz6kc0.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20240824095402.7706-1-sergio.collado@gmail.com>

Sergio González Collado <sergio.collado@gmail.com> writes:

> Translate Documentation/scheduler/sched-eevdf.rst to Spanish.
>
> Signed-off-by: Sergio González Collado <sergio.collado@gmail.com>
> Reviewed-by: Carlos Bilbao <carlos.bilbao.osdev@gmail.com>
> ---
>  v1 -> v2: corrected the commit message
> ---
>  v2 -> v3: corrected typos
> ---
>  .../translations/sp_SP/scheduler/index.rst    |  1 +
>  .../sp_SP/scheduler/sched-design-CFS.rst      |  8 +--
>  .../sp_SP/scheduler/sched-eevdf.rst           | 58 +++++++++++++++++++
>  3 files changed, 63 insertions(+), 4 deletions(-)
>  create mode 100644 Documentation/translations/sp_SP/scheduler/sched-eevdf.rst

This file adds a new docs-build warning:

> Documentation/translations/sp_SP/scheduler/sched-eevdf.rst:4: WARNING: undefined label: 'sched_eevdf'

I went ahead and fixed it with this change:

-:Original: :ref:`Documentation/scheduler/sched-eevdf.rst <sched_eevdf>`
+:Original: Documentation/scheduler/sched-eevdf.rst

But I *really* wish I didn't have to find and fix such things...

jon

      reply	other threads:[~2024-08-26 21:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-24  9:54 [PATCH v3] docs/sp_Sp: Add translation to spanish of the documentation related to EEVDF Sergio González Collado
2024-08-26 21:33 ` 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=87a5gz6kc0.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=carlos.bilbao.osdev@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.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