Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Ivan Orlov <ivan.orlov0322@gmail.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
Subject: Re: [PATCH 1/5] kunit: string-stream: export non-static functions
Date: Sun, 9 Jun 2024 20:01:26 +0100	[thread overview]
Message-ID: <655c6a80-53d0-4a9c-b242-25936646e49c@gmail.com> (raw)
In-Reply-To: <CABVgOSnNLmmMDHin=mvrAmN3m6mJmWsntcc_JvV03pCzXUEX+w@mail.gmail.com>

On 6/8/24 10:20, David Gow wrote:
> On Tue, 4 Jun 2024 at 20:32, Ivan Orlov <ivan.orlov0322@gmail.com> wrote:
>>
>> Export non-static functions from the string-stream.c file into the KUnit
>> namespace in order to be able to access them from the KUnit core tests
>> (when they are loaded as modules).
>>
>> Signed-off-by: Ivan Orlov <ivan.orlov0322@gmail.com>
>> ---
> 
> Looks good to me, thanks.
> 
> It's very slightly hilarious to use EXPORT_SYMBOL_IF_KUNIT() here,
> because _of course_ KUnit is enabled, but I think it's the right idea
> nevertheless.
> 
> Reviewed-by: David Gow <davidgow@google.com>

Hi David,

Thank you for the review.

Yes, the name of the EXPORT_SYMBOL_IF_KUNIT macro in this case is a bit 
confusing... It is used not only to export the symbol conditionally (if 
CONFIG_KUNIT is enabled), but also to export the symbol into the KUnit 
namespace (so I used it as a shortcut for this action here) :)

-- 
Kind regards,
Ivan Orlov


  reply	other threads:[~2024-06-09 19:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04 12:31 [PATCH 0/5] Reorganize string-stream and assert tests Ivan Orlov
2024-06-04 12:32 ` [PATCH 1/5] kunit: string-stream: export non-static functions Ivan Orlov
2024-06-08  9:20   ` David Gow
2024-06-09 19:01     ` Ivan Orlov [this message]
2024-06-04 12:32 ` [PATCH 2/5] kunit: kunit-test: Remove stub for log tests Ivan Orlov
2024-06-08  9:20   ` David Gow
2024-06-04 12:32 ` [PATCH 3/5] kunit: string-stream-test: Make it a separate module Ivan Orlov
2024-06-08  9:20   ` David Gow
2024-06-04 12:32 ` [PATCH 4/5] kunit: assert: export non-static functions Ivan Orlov
2024-06-08  9:20   ` David Gow
2024-06-09 19:05     ` Ivan Orlov
2024-06-04 12:32 ` [PATCH 5/5] kunit: Merge assertion test into kunit-test.c Ivan Orlov
2024-06-08  9:20   ` David Gow
2024-06-11 13:10     ` Ivan Orlov

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=655c6a80-53d0-4a9c-b242-25936646e49c@gmail.com \
    --to=ivan.orlov0322@gmail.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=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