linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brett A C Sheffield <bacs@librecast.net>
To: Shuah Khan <shuah@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
	linux-kselftest@vger.kernel.org, workflows@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Brett A C Sheffield <bacs@librecast.net>
Subject: [PATCH 0/1] docs: kselftest: remove link to obsolete wiki
Date: Sun, 24 Aug 2025 07:48:44 +0000	[thread overview]
Message-ID: <20250824075007.13901-2-bacs@librecast.net> (raw)

Greetings,

I've recently been getting my head around the kselftest system from a standing
start. As I do so, it makes sense that I submit any patches to fix or clarify
the accompanying documentation while I still have a newbie's perspective, as
presumably that is who such documentation is aimed at.

Paragraph three of the "Linux Kernel Selftests" documentation immediately sends
me off elsewhere to a wiki which greets me with the ominous warning:

"OBSOLETE CONTENT This wiki has been archived and the content is no longer
updated."

The wiki hasn't been updated since 2019, still refers to Freenode as an IRC
network where one might find help, and mentions kernel versions that are
probably older than some budding kernel developers.

There are a few links to Google docs with slides from presentations given over a
decade ago, but I don't think there's much in here that isn't covered more
accessibly in the kernel Documentation/

If there's anything in the archived wiki that should be retained, lets move it
into the main documentation.

Cheers,


Brett
--

Brett A C Sheffield (1):
  docs: kselftest: remove link to obsolete wiki

 Documentation/dev-tools/kselftest.rst | 5 -----
 1 file changed, 5 deletions(-)

-- 
2.49.1


             reply	other threads:[~2025-08-24  7:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-24  7:48 Brett A C Sheffield [this message]
2025-08-24  7:48 ` [PATCH 1/1] docs: kselftest: remove link to obsolete wiki Brett A C Sheffield

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=20250824075007.13901-2-bacs@librecast.net \
    --to=bacs@librecast.net \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=workflows@vger.kernel.org \
    /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).