docs.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel Wagenknecht" <dwagenknecht@emlix.com>
To: docs@lists.yoctoproject.org
Subject: [PATCH 1/2] common-tasks: add note about license implications of bundled initramfs
Date: Thu, 23 Sep 2021 10:34:11 +0200	[thread overview]
Message-ID: <20210923083412.1500103-2-dwagenknecht@emlix.com> (raw)
In-Reply-To: <20210923083412.1500103-1-dwagenknecht@emlix.com>

Ensure users are aware that usage of INITRAMFS_IMAGE_BUNDLE is only
appropiate for use with GPLv2 compatible software.

Signed-off-by: Daniel Wagenknecht <dwagenknecht@emlix.com>
---
 documentation/dev-manual/common-tasks.rst | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/documentation/dev-manual/common-tasks.rst b/documentation/dev-manual/common-tasks.rst
index bd8bbecb3..b81f51bf8 100644
--- a/documentation/dev-manual/common-tasks.rst
+++ b/documentation/dev-manual/common-tasks.rst
@@ -3886,6 +3886,12 @@ Follow these steps to create an initramfs image:
    variable, allowing the initramfs image to be built into the kernel
    normally.
 
+   .. note::
+
+      Bundling the initramfs with the kernel conflates the code in the initramfs
+      with the GPLv2 licensed Linux kernel binary. Thus only GPLv2 compatible
+      software may be part of a bundled initramfs.
+
    .. note::
 
       If you choose to not bundle the initramfs image with the kernel
-- 
2.25.1


  reply	other threads:[~2021-09-23  8:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-23  8:34 [PATCH 0/2] add notes about license implications of bundled initramfs Daniel Wagenknecht
2021-09-23  8:34 ` Daniel Wagenknecht [this message]
2021-09-23  8:34 ` [PATCH 2/2] ref-manual: add note " Daniel Wagenknecht
2021-10-01 17:29 ` [docs] [PATCH 0/2] add notes " Michael Opdenacker

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=20210923083412.1500103-2-dwagenknecht@emlix.com \
    --to=dwagenknecht@emlix.com \
    --cc=docs@lists.yoctoproject.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;
as well as URLs for NNTP newsgroup(s).