All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Martin Doucha <mdoucha@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v3 5/5] busy_poll: Move TST_{SETUP, CLEANUP} to the tests
Date: Mon, 2 May 2022 15:50:03 +0200	[thread overview]
Message-ID: <Ym/hi05AYBqtifLO@pevik> (raw)
In-Reply-To: <cfabdc28-fef8-576f-7845-630a443833d1@suse.cz>

Hi Martin,

> On 29. 04. 22 20:09, Petr Vorel wrote:
> > I was thinking about it as well. Makes sense, but then it hides the fact that
> > busy_poll_lib.sh contain other API variables (missing TST_TESTFUNC suggest that
> > there are some variables in busy_poll_lib.sh). Anyway, I'm ok to move it there
> > as well, just document that sharing variables between library and test will be
> > always a bit problematic.

> Now that you mention the other variables in busy_poll_lib.sh, I guess
> that TST_MIN_KVER and TST_NEEDS_CMDS should use conditional expansion so
> that the values can be changed in the tests.
Makes sense. But I'd probably prefer to postpone this commit,
because TST_NEEDS_CMDS will be in more shell libraries.
Because even this cleanup so far wasn't my intention, I'd prefer to get it
merged soon so that I can post rebased fixes for tst_net.sh with disabled IPv6
(to get them merged before release).

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2022-05-02 13:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28  6:56 [LTP] [PATCH v3 5/5] busy_poll: Move TST_{SETUP, CLEANUP} to the tests Petr Vorel
2022-04-29 16:05 ` Martin Doucha
2022-04-29 18:09   ` Petr Vorel
2022-05-02  8:54     ` Martin Doucha
2022-05-02 13:50       ` Petr Vorel [this message]
2022-05-02 14:00         ` Martin Doucha

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=Ym/hi05AYBqtifLO@pevik \
    --to=pvorel@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=mdoucha@suse.cz \
    /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.