From: "Sapp, Randolph" <rs@ti.com>
To: Ryan Eatmon <reatmon@ti.com>
Cc: <denys@ti.com>, <afd@ti.com>, <meta-ti@lists.yoctoproject.org>
Subject: Re: [PATCH] meta-ti-extras: ti-unpack: Drop update_data call
Date: Fri, 27 Jan 2023 17:07:19 -0600 [thread overview]
Message-ID: <7W26PR.GR323TWM8Z333@ti.com> (raw)
In-Reply-To: <eb4f4eaf-9e37-969c-c4aa-0c583d146f65@ti.com>
On Fri, Jan 27 2023 at 03:48:58 PM -0600, Ryan Eatmon <reatmon@ti.com>
wrote:
> On 1/27/2023 15:44, Sapp, Randolph wrote:
>> On Fri, Jan 27 2023 at 12:12:55 PM -0600, Ryan Eatmon
>> <reatmon@ti.com> \x7fwrote:
>>> This change was already made on the master branch back in November
>>> to \x7f\x7faddress this issue. Are you seeing this on other branches? I
>>> do not \x7f\x7fbelieve that this patch needs to be applied to dunfell or
>>> kirkstone \x7f\x7funless you are seeing an issue.
>>
>> I saw this issue under kirkstone with the latest version of my GPU
>> patch \x7ffor meta-ti and meta-arago.
>
> They must have back ported it.
Whoops, I was tracking bitbake main. Kirkstone doesn't appear to have
that commit yet. Still, there should be no reason to call update_data
as it is a deprecated function and a NOOP. Entirely up to you whether
you want to take this, I don't care.
prev parent reply other threads:[~2023-01-27 23:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 18:02 [PATCH] meta-ti-extras: ti-unpack: Drop update_data call Randolph Sapp
2023-01-27 18:12 ` Ryan Eatmon
2023-01-27 21:44 ` Sapp, Randolph
2023-01-27 21:48 ` Ryan Eatmon
2023-01-27 23:07 ` Sapp, Randolph [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=7W26PR.GR323TWM8Z333@ti.com \
--to=rs@ti.com \
--cc=afd@ti.com \
--cc=denys@ti.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=reatmon@ti.com \
/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.