From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Bastian Krause <bst@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] doc: dev_layers_in_ptxdist: drop extra "`"
Date: Fri, 28 May 2021 09:01:21 +0200 [thread overview]
Message-ID: <20210528070121.794981-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20210525160822.6416-1-bst@pengutronix.de>
Thanks, applied as e6d3ee8b98d5602ba9d7e7a1267bca45a5dfa24a.
Michael
[sent from post-receive hook]
On Fri, 28 May 2021 09:01:20 +0200, Bastian Krause <bst@pengutronix.de> wrote:
> The RST custom link text syntax is
>
> :ref:`custom text<Heading Text>`
>
> Signed-off-by: Bastian Krause <bst@pengutronix.de>
> Message-Id: <20210525160822.6416-1-bst@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/doc/dev_layers_in_ptxdist.rst b/doc/dev_layers_in_ptxdist.rst
> index a1066396ca28..27ca85832e93 100644
> --- a/doc/dev_layers_in_ptxdist.rst
> +++ b/doc/dev_layers_in_ptxdist.rst
> @@ -29,7 +29,7 @@ are used. Any layer specific handling is done implicitly by PTXdist.
> However, there are a few things that need special handling.
>
> The variables :ref:`PTXDIST_WORKSPACE<ptxdist_workspace>` and
> -:ref:`PTXDIST_PLATFORMCONFIGDIR`<ptxdist_platformconfigdir>` always refer
> +:ref:`PTXDIST_PLATFORMCONFIGDIR<ptxdist_platformconfigdir>` always refer
> to the directories in the top layer. These variables might be used in rules
> files like this:
>
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
prev parent reply other threads:[~2021-05-28 7:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 16:08 [ptxdist] [PATCH] " Bastian Krause
2021-05-25 20:37 ` Roland Hieber
2021-05-28 7:01 ` Michael Olbrich [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=20210528070121.794981-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=bst@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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