From: "Denys Dmytriyenko" <denis@denix.org>
To: Jon Mason <jdmason@kudzu.us>
Cc: meta-arm@lists.yoctoproject.org
Subject: Re: [meta-arm] [PATCH] layer.conf: remove dependency on meta-python
Date: Thu, 23 Jul 2020 14:16:54 -0400 [thread overview]
Message-ID: <20200723181654.GR17660@denix.org> (raw)
In-Reply-To: <20200723180730.GA19291@kudzu.us>
On Thu, Jul 23, 2020 at 02:07:31PM -0400, Jon Mason wrote:
> On Wed, Jul 22, 2020 at 12:07:40PM -0400, Denys Dmytriyenko wrote:
> > On Mon, Jul 20, 2020 at 01:51:32PM -0400, Denys Dmytriyenko wrote:
> > > On Mon, Jun 08, 2020 at 11:51:43AM -0400, Jon Mason wrote:
> > > > On Wed, Jun 03, 2020 at 07:49:25PM -0400, Denys Dmytriyenko wrote:
> > > > > From: Denys Dmytriyenko <denys@ti.com>
> > > > >
> > > > > Corresponding Python modules pycryptodome(x) and pyelftools, needed by optee,
> > > > > were moved from meta-python to oe-core.
> > > > >
> > > > > Signed-off-by: Denys Dmytriyenko <denys@ti.com>
> > > >
> > > > Pulled into master
> > >
> > > Can this be backported to dunfell as well, since the required Python module
> > > move has been finished in oe-core and meta-openembedded few weeks ago and
> > > there's been plenty of time for everyone to catch up with the change?
> >
> > Are there any objections to this change? Please let me know. Thanks.
>
> No internal objections, and it builds meta-arm-bsp without any
> problems (though not tested). So, I'm pulling in a modified version
> (as the current one doesn't cleanly apply) into the dunfell branch.
Thanks!
--
Denys
prev parent reply other threads:[~2020-07-23 18:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 23:49 [PATCH] layer.conf: remove dependency on meta-python Denys Dmytriyenko
2020-06-08 15:51 ` [meta-arm] " Jon Mason
2020-07-20 17:51 ` Denys Dmytriyenko
[not found] ` <16238755CA6601E8.5706@lists.yoctoproject.org>
2020-07-22 16:07 ` Denys Dmytriyenko
2020-07-23 18:07 ` Jon Mason
2020-07-23 18:16 ` Denys Dmytriyenko [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=20200723181654.GR17660@denix.org \
--to=denis@denix.org \
--cc=jdmason@kudzu.us \
--cc=meta-arm@lists.yoctoproject.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.