From: Dean Marx <dmarx@iol.unh.edu>
To: Paul Szczepanek <paul.szczepanek@arm.com>
Cc: dev@dpdk.org, probb@iol.unh.edu
Subject: Re: [PATCH v2] dts: fix doxygen API link and DTS docs placement
Date: Mon, 28 Oct 2024 14:56:34 -0400 [thread overview]
Message-ID: <CABD7UXMvedMXaCtVvGpWNsfv2JAGHPxSHngZshP7oiYcyOBQJw@mail.gmail.com> (raw)
In-Reply-To: <20241025103520.394951-1-paul.szczepanek@arm.com>
[-- Attachment #1: Type: text/plain, Size: 882 bytes --]
On Fri, Oct 25, 2024 at 6:35 AM Paul Szczepanek <paul.szczepanek@arm.com>
wrote:
> Alias used to produce the link to the DTS API docs uses config data.
> The required value in config data was being added in the wrong scope.
> This moves the key addition to where the config data object is created.
>
> DTS docs need to be placed in the same dir as main API docs.
> Made DTS docs dependent on main docs and stopped separate install step
> relying instead on the parent docs to install them.
> This means they can no longer be build without main docs.
>
> Added a line to sphinx python wrapper to create the destination path
> if not already present.
>
> Fixes: 7f9326423a04 ("dts: add API doc generation")
>
> Signed-off-by: Paul Szczepanek <paul.szczepanek@arm.com>
> Acked-by: Patrick Robb <probb@iol.unh.edu>
>
Reviewed-by: Dean Marx <dmarx@iol.unh.edu>
[-- Attachment #2: Type: text/html, Size: 1379 bytes --]
prev parent reply other threads:[~2024-10-28 18:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 14:57 [PATCH] dts: fix doxygen API link Paul Szczepanek
2024-10-23 15:00 ` Luca Vizzarro
2024-10-23 15:07 ` David Marchand
2024-10-23 15:10 ` Patrick Robb
2024-10-23 15:30 ` David Marchand
2024-10-24 9:12 ` David Marchand
2024-10-24 17:45 ` Paul Szczepanek
2024-10-25 10:35 ` [PATCH v2] dts: fix doxygen API link and DTS docs placement Paul Szczepanek
2024-10-28 18:56 ` Dean Marx [this message]
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=CABD7UXMvedMXaCtVvGpWNsfv2JAGHPxSHngZshP7oiYcyOBQJw@mail.gmail.com \
--to=dmarx@iol.unh.edu \
--cc=dev@dpdk.org \
--cc=paul.szczepanek@arm.com \
--cc=probb@iol.unh.edu \
/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).