u-boot-amlogic archives
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@cherry.de>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Quentin Schulz <foss+uboot@0leil.net>
Cc: Tom Rini <trini@konsulko.com>, Simon Glass <sjg@chromium.org>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Marek Vasut <marek.vasut+renesas@mailbox.org>,
	Ilias Apalodimas <ilias.apalodimas@linaro.org>,
	Viacheslav Bocharov <adeep@lexina.in>,
	Stefano Babic <sbabic@nabladev.com>,
	Fabio Estevam <festevam@gmail.com>, Soeren Moch <smoch@web.de>,
	Alper Nebi Yasak <alpernebiyasak@gmail.com>,
	Le Jin <le.jin@siemens.com>, Jan Kiszka <jan.kiszka@siemens.com>,
	Nobuhiro Iwamatsu <iwamatsu@nigauri.org>,
	Peter Robinson <pbrobinson@gmail.com>,
	Sean Anderson <seanga2@gmail.com>, Bin Meng <bmeng.cn@gmail.com>,
	Lukasz Majewski <lukma@denx.de>,
	Mattijs Korpershoek <mkorpershoek@kernel.org>,
	u-boot@lists.u-boot-project.org, u-boot-amlogic@groups.io,
	"NXP i.MX U-Boot Team" <uboot-imx@nxp.com>
Subject: Re: [PATCH next 00/45] doc: fix some issues reported by linkcheck
Date: Thu, 27 Aug 2026 21:59:13 +0200	[thread overview]
Message-ID: <81241329-290d-4c4e-80b4-c3bbdaa26cf8@cherry.de> (raw)
In-Reply-To: <a2b54c83-97a2-4b81-9c6c-6be32f127985@gmx.de>

Hi Heinrich,

On 8/27/26 1:03 PM, Heinrich Schuchardt wrote:
> On 8/25/26 18:49, Quentin Schulz wrote:
>> Saw a dead link and made the mistake of running `make linkcheckdocs`.
>> Now I'm knee-deep in it and cannot ignore all the dead and redirected
>> links. A day later, I've had enough so this is what I managed to fix in
>> that time. There are many URLs still redirecting (could be fine, but
>> needs to be individually checked as some big companies have a tendencies
>> to redirect to generic pages instead of issuing 404s...) or returning
>> 4xx. The issue is that those 4xx also need to be individually checked
>> because since the AIpocalypse has started many websites now have web
>> crawler protection in place and linkcheck will trigger those and be
>> denied access (or be heavily rate limited).
>>
>> Please be mindful and only run this script once, save its output and
>> work on fixing individual errors without rerunning the script, otherwise
>> we would only participate in hammering websites even more (linkcheck
>> runs multiple workers in parallel and retries when rate-limited).
>>
>> Note that linkcheck doesn't check for links in code-blocks so our
>> instructions may point at dead links also.
>>
>> At an attempt to avoid tens of people running linkcheck at the same
>> time, here's the output sorted and filtered on !ok status:
> 
> Hello Quentin,
> 
> in patchwork.ozlabs.org, lore.kernel.org/u-boot, and https:// 
> eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.u-boot- 
> project.org%2F&data=05%7C02%7Cquentin.schulz%40cherry.de%7C3c09d2cdb28041d4b5cc08df042aede7%7C5e0e1b5221b54e7b83bb514ec460677e%7C0%7C0%7C639234254572323528%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=EVMJd%2FfRl5KHcaDFXZvcck%2F38e8nTUtVCJ61A8CT1Cg%3D&reserved=0 only patches 1 - 21 arrived.
> 

I know, 
https://lists.u-boot-project.org/pipermail/u-boot/2026-August/629812.html 
(for some reason it didn't make it to lore.kernel.org...).

I once again got rate limited for 24h, so the last three patches will 
have to wait for this weekend. I'll likely need to split this in two or 
three for a v2 so I don't get rate-limited in the middle of a series.

> Please, send the rest of the series using
> 
> --in-reply-to=20260825-linkcheck-v1-0-ee7573fe3a4a@cherry.de
> 

Thanks, was wondering how to do that!

Cheers,
Quentin


  parent reply	other threads:[~2026-08-28 13:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260825-linkcheck-v1-0-ee7573fe3a4a@cherry.de>
2026-08-25 16:57 ` [PATCH next 00/45] doc: fix some issues reported by linkcheck Quentin Schulz
2026-08-25 17:08 ` Tom Rini
     [not found] ` <20260825-linkcheck-v1-12-ee7573fe3a4a@cherry.de>
2026-08-26  7:59   ` [PATCH next 12/45] doc: board/amlogic: jethub-j100: update product page Viacheslav
     [not found] ` <20260825-linkcheck-v1-13-ee7573fe3a4a@cherry.de>
2026-08-26  9:10   ` [PATCH next 13/45] doc: board/amlogic: jethub-j80: use redirect link directly Viacheslav
     [not found] ` <20260825-linkcheck-v1-11-ee7573fe3a4a@cherry.de>
2026-08-26 10:56   ` [PATCH next 11/45] doc: develop: uefi: update link to ipxe git repo Ilias Apalodimas
     [not found] ` <a2b54c83-97a2-4b81-9c6c-6be32f127985@gmx.de>
2026-08-27 19:59   ` Quentin Schulz [this message]
     [not found] ` <20260828210003.823954-2-foss+uboot@0leil.net>
2026-09-11 11:42   ` [PATCH next 45/45] binman: gbb: update link Simon Glass

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=81241329-290d-4c4e-80b4-c3bbdaa26cf8@cherry.de \
    --to=quentin.schulz@cherry.de \
    --cc=adeep@lexina.in \
    --cc=alpernebiyasak@gmail.com \
    --cc=bmeng.cn@gmail.com \
    --cc=festevam@gmail.com \
    --cc=foss+uboot@0leil.net \
    --cc=ilias.apalodimas@linaro.org \
    --cc=iwamatsu@nigauri.org \
    --cc=jan.kiszka@siemens.com \
    --cc=le.jin@siemens.com \
    --cc=lukma@denx.de \
    --cc=marek.vasut+renesas@mailbox.org \
    --cc=mkorpershoek@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=pbrobinson@gmail.com \
    --cc=sbabic@nabladev.com \
    --cc=seanga2@gmail.com \
    --cc=sjg@chromium.org \
    --cc=smoch@web.de \
    --cc=trini@konsulko.com \
    --cc=u-boot-amlogic@groups.io \
    --cc=u-boot@lists.u-boot-project.org \
    --cc=uboot-imx@nxp.com \
    --cc=xypron.glpk@gmx.de \
    /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