All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Opdenacker" <michael.opdenacker@bootlin.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH 1/2] test-manual: Add extra detail to YP Compatible section
Date: Wed, 4 Aug 2021 12:04:34 +0200	[thread overview]
Message-ID: <d982b722-9fd8-035f-878e-62ce7da99e9c@bootlin.com> (raw)
In-Reply-To: <20210804094714.3500323-1-richard.purdie@linuxfoundation.org>

Hi Richard,

Thanks for the documentation patch!

On 8/4/21 11:47 AM, Richard Purdie wrote:
> Add a note about documenting where a layer doesn't support 'core'
> functionality.
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> ---
>  documentation/test-manual/yocto-project-compatible.rst | 5 +++++
>  1 file changed, 5 insertions(+)
>
> diff --git a/documentation/test-manual/yocto-project-compatible.rst b/documentation/test-manual/yocto-project-compatible.rst
> index a7897469f..b83a0f12b 100644
> --- a/documentation/test-manual/yocto-project-compatible.rst
> +++ b/documentation/test-manual/yocto-project-compatible.rst
> @@ -115,6 +115,11 @@ Here are key best practices the program tries to encourage:
>     user changes a configuration setting to activate the layer, by selecting
>     a :term:`MACHINE`, a :term:`DISTRO` or a :term:`DISTRO_FEATURES` setting.
>  
> +-  Layers should be documenting where they don’t support normal 'core'
> +   functionality such as where debug symbols are disabled or missing, where
> +   development headers and on-target library usage may not work or where


Replaced "or" by "and" here, as we are dealing with a list of examples,
rather than with a list of alternatives.
https://forum.oxforddictionaries.com/en/discussion/27/such-as-or-or-and


> +   functionality like the SDK/eSDK would not be execpted to work.


s/execpted/expected/

This sounded like a system call, too much work with glibc, I guess ;-)
I took care of this change too, and will merge the change into
master-next (though extra reviews are still possible).

Cheers
Michael.

-- 
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  parent reply	other threads:[~2021-08-04 10:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-04  9:47 [PATCH 1/2] test-manual: Add extra detail to YP Compatible section Richard Purdie
2021-08-04  9:47 ` [PATCH 2/2] migration-3.4: Add extra notes to override sytnax changes Richard Purdie
2021-08-04 10:29   ` [docs] " Quentin Schulz
2021-08-04 10:42     ` Richard Purdie
2021-08-04 13:29     ` Michael Opdenacker
2021-08-04 10:04 ` Michael Opdenacker [this message]
2021-08-04 10:13   ` [docs] [PATCH 1/2] test-manual: Add extra detail to YP Compatible section Quentin Schulz
2021-08-04 10:18     ` Richard Purdie
2021-08-04 10:15   ` Richard Purdie
2021-08-05  8:07     ` 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=d982b722-9fd8-035f-878e-62ce7da99e9c@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=richard.purdie@linuxfoundation.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 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.