All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH] Documentation: Add qemu instructions for OpenRISC
Date: Sun, 4 Apr 2021 20:46:04 +0200	[thread overview]
Message-ID: <bd106f14-c773-a4a8-2f43-2e269f4f04e4@pengutronix.de> (raw)
In-Reply-To: <20210304210747.3679483-1-shorne@gmail.com>

Hello Sascha,

On 04.03.21 22:07, Stafford Horne wrote:
> Most developers have qemu and rather not download and install the
> or1ksim.  Also, this adds details on how to get a openrisc toolchain.
> 
> Signed-off-by: Stafford Horne <shorne@gmail.com>

I don't see this in next.

> ---
>  Documentation/boards/openrisc.rst | 68 +++++++++++++++++++++++++++++++
>  1 file changed, 68 insertions(+)
> 
> diff --git a/Documentation/boards/openrisc.rst b/Documentation/boards/openrisc.rst
> index f9d67f965..34586b4a7 100644
> --- a/Documentation/boards/openrisc.rst
> +++ b/Documentation/boards/openrisc.rst
> @@ -1,6 +1,74 @@
>  OpenRISC
>  ========
>  
> +Optaining an OpenRISC toolchain

Could you fix up s/Optaining/Obtaining/ while at it?

Cheers,

Ahmad


-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2021-04-04 18:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-04 21:07 [OpenRISC] [PATCH] Documentation: Add qemu instructions for OpenRISC Stafford Horne
2021-04-04 18:46 ` Ahmad Fatoum [this message]
2021-04-07 23:19   ` Stafford Horne
2021-04-13  7:42 ` Sascha Hauer

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=bd106f14-c773-a4a8-2f43-2e269f4f04e4@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=openrisc@lists.librecores.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.