[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANpmjNP6eZqQ8c+E5EsWdBSW-Q85FeJEu6gc7Puqro3igOXmWg@mail.gmail.com>
Date: Mon, 27 Sep 2021 14:27:39 +0200
From: Marco Elver <elver@...gle.com>
To: Isabella B do Amaral <isabellabdoamaral@....br>
Cc: Geert Uytterhoeven <geert@...ux-m68k.org>,
Enzo Ferreira <ferreiraenzoa@...il.com>,
Augusto DurĂ£es Camargo
<augusto.duraes33@...il.com>,
Brendan Higgins <brendanhiggins@...gle.com>,
Daniel Latypov <dlatypov@...gle.com>,
David Gow <davidgow@...gle.com>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
KUnit Development <kunit-dev@...glegroups.com>,
~lkcamp/patches@...ts.sr.ht,
Rodrigo Siqueira <rodrigosiqueiramelo@...il.com>
Subject: Re: [PATCH v2 3/5] test_hash.c: split test_hash_init
On Mon, 27 Sept 2021 at 14:03, Isabella B do Amaral
<isabellabdoamaral@....br> wrote:
>
> Hi, Marco,
>
> On Mon, Sep 27, 2021 at 5:17 AM Marco Elver <elver@...gle.com> wrote:
> >
> > On Mon, 27 Sept 2021 at 00:33, 'Isabella Basso' via KUnit Development
> > <kunit-dev@...glegroups.com> wrote:
> > >
> > > Split up test_hash_init so that it calls each test more explicitly
> > > insofar it is possible without rewriting the entire file. This aims at
> > > improving readability.
> > >
> > > Split tests performed on string_or as they don't interfere with those
> > > performed in hash_or. Also separate pr_info calls about skipped tests as
> > > they're not part of the tests themselves, but only warn about
> > > (un)defined arch-specific hash functions.
> > >
> > > Changes since v1:
> > > - As suggested by David Gow:
> > > 1. Rename arch-specific test functions.
> > > 2. Remove spare whitespace changes.
> > > - As suggested by Marco Elver:
> > > 1. Add struct for carrying test variables.
> >
> > Did the patches get mixed up? The struct doesn't appear to be introduced here.
>
> Yeah, thanks for the heads up! I must have mixed the messages when rebasing.
> Sorry about that. The struct was actually introduced in patch 2/5. Do
> you want to
> have a look at it or should I send the v3 with the correct message before that?
For review it's fine as-is, given it's a trivial change, but the final
series should have it in the right place.
Powered by blists - more mailing lists