public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: Marcus Folkesson <marcus.folkesson@gmail.com>
To: Quentin Schulz <quentin.schulz@cherry.de>
Cc: openembedded-core@lists.openembedded.org, docs@lists.yoctoproject.org
Subject: Re: [OE-core] [PATCH 2/2] ref-manual: classes: add new image-bootfiles class
Date: Thu, 23 May 2024 15:56:33 +0200	[thread overview]
Message-ID: <Zk9LEdzTFcU22mH6@gmail.com> (raw)
In-Reply-To: <76a18407-d650-47a2-b8c8-f639350c3630@cherry.de>

Hi Quentin,

On Thu, May 23, 2024 at 03:33:00PM +0200, Quentin Schulz wrote:
> Hi Markus,
> 
> On 5/21/24 7:33 PM, Marcus Folkesson via lists.openembedded.org wrote:
> > [You don't often get email from marcus.folkesson=gmail.com@lists.openembedded.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
> > 
> > Describe the newly introduced image-bootfiles class.
> > 
> > Signed-off-by: Marcus Folkesson <marcus.folkesson@gmail.com>
> > ---
> >   documentation/ref-manual/classes.rst | 14 ++++++++++++++
> >   1 file changed, 14 insertions(+)
> > 
> > diff --git a/documentation/ref-manual/classes.rst b/documentation/ref-manual/classes.rst
> > index 9520d0bf7c..53b3697bee 100644
> > --- a/documentation/ref-manual/classes.rst
> > +++ b/documentation/ref-manual/classes.rst
> > @@ -1169,6 +1169,20 @@ Yocto Project Overview and Concepts Manual.
> > 
> >   .. _ref-classes-image-buildinfo:
> > 
> 
> This isn't the appropriate name for the reflink, we should ave
> 
> .. _ref-classes-image-bootfiles:
> 
> instead, to match the actual name of the class.
> 
> > +``image-bootfiles``
> > +===================
> > +
> > +The :ref:`ref-classes-image-buildinfo` class copies over files listed
> 
> That's not the appropriate name, it should be ref-classes-image-bootfiles
> (it currently renders properly because the reflink is incorrect).
> 
> > +in :ref:`IMAGE_BOOT_FILES` to the /boot directory of the root filesystem.
> > +
> 
> Tick quote /boot:
> `/boot`
> it;'s not meant to be understood as an English word.
> 
> > +This can be useful if no separate boot partition is used but all boot files
> 
> Replace "all" with "some", it depends on the content of IMAGE_BOOT_FILES, so
> we cannot say "all" here, it is misleading.
> 
> > +should be included into the rootfs image.
> > +
> > +:ref:`IMAGE_BOOT_FILES` is the same space-separated list of files used
> > +by the ``bootimg-partition`` source plugin to populate the boot partition.
> > +
> 
> I would not mention this here, rather edit the variables glossary entry for
> IMAGE_BOOT_FILES to mention that this is also used by image-bootfiles.
> Also, it seems bootimg-efi plugin uses it, according to the glossary entry.
> 
> > +.. _ref-classes-image_types:
> 
> This isn't the appropriate name for the reflink, we should have
> 
> .. _ref-classes-image-buildinfo:
> 
> instead.
> 
> Cheers,
> Quentin

Thank you for all the comments, I agree with them all and will update
the patch accordingly.

FYI, I will drop the documentation patch from this series and resend it
once the class is ready for merging.
It was suggested by the doc mailing list (had to resend it as I was not
subscribed, so it is not part of this thread).


Best regards,
Marcus Folkesson



      reply	other threads:[~2024-05-23 13:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240521173343.2954628-1-marcus.folkesson@gmail.com>
2024-05-23 13:26 ` [OE-core] [PATCH 1/2] image-bootfiles.bbclass: new class, copy boot files to /boot on rfs Quentin Schulz
2024-05-23 13:38   ` [docs] " Alexander Kanavin
2024-05-23 13:48     ` Quentin Schulz
2024-05-23 13:49   ` Marcus Folkesson
2024-05-23 13:56     ` Quentin Schulz
     [not found] ` <20240521173343.2954628-2-marcus.folkesson@gmail.com>
2024-05-23 13:33   ` [OE-core] [PATCH 2/2] ref-manual: classes: add new image-bootfiles class Quentin Schulz
2024-05-23 13:56     ` Marcus Folkesson [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=Zk9LEdzTFcU22mH6@gmail.com \
    --to=marcus.folkesson@gmail.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=quentin.schulz@cherry.de \
    /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