All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Akira Yokosawa <akiyks@gmail.com>,
	Greg KH <gregkh@linuxfoundation.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH] scripts/kernel-doc: Get -export option working again
Date: Tue, 10 Dec 2024 17:29:16 -0700	[thread overview]
Message-ID: <87v7vr12qr.fsf@trenco.lwn.net> (raw)
In-Reply-To: <b7c99226-7c03-425a-91b6-c7969bdbb1cf@gmail.com>

Akira Yokosawa <akiyks@gmail.com> writes:

> Jonathan Corbet wrote:
> [...]
>> Ah ... I should have thought of that ... I'm glad you did.  I've just
>> pushed the fix out to linux-next, will send it Linusward in the near
>> future.  Thanks for fixing this,
>
> Your docs-fixes is based on v6.13-rc1.
> This fix needs to come after v6.13-rc2.

...which will happen once the fix hits mainline - the *fix* doesn't
depend on -rc2.

> On current docs-next,
>
>     ./script/kernel-doc -rst -export drivers/iommu/iommufd/device.c
>
> returns:
>
>     drivers/iommu/iommufd/device.c:1: warning: no structured comments found
>
> I guess restarting everything from v6.13-rc2 would make our life much easier
> for v6.14.

I suppose I can rebase docs-next forward (or back-merge) if there's a
real need to do so... I'm not sure how important that is to get rid of a
few warnings?

Thanks,

jon

  reply	other threads:[~2024-12-11  0:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-10 11:04 [PATCH] scripts/kernel-doc: Get -export option working again Akira Yokosawa
2024-12-10 18:12 ` Randy Dunlap
2024-12-10 18:53 ` Matthew Wilcox
2024-12-10 20:58 ` Jonathan Corbet
2024-12-11  0:15   ` Akira Yokosawa
2024-12-11  0:29     ` Jonathan Corbet [this message]
2024-12-11 15:23       ` Akira Yokosawa
2024-12-11 16:25         ` 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=87v7vr12qr.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=akiyks@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.