From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>,
Alexander Kanavin <alex@linutronix.de>
Subject: Re: [OE-core] [RFC PATCH 2/6] meta-ide-support: adjust to provide (e)SDK experience directly in a yocto build
Date: Thu, 23 Jun 2022 18:41:01 +0200 [thread overview]
Message-ID: <20220623184101.206540dd@booty> (raw)
In-Reply-To: <CANNYZj-GAsOMpoqC6RWvrWnbNHS4+00d_wZtEWwwPH5-w0bu2Q@mail.gmail.com>
Hi Alex,
On Thu, 23 Jun 2022 16:52:55 +0200
Alexander Kanavin <alex.kanavin@gmail.com> wrote:
> Thanks Luca, this was not meant for merging (RFC), but it helps to see
> the issues upfront.
Sure, however Richard asked me to test this on the autobuilders.
Cheers.
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2022-06-23 16:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 10:33 [RFC PATCH 0/6] (e)SDK workflow directly in a Yocto build Alexander Kanavin
2022-06-22 10:33 ` [RFC PATCH 1/6] toolchain-scripts.bbclass: adjust toolchain_create_tree_env_script to better replicate (e)SDK Alexander Kanavin
2022-06-22 10:33 ` [RFC PATCH 2/6] meta-ide-support: adjust to provide (e)SDK experience directly in a yocto build Alexander Kanavin
2022-06-23 10:03 ` [OE-core] " Luca Ceresoli
2022-06-23 14:52 ` Alexander Kanavin
2022-06-23 16:41 ` Luca Ceresoli [this message]
2022-06-22 10:33 ` [RFC PATCH 3/6] oeqa/sdk: add a test class for running SDK tests directly in a Yocto build Alexander Kanavin
2022-06-22 10:33 ` [RFC PATCH 4/6] selftest/meta_ide: add a test for running SDK tests Alexander Kanavin
2022-06-22 10:33 ` [RFC PATCH 5/6] oeqa/sdk: allow epoxy/galculator tests to run in esdk and direct yocto builds Alexander Kanavin
2022-06-22 10:33 ` [RFC PATCH 6/6] oeqa/sdk: drop the nativesdk-python 2.x test Alexander Kanavin
2022-10-10 8:22 ` [OE-core] [RFC PATCH 0/6] (e)SDK workflow directly in a Yocto build Paul Eggleton
2022-10-10 9:20 ` Alexander Kanavin
2022-10-13 8:43 ` Leon Woestenberg
2022-10-13 8:52 ` Alexander Kanavin
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=20220623184101.206540dd@booty \
--to=luca.ceresoli@bootlin.com \
--cc=alex.kanavin@gmail.com \
--cc=alex@linutronix.de \
--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.