All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Opdenacker" <michael.opdenacker@bootlin.com>
To: Jon Mason <jdmason@kudzu.us>, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 3/3] docs: update docs with new tune locations
Date: Fri, 13 Aug 2021 12:03:43 +0200	[thread overview]
Message-ID: <38d0eba3-72b2-b85b-674f-79dad2997761@bootlin.com> (raw)
In-Reply-To: <169A389D543FF76C.17558@lists.openembedded.org>

Hi Jon,

On 8/11/21 12:07 PM, Michael Opdenacker wrote:
>
> Thanks for the patch!
> Indeed, I believe that moving all arm includes to a specific directory
> would be more consistent, but that's just from the perspective of
> someone looking at the source repositories. I don't know how much
> trouble the big change would cause.
>
> Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>


Merged into yocto-docs master-next. Thanks again!
Michael.

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


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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-10 21:45 [PATCH 0/3] tunes: the great migration Jon Mason
2021-08-10 21:45 ` [PATCH 1/3] conf/machine: move tune files to architecture directories Jon Mason
2021-08-10 21:45 ` [PATCH 2/3] yocto-bsp: update machine confs with new tune locations Jon Mason
2021-08-13  8:19   ` [OE-core] " Alexandre Belloni
2021-08-10 21:45 ` [PATCH 3/3] docs: update docs " Jon Mason
2021-08-11 10:07   ` [OE-core] " Michael Opdenacker
     [not found]   ` <169A389D543FF76C.17558@lists.openembedded.org>
2021-08-13 10:03     ` Michael Opdenacker [this message]
2021-08-13 12:48       ` 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=38d0eba3-72b2-b85b-674f-79dad2997761@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=jdmason@kudzu.us \
    --cc=openembedded-core@lists.openembedded.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.