From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: kernel-team@android.com, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v7 1/1] mmapstress01: refactor to tst_test framework
Date: Mon, 14 Nov 2022 15:17:15 +0100 [thread overview]
Message-ID: <Y3JN6wLNezRUodYD@pevik> (raw)
In-Reply-To: <Y3IdXcWbV/svAUWl@yuki>
Hi Cyril, all,
> Hi!
> > @Metan: I wonder if this can be fixed in docparser.
> For the time being I would rather keep the structures inline in the
> tst_test.
Good to know.
> Fixing this in the dumb parser would be doable, but quite an effort. We
> would have to start tracking global variables the same way we track
> macros.
> > @Richie: If not, it would be nice to have check for it (I'll add issue with
> > "check" label).
> And rewrite to any other system would be even bigger effort. Sounds like
> a hackweek project if anyone is interested.
Understand if nobody (even Richie) wants to put any effort into automatic check.
I certainly don't. I'll send a patch where I document the need to put inline in
the tst_test (sending patch mainly due my bad English).
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2022-11-14 14:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 21:58 [LTP] [PATCH v7 0/1] mmapstress01: refactor to ltp framework Edward Liaw via ltp
2022-10-27 21:58 ` [LTP] [PATCH v7 1/1] mmapstress01: refactor to tst_test framework Edward Liaw via ltp
2022-11-08 10:49 ` Richard Palethorpe
2022-11-08 11:19 ` Richard Palethorpe
2022-11-11 16:53 ` Petr Vorel
2022-11-11 17:07 ` Petr Vorel
2022-11-14 10:00 ` Richard Palethorpe
2022-11-14 9:44 ` Richard Palethorpe
2022-11-14 10:50 ` Cyril Hrubis
2022-11-14 14:17 ` 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=Y3JN6wLNezRUodYD@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@suse.cz \
--cc=kernel-team@android.com \
--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