[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87wm1ho3cs.fsf@trenco.lwn.net>
Date: Fri, 16 Jan 2026 10:48:51 -0700
From: Jonathan Corbet <corbet@....net>
To: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
Cc: Randy Dunlap <rdunlap@...radead.org>, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, Akira Yokosawa <akiyks@...il.com>, Shuah
Khan <shuah@...nel.org>, Jani Nikula <jani.nikula@...ux.intel.com>
Subject: Re: [PATCH 0/2] Move kernel-doc to tools/docs
Mauro Carvalho Chehab <mchehab+huawei@...nel.org> writes:
> Em Wed, 14 Jan 2026 12:24:31 -0700
> Jonathan Corbet <corbet@....net> escreveu:
>
>> Randy Dunlap <rdunlap@...radead.org> writes:
>>
>> > I do many of these on a regular basis:
>> >
>> > $ ./scripts/kernel-doc -none -Wall <path_to_source_file>
>> >
>> > Will I still be able to do that (by using ./tools/doc/kernel-doc ...)?
>>
>> Yes. The tool moves, but its functionality remains unchanged.
>
> That's actually a good point: should we preserve a link on scripts
> pointing to ../tools/doc/kernel-doc? I suspect that a change like
> that could break some machinery on several CI tools and scripts
> out there. If so, it could be useful to keep a link - at least for
> a couple of kernel releases.
So is the location of kernel-doc part of our ABI, or an internal detail?
:)
I'm not deeply opposed to maintaining the symlink, though I'd rather
not. It won't be for "a couple of releases", though; if the symlink is
there, nothing will ever change.
Thanks,
jon
Powered by blists - more mailing lists