From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Rae Moar <rmoar@google.com>
Cc: linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
David Gow <davidgow@google.com>
Subject: Re: [PATCH] kunit: Fix kernel-doc for EXPORT_SYMBOL_IF_KUNIT
Date: Fri, 6 Sep 2024 22:20:57 +0200 [thread overview]
Message-ID: <a01fbbcb-abe8-4629-b3b8-19c264166b49@intel.com> (raw)
In-Reply-To: <CA+GJov4ZR6Cfms-j8v3xVSj10L1_4JptQfYt6tqZGi1s=0cyBQ@mail.gmail.com>
Hi Rae,
On 06.09.2024 21:57, Rae Moar wrote:
> On Thu, Aug 29, 2024 at 4:28 PM Michal Wajdeczko
> <michal.wajdeczko@intel.com> wrote:
>>
>>
>>
>> On 29.08.2024 20:58, Rae Moar wrote:
>>> On Thu, Aug 29, 2024 at 11:32 AM Michal Wajdeczko
>>> <michal.wajdeczko@intel.com> wrote:
>>>>
>>>> While kunit/visibility.h is today not included in any generated
>>>> kernel documentation, also likely due to the fact that none of the
>>>> existing comments are correctly recognized as kernel-doc, but once
>>>> we decide to add this header and fix the tool, there will be:
>>>>
>>>> ../include/kunit/visibility.h:61: warning: Function parameter or
>>>> struct member 'symbol' not described in 'EXPORT_SYMBOL_IF_KUNIT'
>>>>
>>>> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
>>>
>>> Hello!
>>>
>>> This looks good to me. Thanks for adding this. We will need to do a
>>> patch on making this recognized as a kernel-doc at some point.
>>
>> here it goes [1]
>>
>> [1]
>> https://lore.kernel.org/linux-doc/20240829202529.1660-1-michal.wajdeczko@intel.com/
>
> Hi Michal!
>
> Thanks for your fast response to this! It looks like this patch
> changes the kernel-doc specification,
I'm not sure it changes anything as in the spec there is just:
"The opening comment mark ``/**`` is used for kernel-doc comments."
without any mention that it has to be at the start of the line.
In fact above patch was able to detect (too) many mistakes in existing
comments that were either incomplete or false kernel-doc, but once we
fixed those, there is high chance patch will be accepted.
Michal
> which is a very worthwhile
> conversation, but in this instance I intended to change the code
> comments in visibility.h to match the current kernel-doc
> specification. I am also happy to make those edits in a future patch.
>
> Thanks!
> -Rae
>
>>
>>>
>>> Reviewed-by: Rae Moar <rmoar@google.com>
>>>
>>> Thanks!
>>> -Rae
>>>
>>>> ---
>>>> Cc: Rae Moar <rmoar@google.com>
>>>> Cc: David Gow <davidgow@google.com>
>>>> ---
>>>> include/kunit/visibility.h | 1 +
>>>> 1 file changed, 1 insertion(+)
>>>>
>>>> diff --git a/include/kunit/visibility.h b/include/kunit/visibility.h
>>>> index 0dfe35feeec6..efff77b58dd6 100644
>>>> --- a/include/kunit/visibility.h
>>>> +++ b/include/kunit/visibility.h
>>>> @@ -22,6 +22,7 @@
>>>> * EXPORTED_FOR_KUNIT_TESTING namespace only if CONFIG_KUNIT is
>>>> * enabled. Must use MODULE_IMPORT_NS(EXPORTED_FOR_KUNIT_TESTING)
>>>> * in test file in order to use symbols.
>>>> + * @symbol: the symbol identifier to export
>>>> */
>>>> #define EXPORT_SYMBOL_IF_KUNIT(symbol) EXPORT_SYMBOL_NS(symbol, \
>>>> EXPORTED_FOR_KUNIT_TESTING)
>>>> --
>>>> 2.43.0
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google Groups "KUnit Development" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send an email to kunit-dev+unsubscribe@googlegroups.com.
>>>> To view this discussion on the web visit https://groups.google.com/d/msgid/kunit-dev/20240829183150.1616-1-michal.wajdeczko%40intel.com.
next prev parent reply other threads:[~2024-09-06 20:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 18:31 [PATCH] kunit: Fix kernel-doc for EXPORT_SYMBOL_IF_KUNIT Michal Wajdeczko
2024-08-29 18:58 ` Rae Moar
2024-08-29 20:28 ` Michal Wajdeczko
2024-09-06 19:57 ` Rae Moar
2024-09-06 20:20 ` Michal Wajdeczko [this message]
2024-09-04 21:24 ` 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=a01fbbcb-abe8-4629-b3b8-19c264166b49@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=davidgow@google.com \
--cc=kunit-dev@googlegroups.com \
--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