mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] Documentation: imd: fix sphinx warning
Date: Wed, 21 Sep 2016 10:12:42 +0200	[thread overview]
Message-ID: <20160921081242.j7rtr4yu6ofjnjgf@pengutronix.de> (raw)
In-Reply-To: <20160920141301.10187-1-antonynpavlov@gmail.com>

On Tue, Sep 20, 2016 at 05:13:01PM +0300, Antony Pavlov wrote:
> The patch fixes this sphinx warnings:
> 
>     barebox/Documentation/user/imd.rst:27: WARNING: Could not lex literal_block as "c". Highlighting skipped.
> 
> Signed-off-by: Antony Pavlov <antonynpavlov@gmail.com>
> Cc: Sascha Hauer <s.hauer@pengutronix.de>
> ---
>  Documentation/user/imd.rst | 8 ++++++--
>  1 file changed, 6 insertions(+), 2 deletions(-)

Applied, thanks

Sascha

> 
> diff --git a/Documentation/user/imd.rst b/Documentation/user/imd.rst
> index e0251d6..ce1b90c 100644
> --- a/Documentation/user/imd.rst
> +++ b/Documentation/user/imd.rst
> @@ -22,7 +22,9 @@ The informations can be extracted with the ``bareboximd`` tool which lives under
>  ``scripts/`` in the barebox sourcecode. If enabled it is compiled for the compile
>  host and also for the target architecture. barebox itself has the :ref:`command_imd`
>  command to extract the informations. Here is an example output of the tool called
> -without additional options::
> +without additional options:
> +
> +.. code-block:: none
>  
>    # imd barebox-phytec-pbab01dl-1gib.img
>    build: #890 Wed Jul 30 16:15:24 CEST 2014
> @@ -31,7 +33,9 @@ without additional options::
>    of_compatible: phytec,imx6x-pbab01 phytec,imx6dl-pfla02 fsl,imx6dl
>    model: Phytec phyFLEX-i.MX6 Duallite Carrier-Board
>  
> -Single informations can be extracted with the ``-t <type>`` option::
> +Single informations can be extracted with the ``-t <type>`` option:
> +
> +.. code-block:: none
>  
>    # imd barebox-phytec-pbab01dl-1gib.img -t release
>    2014.07.0-00167-ge6632a9-dirty
> -- 
> 2.9.3
> 
> 

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2016-09-21  8:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-20 14:13 Antony Pavlov
2016-09-21  8:12 ` Sascha Hauer [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=20160921081242.j7rtr4yu6ofjnjgf@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=antonynpavlov@gmail.com \
    --cc=barebox@lists.infradead.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