From: Randy Dunlap <rdunlap@infradead.org>
To: Jonathan Corbet <corbet@lwn.net>, Jakub Kicinski <kuba@kernel.org>
Cc: linux-doc@vger.kernel.org, arkadiusz.kubalewski@intel.com,
netdev@vger.kernel.org
Subject: Re: [PATCH docs] scripts: kernel-doc: support private / public marking for enums
Date: Sat, 15 Jul 2023 17:35:30 -0700 [thread overview]
Message-ID: <5e5ee5f1-6391-dea3-77eb-c55dd7bff0a3@infradead.org> (raw)
In-Reply-To: <f5c04cf1-c6ca-70d6-1903-4603acc30df4@infradead.org>
On 7/14/23 08:15, Randy Dunlap wrote:
>
>
> On 7/14/23 06:29, Jonathan Corbet wrote:
>> Randy Dunlap <rdunlap@infradead.org> writes:
>>
>>> Hi Jon,
>>>
>>> On 6/21/23 20:10, Randy Dunlap wrote:
>>>>
>>>>
>>>> On 6/21/23 15:35, Jakub Kicinski wrote:
>>>>> Enums benefit from private markings, too. For netlink attribute
>>>>> name enums always end with a pair of __$n_MAX and $n_MAX members.
>>>>> Documenting them feels a bit tedious.
>>>>>
>>>>> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
>>>>
>>>> Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
>>>> Tested-by: Randy Dunlap <rdunlap@infradead.org>
>>>>
>>>> Thanks.
>>>
>>> I have a need for this patch. Are you planning to merge it?
>>
>> It's commit e27cb89a22ad in 6.5-rc1 ...
>
> Oops, my bad, sorry about that.
>
> I'm testing with linux-next. Something is rotten here /methinks.
>
> I will check it out.
Apparently this was due to user error -- it works today.
Sorry about the noise.
next prev parent reply other threads:[~2023-07-16 0:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 22:35 [PATCH docs] scripts: kernel-doc: support private / public marking for enums Jakub Kicinski
2023-06-22 3:10 ` Randy Dunlap
2023-07-14 5:03 ` Randy Dunlap
2023-07-14 13:29 ` Jonathan Corbet
2023-07-14 15:15 ` Randy Dunlap
2023-07-16 0:35 ` Randy Dunlap [this message]
2023-07-03 16:48 ` Jonathan Corbet
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=5e5ee5f1-6391-dea3-77eb-c55dd7bff0a3@infradead.org \
--to=rdunlap@infradead.org \
--cc=arkadiusz.kubalewski@intel.com \
--cc=corbet@lwn.net \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).