Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Artur Alves Cavalcante de Barros <arturacb@gmail.com>
To: Shuah Khan <skhan@linuxfoundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Brendan Higgins <brendan.higgins@linux.dev>,
	David Gow <davidgow@google.com>, Rae Moar <rmoar@google.com>,
	linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com
Cc: n@nfraprado.net, andrealmeid@riseup.net, vinicius@nukelet.com,
	diego.daniel.professional@gmail.com
Subject: Re: [PATCH v3 0/1] Add KUnit tests for llist
Date: Thu, 19 Sep 2024 19:27:16 -0300	[thread overview]
Message-ID: <bcd02805-5262-4d44-9528-64c63a55e8b6@gmail.com> (raw)
In-Reply-To: <bd5eb792-124f-4eaa-9ff9-a99765d1ef73@linuxfoundation.org>

On 9/19/24 1:01 PM, Shuah Khan wrote:
> On 9/16/24 18:51, Artur Alves wrote:
>> Hi all,
>>
>> This is part of a hackathon organized by LKCAMP[1], focused on writing
>> tests using KUnit. We reached out a while ago asking for advice on what
>> would be a useful contribution[2] and ended up choosing data structures
>> that did not yet have tests.
>>
>> This patch adds tests for the llist data structure, defined in
>> include/linux/llist.h, and is inspired by the KUnit tests for the doubly
>> linked list in lib/list-test.c[3].
>>
>> It is important to note that this patch depends on the patch referenced
>> in [4], as it utilizes the newly created lib/tests/ subdirectory.
>>
>> [1] https://lkcamp.dev/about/
>> [2] https://lore.kernel.org/all/Zktnt7rjKryTh9-N@arch/
>> [3] https://elixir.bootlin.com/linux/latest/source/lib/list-test.c
>> [4] https://lore.kernel.org/all/20240720181025.work.002-kees@kernel.org/
>>
>> ---
>> Changes in v3:
>>      - Resolved checkpatch warnings:
>>          - Renamed tests for macros starting with 'for_each'
> 
> Shouldn't this a separate patch to make it easy to review?
> 
>>          - Removed link from commit message
>>      - Replaced hardcoded constants with ENTRIES_SIZE
> 
> Shouldn't this a separate patch to make it easy to review?
> 
>>      - Updated initialization of llist_node array
>>      - Fixed typos
>>      - Update Kconfig.debug message for llist_kunit
> 
> Are these changes to existing code or warnings on your added code?
>>
>> Changes in v2:
>>      - Add MODULE_DESCRIPTION()
>>      - Move the tests from lib/llist_kunit.c to lib/tests/llist_kunit.c
>>      - Change the license from "GPL v2" to "GPL"
>>
>> Artur Alves (1):
>>    lib/llist_kunit.c: add KUnit tests for llist
>>
>>   lib/Kconfig.debug       |  11 ++
>>   lib/tests/Makefile      |   1 +
>>   lib/tests/llist_kunit.c | 358 ++++++++++++++++++++++++++++++++++++++++
>>   3 files changed, 370 insertions(+)
>>   create mode 100644 lib/tests/llist_kunit.c
>>
> 
> You are combining lot of changes in one single patch. Each change as a 
> separate
> patch will help reviewers.
> 
> Adding new test should be a separate patch.
> 
> - renaming as a separate patch
> 
> thanks,
> -- Shuah

Hi, thanks for the reply!

I'm not sure if I understood your concerns ...

In this patch, I'm adding the entire test suite for the lock-less list 
data structure, which is the primary reason for its larger size. The 
changes in V2 and V3 were made in response to code review suggestions 
from previous iterations.

However, as a big patch I see how this cause an annoyance to review. I'm 
open to any suggestions on how I can reduce its size or make the review 
process more manageable.

Best regards,
- Artur

  reply	other threads:[~2024-09-19 22:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-17  0:51 [PATCH v3 0/1] Add KUnit tests for llist Artur Alves
2024-09-17  0:51 ` [PATCH v3 1/1] lib/llist_kunit.c: add " Artur Alves
2024-10-02 20:27   ` Rae Moar
2024-10-03  6:56   ` David Gow
2024-09-19 16:01 ` [PATCH v3 0/1] Add " Shuah Khan
2024-09-19 22:27   ` Artur Alves Cavalcante de Barros [this message]
2024-09-20  7:10   ` David Gow
2024-09-20 15:10     ` Shuah Khan
2024-09-21  3:07       ` Artur Alves Cavalcante de Barros
2024-09-21  2:49     ` Artur Alves Cavalcante de Barros
2024-09-23 15:48       ` Shuah Khan

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=bcd02805-5262-4d44-9528-64c63a55e8b6@gmail.com \
    --to=arturacb@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=andrealmeid@riseup.net \
    --cc=brendan.higgins@linux.dev \
    --cc=davidgow@google.com \
    --cc=diego.daniel.professional@gmail.com \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=n@nfraprado.net \
    --cc=rmoar@google.com \
    --cc=skhan@linuxfoundation.org \
    --cc=vinicius@nukelet.com \
    /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