All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: Ann Yun <by.ann.yun@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 v2] Documentation:openrisc: Add build instructions with initramfs
Date: Sat, 26 Apr 2025 17:16:47 +0100	[thread overview]
Message-ID: <aA0G74KvymHRU44-@antec> (raw)
In-Reply-To: <20250426154544.15351-1-by.ann.yun@gmail.com>

On Sat, Apr 26, 2025 at 11:45:44AM -0400, Ann Yun wrote:
> Mention how to include initramfs when building the kernel and
> direct the reader to ramfs-rootfs-initramfs.rst documentation for more
> details
> 
> Signed-off-by: Ann Yun <by.ann.yun@gmail.com>
> ---
> V1 -> V2: Mention Documentation/filesystems/ramfs-rootfs-initramfs.rst
> 
>  Documentation/arch/openrisc/openrisc_port.rst | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/Documentation/arch/openrisc/openrisc_port.rst b/Documentation/arch/openrisc/openrisc_port.rst
> index a8f307a3b499..69aed4069e3b 100644
> --- a/Documentation/arch/openrisc/openrisc_port.rst
> +++ b/Documentation/arch/openrisc/openrisc_port.rst
> @@ -40,6 +40,12 @@ Build the Linux kernel as usual::
>  	make ARCH=openrisc CROSS_COMPILE="or1k-linux-" defconfig
>  	make ARCH=openrisc CROSS_COMPILE="or1k-linux-"
>  
> +If you want to embed initramfs in the kernel, also pass ``CONFIG_INITRAMFS_SOURCE``. For example::
> +
> +	make ARCH=openrisc CROSS_COMPILE="or1k-linux-" CONFIG_INITRAMFS_SOURCE="path/to/rootfs path/to/devnodes"
> +
> +For more information on this, please check Documentation/filesystems/ramfs-rootfs-initramfs.rst. 

This is one trailing whitespace on the above line.  Can it be removed

-Stafford

>  3) Running on FPGA (optional)
>  
>  The OpenRISC community typically uses FuseSoC to manage building and programming
> -- 
> 2.37.2
> 

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-26 15:45 [PATCH v2] Documentation:openrisc: Add build instructions with initramfs Ann Yun
2025-04-26 16:16 ` Stafford Horne [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=aA0G74KvymHRU44-@antec \
    --to=shorne@gmail.com \
    --cc=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=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 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.