From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/2] lib: Add support for test tags
Date: Tue, 15 Oct 2019 11:57:24 +0200 [thread overview]
Message-ID: <20191015095724.GC14021@rei> (raw)
In-Reply-To: <87tv8awj36.fsf@rpws.prws.suse.cz>
Hi!
> It may be better just to print "Associated Linux kernel commit: ..." and
> "Associated bug ID: CVE-..." in the loop. Then we can avoid any
> discussions about what type of test it is.
I will try that.
> Also, a test description tag could be added if necessary.
My plan is actually to keep the description in the top level comment but
parse that by the docparse tool, then we will have a browseable test
documentation that could be put to the web and we can point to that
here.
> Maybe it would also be a good idea to link back to the test source code
> on github? Possibly this info could be injected at build time?
I tried to inject things at a build time and it wasn't pretty, so I
would like to avoid that.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2019-10-15 9:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 11:25 [LTP] [PATCH 0/2] Add support for a test tags Cyril Hrubis
2019-10-14 11:25 ` [LTP] [PATCH 1/2] lib: Add support for " Cyril Hrubis
2019-10-15 5:12 ` Li Wang
2019-10-15 7:42 ` Richard Palethorpe
2019-10-15 9:57 ` Cyril Hrubis [this message]
2019-10-15 9:54 ` Cyril Hrubis
2019-10-16 13:30 ` Petr Vorel
2019-10-16 14:46 ` Cyril Hrubis
2019-10-16 19:43 ` Petr Vorel
2019-10-14 11:25 ` [LTP] [PATCH 2/2] testcases/kernel: Add linux git and CVE tags Cyril Hrubis
2019-10-15 4:54 ` Li Wang
2019-10-15 9:52 ` Cyril Hrubis
2019-10-16 13:21 ` Petr Vorel
2019-10-17 3:22 ` Li Wang
2019-10-17 8:38 ` Jan Stancek
-- strict thread matches above, loose matches on Subject: below --
2019-10-14 11:23 [LTP] [PATCH 0/2] Add support for a test tags Cyril Hrubis
2019-10-14 11:23 ` [LTP] [PATCH 1/2] lib: Add support for " Cyril Hrubis
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=20191015095724.GC14021@rei \
--to=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