From: Quentin Schulz <quentin.schulz@cherry.de>
To: Johan Jonker <jbx6244@gmail.com>
Cc: kever.yang@rock-chips.com, sjg@chromium.org, trini@konsulko.com,
u-boot@lists.u-boot-project.org, eddie.cai.linux@gmail.com
Subject: Re: [PATCH v5 3/9] rockchip: doc: remove TODO
Date: Wed, 12 Aug 2026 15:34:04 +0200 [thread overview]
Message-ID: <44f1970c-aee2-49a4-b532-80abd7547e12@cherry.de> (raw)
In-Reply-To: <61027ad5-678f-4598-8aa1-cba5e90c4e2f@gmail.com>
Hi Johan,
On 8/6/26 1:11 PM, Johan Jonker wrote:
> Don't try to guess the future consensus. And don't add
> a TODO if you don't have the intent to send an immediate
> follow up. Remove the TODO in a constantly changing document.
>
Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
Thanks!
Quentin
next prev parent reply other threads:[~2026-08-12 13:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 11:08 [PATCH v5 0/9] doc: clean up README.rockchip Johan Jonker
2026-08-06 11:10 ` [PATCH v5 1/9] rockchip: scripts: remove rkmux.py Johan Jonker
2026-08-06 11:10 ` [PATCH v5 2/9] rockchip: doc: add mask ROM mode text Johan Jonker
2026-08-12 13:32 ` Quentin Schulz via U-Boot
2026-08-06 11:11 ` [PATCH v5 3/9] rockchip: doc: remove TODO Johan Jonker
2026-08-12 13:34 ` Quentin Schulz [this message]
2026-08-06 11:11 ` [PATCH v5 4/9] rockchip: doc: add more building instructions Johan Jonker
2026-08-12 13:44 ` Quentin Schulz via U-Boot
2026-08-12 14:48 ` Quentin Schulz via U-Boot
2026-08-06 11:11 ` [PATCH v5 5/9] rockchip: tools: rksd: remove reference to README.rockchip Johan Jonker
2026-08-06 11:11 ` [PATCH v5 6/9] rockchip: tools: rkspi: " Johan Jonker
2026-08-06 11:12 ` [PATCH v5 7/9] rockchip: tools: add comment section to rkimage.c Johan Jonker
2026-08-12 14:06 ` Quentin Schulz via U-Boot
2026-08-06 11:12 ` [PATCH v5 8/9] rockchip: doc: rockusb: remove reference to README.rockchip Johan Jonker
2026-08-06 11:12 ` [PATCH v5 9/9] rockchip: doc: remove README.rockchip Johan Jonker
2026-08-12 14:45 ` Quentin Schulz via U-Boot
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=44f1970c-aee2-49a4-b532-80abd7547e12@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=eddie.cai.linux@gmail.com \
--cc=jbx6244@gmail.com \
--cc=kever.yang@rock-chips.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.u-boot-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.