mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Aleksander Morgado <aleksander@aleksander.es>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] Documentation: remote-control: fix typo
Date: Thu, 1 Jun 2017 09:30:43 +0200	[thread overview]
Message-ID: <20170601073043.3r6cbj3ib3sjv72o@pengutronix.de> (raw)
In-Reply-To: <20170530214634.6768-1-aleksander@aleksander.es>

On Tue, May 30, 2017 at 11:46:34PM +0200, Aleksander Morgado wrote:
> Correctly reference `--port` instead of	`--baudrate` when explaining
> how to specify the port.
> 
> Signed-off-by: Aleksander Morgado <aleksander@aleksander.es>
> ---
>  Documentation/user/remote-control.rst | 7 +++----
>  1 file changed, 3 insertions(+), 4 deletions(-)

Applied, thanks

Sascha

> 
> diff --git a/Documentation/user/remote-control.rst b/Documentation/user/remote-control.rst
> index 99c2181df..217251429 100644
> --- a/Documentation/user/remote-control.rst
> +++ b/Documentation/user/remote-control.rst
> @@ -53,9 +53,9 @@ configuring bbremote
>  ^^^^^^^^^^^^^^^^^^^^
>  
>  bbremote needs the port and possibly the baudrate to access the remote
> -barebox. The port can be configured with the ``--baudrate`` option or
> -with the ``BBREMOTE_PORT`` environment variable. The port can either be
> -the device special file if it's a local port or if it's a remote port a
> +barebox. The port can be configured with the ``--port`` option or with
> +the ``BBREMOTE_PORT`` environment variable. The port can either be the
> +device special file if it's a local port or if it's a remote port a
>  string of the form: ``rfc2217://host:port``. The baudrate can be given
>  with the ``--baudrate`` option or the ``BBREMOTE_BAUDRATE`` environment
>  variable. For the rest of this document it is assumed that ``bbremote``
> @@ -131,4 +131,3 @@ This can be mounted on barebox using the regular mount command using
>    bbremote --export=somedir console
>    mkdir -p /ratpfs; mount -t ratpfs none /ratpfs
>    ls /ratpfs
> -
> -- 
> 2.12.2
> 
> 

-- 
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:[~2017-06-01  7:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-30 21:46 Aleksander Morgado
2017-06-01  7:30 ` Sascha Hauer [this message]
2017-06-01 12:26   ` Aleksander Morgado
2017-06-01 12:31     ` Sascha Hauer
2017-06-01 17:40       ` Aleksander Morgado

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=20170601073043.3r6cbj3ib3sjv72o@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=aleksander@aleksander.es \
    --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