linux-openrisc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ann Yun <by.ann.yun@gmail.com>
To: Stafford Horne <shorne@gmail.com>
Cc: jonas@southpole.se, stefan.kristiansson@saunalahti.fi,
	corbet@lwn.net,  linux-openrisc@vger.kernel.org,
	linux-doc@vger.kernel.org,  linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation:openrisc: Add build instructions with initramfs
Date: Sat, 26 Apr 2025 09:58:28 -0400	[thread overview]
Message-ID: <CAB60mtNRLstmV7c97=tUnW9GhMkn809eKHcGnA4x1iGcpGjYLQ@mail.gmail.com> (raw)
In-Reply-To: <aAyeY-cFSDuLYnJZ@antec>

Hi Stafford,

I am sending my same reply to the whole group again, because I
previously did not do "Reply All".

On Sat, Apr 26, 2025 at 4:50 AM Stafford Horne <shorne@gmail.com> wrote:
>
> I think this is good, but maybe we can mention to refer to Documentation/filesystems/ramfs-rootfs-initramfs.rst
> for more details on this?

Thanks for pointing that out. That is an excellent idea, I will add that.

> Also, it may be helpful to mention we can get pre-built busybox rootfs images
> here:
>
>   https://github.com/stffrdhrn/or1k-rootfs-build/releases
>
> But if we do that then it would be better to show how to use thos rootfs images,
> which maybe something better we have in our openrisc/tutorials[0].
>
> -Stafford
>
> [0] https://github.com/openrisc/tutorials

Exactly! I was working on a QEMU tutorial inside openrisc/tutorials
and that prompted me to add that one line here.

Ann

      reply	other threads:[~2025-04-26 13:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-25 20:10 [PATCH] Documentation:openrisc: Add build instructions with initramfs Ann Yun
2025-04-26  8:50 ` Stafford Horne
2025-04-26 13:58   ` Ann Yun [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='CAB60mtNRLstmV7c97=tUnW9GhMkn809eKHcGnA4x1iGcpGjYLQ@mail.gmail.com' \
    --to=by.ann.yun@gmail.com \
    --cc=corbet@lwn.net \
    --cc=jonas@southpole.se \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-openrisc@vger.kernel.org \
    --cc=shorne@gmail.com \
    --cc=stefan.kristiansson@saunalahti.fi \
    /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;
as well as URLs for NNTP newsgroup(s).