From: Roland Hieber <r.hieber@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [ptxdist] [PATCH 2/2] doc: user_manual: Fix typos (missing words)
Date: Fri, 5 Oct 2018 12:09:27 +0200 [thread overview]
Message-ID: <20181005100927.h5zd25nxfuss74lg@pengutronix.de> (raw)
In-Reply-To: <20181004135513.11087-2-a.fatoum@pengutronix.de>
On Thu, Oct 04, 2018 at 03:55:16PM +0200, Ahmad Fatoum wrote:
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
> doc/user_manual.inc | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/doc/user_manual.inc b/doc/user_manual.inc
> index ccae2d9a5a1a..18a87898f2da 100644
> --- a/doc/user_manual.inc
> +++ b/doc/user_manual.inc
> @@ -315,8 +315,8 @@ Selecting a Userland Configuration
>
> First of all we have to select a userland configuration. This step
> defines what kind of applications will be built for the hardware
> -platform. The comes with a predefined configuration we select in the
> -following step:
> +platform. The OSELAS.BSP-Pengutronix-Generic-2014.07.0 project comes
I guess a |ptxdistBSPName| variable expansion fits better here, it is
also used in other places in that section.
> +with a predefined configuration we select in the following step:
>
> ::
>
> @@ -328,7 +328,7 @@ Selecting a Hardware Platform
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Before we can build this BSP, we need to select one of the possible
> -platforms to build for. In this case we want to build for the :
> +platforms to build for. In this case we want to build for the Versatilepb:
Hmm, this is unfortunate, there is |ptxdistPlatformConfigDir|, but no
|ptxdistPlatformName| or the like. Would you like to add if to conf.py?
:)
- Roland
>
> ::
>
> --
> 2.19.0
>
>
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
--
Roland Hieber | r.hieber@pengutronix.de |
Pengutronix e.K. | https://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim | Phone: +49-5121-206917-5086 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2018-10-05 10:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 13:55 [ptxdist] [PATCH 1/2] doc: Fix typos Ahmad Fatoum
2018-10-04 13:55 ` [ptxdist] [PATCH 2/2] doc: user_manual: Fix typos (missing words) Ahmad Fatoum
2018-10-05 10:09 ` Roland Hieber [this message]
2018-10-09 9:15 ` Ahmad Fatoum
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=20181005100927.h5zd25nxfuss74lg@pengutronix.de \
--to=r.hieber@pengutronix.de \
--cc=a.fatoum@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