From: Jonathan Corbet <corbet@lwn.net>
To: Jonathan Cameron <jic23@kernel.org>,
Matti Vaittinen <mazziesaccount@gmail.com>
Cc: Jonathan Cameron <Jonathan.Cameron@Huawei.com>,
"Vaittinen, Matti" <Matti.Vaittinen@fi.rohmeurope.com>,
linux-iio <linux-iio@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-doc@vger.kernel.org
Subject: Re: ROHM ALS, integration time
Date: Tue, 31 Jan 2023 12:58:52 -0700 [thread overview]
Message-ID: <877cx24gsj.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230130201929.52c93ee5@jic23-huawei>
Jonathan Cameron <jic23@kernel.org> writes:
> Both the kernel-doc for this header and the ABI docs end up in
> the kernel html docs. I wonder if a link is possible...
> https://docs.kernel.org/driver-api/iio/core.html#industrial-i-o-devices
> would have the iio_chan_type docs I think if there were any.
> https://docs.kernel.org/admin-guide/abi-testing.html?highlight=abi#abi-sys-iio-devicex-in-intensityy-raw
> is the matching ABI doc.
>
> Mauro, Jon, other docs system experts...
>
> I couldn't immediately find a way to link to a specific ABI docs entry,
> is there a means to do it from kernel-doc in a header?
It should just be possible to write out the type or function name and
have the links generated automatically. Have you tried just putting
"enum iio_chan_type" into the text? If the automarkup code doesn't pick
it up, please let me know.
Thanks,
jon
next prev parent reply other threads:[~2023-01-31 19:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <65c7c45a-c953-e418-f640-9e46841151a1@gmail.com>
[not found] ` <20230130130231.000013b6@Huawei.com>
[not found] ` <9b3dcc7a-a0f8-38ee-4381-d330004d436f@fi.rohmeurope.com>
[not found] ` <20230130171218.00007802@Huawei.com>
[not found] ` <0e0d45b7-e582-82b2-9bac-1f70f9dad9f7@gmail.com>
2023-01-30 20:19 ` ROHM ALS, integration time Jonathan Cameron
2023-01-31 19:58 ` Jonathan Corbet [this message]
2023-02-01 5:55 ` Matti Vaittinen
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=877cx24gsj.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=Jonathan.Cameron@Huawei.com \
--cc=Matti.Vaittinen@fi.rohmeurope.com \
--cc=jic23@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=mazziesaccount@gmail.com \
--cc=mchehab@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