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 v2 1/4] shell: Use conditional expansion for library setup/cleanup
Date: Wed, 27 Apr 2022 10:02:29 +0200	[thread overview]
Message-ID: <Ymj4lRlPK4KAb9iC@pevik> (raw)
In-Reply-To: <d448fbda-cbfb-e954-f5de-f1aa02b5bfd0@suse.cz>

Hi Martin,

> Hi,
> there are a few files where the only change is in the copyright comment.
> I'll leave it up to you whether you want to keep those changes or drop
> them.
Very good point, I'll remove these changes before merging.

> I've also added a suggestion for another improvement in a separate
> patchset below.
Thx!

> I've also run new tests on this patchset and everything seems to work.
> Overall:

> Reviewed-by: Martin Doucha <mdoucha@suse.cz>

Thanks a lot for testing and review!
...
> > +++ b/testcases/network/busy_poll/busy_poll_lib.sh
> > @@ -1,10 +1,11 @@
> >  #!/bin/sh
> >  # SPDX-License-Identifier: GPL-2.0-or-later
> >  # Copyright (c) 2016-2018 Oracle and/or its affiliates. All Rights Reserved.
> > +# Copyright (c) Linux Test Project, 2016-2022

> > -TST_SETUP="setup"
> >  TST_TESTFUNC="test"
> > -TST_CLEANUP="cleanup"
> > +TST_SETUP="${TST_SETUP:-setup}"
> > +TST_CLEANUP="${TST_CLEANUP:-cleanup}"

> The setup() and cleanup() functions here should get a prefix, otherwise
> we're asking for duplicate definitions. But that can be added in a
> separate patchset.

Very good point, thx! Yes, I'll send it as a separate patch.

Kind regards,
Petr

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

  reply	other threads:[~2022-04-27  8:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-22 14:41 [LTP] [PATCH v2 0/4] shell: Cleanup getopts usage Petr Vorel
2022-04-22 14:41 ` [LTP] [PATCH v2 1/4] shell: Use conditional expansion for library setup/cleanup Petr Vorel
2022-04-26 10:53   ` Martin Doucha
2022-04-27  8:02     ` Petr Vorel [this message]
2022-04-27  9:00     ` Petr Vorel
2022-04-22 14:41 ` [LTP] [PATCH v2 2/4] doc: Update library API doc Petr Vorel
2022-04-26 11:03   ` Martin Doucha
2022-04-27  8:04     ` Petr Vorel
2022-04-22 14:41 ` [LTP] [PATCH v2 3/4] tst_test.sh: Cleanup getopts usage Petr Vorel
2022-04-26 14:24   ` Martin Doucha
2022-04-27  8:10     ` Petr Vorel
2022-04-22 14:41 ` [LTP] [PATCH v2 4/4] doc: Update shell API examples Petr Vorel
2022-04-26 14:48   ` Martin Doucha
2022-04-25  3:35 ` [LTP] [PATCH v2 0/4] shell: Cleanup getopts usage Li Wang

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=Ymj4lRlPK4KAb9iC@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.