From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>,
Andrea Cervesato <andrea.cervesato@suse.de>,
ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] Remove TODO
Date: Tue, 7 Oct 2025 17:49:54 +0200 [thread overview]
Message-ID: <20251007154954.GB140031@pevik> (raw)
In-Reply-To: <20251007154419.GA140031@pevik>
> > Hi!
> > > > TODO file is not updated and it talks about goals we already reached via
> > > > new LTP documentation. In general, it contains generic and random topics
> > > > which none is updating anymore, so it's better to remove it in order to
> > > > create less confusion for new comers. If we really want to have a TODO
> > > > list, probably the best place would be doc/ folder.
> > > I vote to have it. So yes, update it and convert it to REST format and move to
> > > doc/.
> > Well the TODO list points in there are mostly generic and are not going
> > to be finished anytime soon. E.g. "write more syscall tests" I'm not
> > sure how useful such documentation will be. Maybe we need a "where to
> > start" guide for a new devs, but I'm afraid that it would have to be
> > written from scratch.
> I'm not against the removal. "Write more syscall tests" contains valid points
> (LWN, man pages git repo), but agree it'd have to be completely rewritten.
> If anybody writes that, mentioning CVE reproducers in kernel and (g)libc commit
> messages would be also useful.
-[3] http://dir.gmane.org/gmane.linux.kernel.api
And link to https://lore.kernel.org/linux-api/ might be useful, although I
personally don't follow it.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2025-10-07 15:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 9:49 [LTP] [PATCH] Remove TODO Andrea Cervesato
2025-10-07 8:38 ` Petr Vorel
2025-10-07 10:13 ` Cyril Hrubis
2025-10-07 15:44 ` Petr Vorel
2025-10-07 15:49 ` Petr Vorel [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=20251007154954.GB140031@pevik \
--to=pvorel@suse.cz \
--cc=andrea.cervesato@suse.de \
--cc=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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