From: "Paul Eggleton" <bluelightning@bluelightning.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH 09/13] ref-manual: add FIT_KERNEL_COMP_ALG*
Date: Thu, 15 Apr 2021 22:07:36 +1200 [thread overview]
Message-ID: <6250809.G0QQBjFxQf@linc> (raw)
In-Reply-To: <799bb8cf-ca33-325f-b717-f68db0b7a1ed@crashcourse.ca>
Hi Robert
On Wednesday, 14 April 2021 20:35:19 NZST Robert P. J. Day wrote:
> On Wed, 14 Apr 2021, Quentin Schulz wrote:
> > On Tue, Apr 13, 2021 at 05:19:50PM -0700, Paul Eggleton wrote:
> > > --- a/documentation/ref-manual/variables.rst
> > > +++ b/documentation/ref-manual/variables.rst
> > > @@ -2580,6 +2580,17 @@ system and gives an overview of their function
> > > and contents.> >
> > > :term:`FIT_HASH_ALG`
> > > :
> > > Specifies the hash algorithm used in creating the FIT Image. For
> > > e.g. sha256.> >
> > > + :term:`FIT_KERNEL_COMP_ALG`
> > > + Compression algorithm to use for the kernel image inside the
> > > fitImage. + At present, the only supported values are "gzip"
> > > (default) or "none", + which allows disabling of compression if it
> > > would otherwise be enabled.>
> > I'm not a native speaker and I'm struggling to understand that last line,
> > would it be possible for you to rephrase please?
>
> i would just drop the second half of that second sentence -- the
> first part says all that needs to be said:
>
> Compression algorithm to use for the kernel image inside the
> fitImage; at present, the only supported values are "gzip" (default)
> or "none".
Sounds reasonable, I've done exactly this. I also adjusted the text to remove
mention of setting FIT_KERNEL_COMP_ALG_EXTENSION if FIT_KERNEL_COMP_ALG is
set to "none" (upon closer inspection that isn't necessary based on how the
code behaves).
> i would pick nits with the varieties of the phrase "fitImage";
> regardless of how it's used as a variable, i believe the proper
> reference is "FIT image", which is how it should appear in the above,
> methinks.
Yep I fixed this as well. We're not consistent with this in the existing text,
I haven't fixed that so we probably should in future.
Thanks,
Paul
next prev parent reply other threads:[~2021-04-15 10:07 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 0:19 [PATCH 00/13] Documentation updates for 3.3 Paul Eggleton
2021-04-14 0:19 ` [PATCH 01/13] ref-manual: add METADATA_REVISION and METADATA_BRANCH Paul Eggleton
2021-04-14 7:59 ` [docs] " Quentin Schulz
2021-04-14 0:19 ` [PATCH 02/13] Use variables for minimum host versions and bump Python to 3.6 Paul Eggleton
2021-04-14 0:19 ` [PATCH 03/13] ref-manual: update/fix text for SDK_VERSION Paul Eggleton
2021-04-14 0:19 ` [PATCH 04/13] overview-manual: fix git command line Paul Eggleton
2021-04-14 0:19 ` [PATCH 05/13] ref-manual: and SDK_CUSTOM_TEMPLATECONF to glossary Paul Eggleton
2021-04-14 8:03 ` [docs] " Quentin Schulz
2021-04-14 0:19 ` [PATCH 06/13] ref-manual: add REQUIRED_VERSION and adjust PREFERRED_VERSION entry Paul Eggleton
2021-04-14 8:10 ` [docs] " Quentin Schulz
2021-04-14 8:17 ` Nicolas Dechesne
2021-04-14 0:19 ` [PATCH 07/13] ref-manual: add python3targetconfig class and remove python 2 references Paul Eggleton
2021-04-14 0:19 ` [PATCH 08/13] ref-manual: add passwd-expire to EXTRA_USERS_PARAMS Paul Eggleton
2021-04-14 8:13 ` [docs] " Quentin Schulz
2021-04-14 8:19 ` Nicolas Dechesne
2021-04-14 8:36 ` Robert P. J. Day
2021-04-15 14:18 ` Michael Opdenacker
2021-04-14 0:19 ` [PATCH 09/13] ref-manual: add FIT_KERNEL_COMP_ALG* Paul Eggleton
2021-04-14 8:16 ` [docs] " Quentin Schulz
2021-04-14 8:35 ` Robert P. J. Day
2021-04-14 8:41 ` Quentin Schulz
2021-04-14 8:43 ` Robert P. J. Day
2021-04-15 10:07 ` Paul Eggleton [this message]
2021-04-14 0:19 ` [PATCH 10/13] ref-manual: fix reference to build-essential Paul Eggleton
2021-04-14 8:17 ` [docs] " Quentin Schulz
2021-04-14 8:21 ` Nicolas Dechesne
2021-04-14 0:19 ` [PATCH 11/13] ref-manual: tweak buildtools section Paul Eggleton
2021-04-14 0:19 ` [PATCH 12/13] ref-manual: add migration section for 3.3 release Paul Eggleton
2021-04-14 8:26 ` [docs] " Quentin Schulz
2021-04-15 9:52 ` Paul Eggleton
2021-04-15 9:59 ` Quentin Schulz
2021-04-15 10:25 ` Nicolas Dechesne
2021-04-15 14:07 ` Quentin Schulz
2021-04-15 17:32 ` Nicolas Dechesne
2021-04-15 14:14 ` Michael Opdenacker
2021-04-14 0:19 ` [PATCH 13/13] ref-manual: migration guide: add release codenames Paul Eggleton
2021-04-14 8:28 ` [docs] " Quentin Schulz
2021-04-15 13:54 ` [docs] [PATCH 00/13] Documentation updates for 3.3 Michael Opdenacker
2021-04-15 14:00 ` Quentin Schulz
2021-04-15 14:05 ` 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=6250809.G0QQBjFxQf@linc \
--to=bluelightning@bluelightning.org \
--cc=docs@lists.yoctoproject.org \
--cc=rpjday@crashcourse.ca \
/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