public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: David Gow <davidgow@google.com>
Cc: <brendan.higgins@linux.dev>, <rmoar@google.com>,
	<linux-kselftest@vger.kernel.org>, <kunit-dev@googlegroups.com>,
	<linux-kernel@vger.kernel.org>, <patches@opensource.cirrus.com>
Subject: Re: [PATCH v5 02/10] kunit: string-stream: Improve testing of string_stream
Date: Fri, 25 Aug 2023 10:32:28 +0100	[thread overview]
Message-ID: <b37dfc5c-8cd6-8d99-e0ec-6f0e5a30d68e@opensource.cirrus.com> (raw)
In-Reply-To: <CABVgOSn4H7HAbn2ZR0KFBwLT6GfBteaGVJa8KT8Q4fjhM7nUQw@mail.gmail.com>

On 25/08/2023 07:49, David Gow wrote:
> On Thu, 24 Aug 2023 at 22:33, Richard Fitzgerald
> <rf@opensource.cirrus.com> wrote:
>>
>> Replace the minimal tests with more-thorough testing.
>>
>> string_stream_init_test() tests that struct string_stream is
>> initialized correctly.
>>
>> string_stream_line_add_test() adds a series of numbered lines and
>> checks that the resulting string contains all the lines.
>>
>> string_stream_variable_length_line_test() adds a large number of
>> lines of varying length to create many fragments, then tests that all
>> lines are present.
>>
>> string_stream_append_test() tests various cases of using
>> string_stream_append() to append the content of one stream to another.
>>
>> Adds string_stream_append_empty_string_test() to test that adding an
>> empty string to a string_stream doesn't create a new empty fragment.
>>
>> Signed-off-by: Richard Fitzgerald <rf@opensource.cirrus.com>
>> ---
>> Changes since V4:
>> - Test cases for appending empty strings have been squashed into this
>>    patch.
>> - Call to string_stream_get_string() is wrapped in a local function
>>    get_concatenated_string(). This is to avoid a lot of code churn later
>>    when string_stream_get_string() is changed to return an unmanaged buffer.
>> ---
> 
> This looks good to me. I'm not 100% sold on the
> 'get_concatenated_string()' function long-term (despite its obvious
> benefits during the refactoring), but that's just personal taste. This
> version is fine regardless.
> 

Yes, we can remove it later. I just wanted to avoid having one enormous
patch that changes everything all over the place.


  reply	other threads:[~2023-08-25  9:33 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-24 14:31 [PATCH v5 00/10] kunit: Add dynamically-extending log Richard Fitzgerald
2023-08-24 14:31 ` [PATCH v5 01/10] kunit: string-stream: Don't create a fragment for empty strings Richard Fitzgerald
2023-08-24 22:42   ` Rae Moar
2023-08-25  6:49   ` David Gow
2023-08-24 14:31 ` [PATCH v5 02/10] kunit: string-stream: Improve testing of string_stream Richard Fitzgerald
2023-08-24 22:42   ` Rae Moar
2023-08-25 14:58     ` Richard Fitzgerald
2023-08-25  6:49   ` David Gow
2023-08-25  9:32     ` Richard Fitzgerald [this message]
2023-08-24 14:31 ` [PATCH v5 03/10] kunit: string-stream: Add option to make all lines end with newline Richard Fitzgerald
2023-08-24 23:13   ` Rae Moar
2023-08-25  6:49   ` David Gow
2023-08-24 14:31 ` [PATCH v5 04/10] kunit: string-stream: Add cases for string_stream newline appending Richard Fitzgerald
2023-08-24 23:22   ` Rae Moar
2023-08-25  6:49   ` David Gow
2023-08-24 14:31 ` [PATCH v5 05/10] kunit: Don't use a managed alloc in is_literal() Richard Fitzgerald
2023-08-25  6:49   ` David Gow
2023-08-24 14:31 ` [PATCH v5 06/10] kunit: string-stream: Add kunit_alloc_string_stream() Richard Fitzgerald
2023-08-25  6:49   ` David Gow
2023-08-24 14:31 ` [PATCH v5 07/10] kunit: string-stream: Decouple string_stream from kunit Richard Fitzgerald
2023-08-25  6:17   ` kernel test robot
2023-08-25  6:49   ` David Gow
2023-08-24 14:31 ` [PATCH v5 08/10] kunit: string-stream: Add tests for freeing resource-managed string_stream Richard Fitzgerald
2023-08-25  6:49   ` David Gow
2023-08-25  9:41     ` Richard Fitzgerald
2023-08-24 14:31 ` [PATCH v5 09/10] kunit: Use string_stream for test log Richard Fitzgerald
2023-08-25  6:17   ` kernel test robot
2023-08-25  6:53   ` David Gow
2023-08-25  7:30   ` kernel test robot
2023-08-24 14:31 ` [PATCH v5 10/10] kunit: string-stream: Test performance of string_stream Richard Fitzgerald
2023-08-25  6:50   ` David Gow
2023-08-25  6:58 ` [PATCH v5 00/10] kunit: Add dynamically-extending log David Gow

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=b37dfc5c-8cd6-8d99-e0ec-6f0e5a30d68e@opensource.cirrus.com \
    --to=rf@opensource.cirrus.com \
    --cc=brendan.higgins@linux.dev \
    --cc=davidgow@google.com \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=rmoar@google.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