All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: Antonios Christidis <a-christidis@ti.com>
Cc: reatmon@ti.com, denys@konsulko.com, meta-ti@lists.yoctoproject.org
Subject: Re: [meta-ti][wrynose/master][PATCH V2] mesa-pvr: Migration from v24.0.1 -> v25.2.8
Date: Thu, 11 Jun 2026 09:35:01 -0400	[thread overview]
Message-ID: <20260611133501.GN23325@denix.org> (raw)
In-Reply-To: <34825ca9-9b5c-4706-a2ff-6f5311fde8b0@ti.com>

On Wed, Jun 10, 2026 at 06:10:58PM -0500, Antonios Christidis wrote:
> Dear Denys,
> 
> 
> I remembered your previous advice on this and tried this out before
> sending both patches.
> 
> The diff that is generated is too complex and difficult to read.
> Especially with the way git thinks mesa-pvr-25.inc file was created.
> 
> To make up for this, I have described the changes for the
> mesa-pvr_25.1.8.bb in the commit message. And the changes on
> mesa-pvr-25.inc can be tracked via oe-core, commit sha:
> 2c0c7c3e5b71.

Hmm, I wasn't expecting version 25 to be very different from 24.
E.g. here's the big update 24 -> 25 in OE-Core:
https://git.openembedded.org/openembedded-core/commit/meta/recipes-graphics/mesa/mesa.inc?id=f9eb0468e45ee5a6a3b3195ef5e78c328c4347c9

In such case, it is recommended to split the changes and have a single 
commit that copies OE-Core mesa.inc _verbatim_ from commit 2c0c7c3e5b71 
into mesa-pvr_25.inc in meta-ti without any modifications, making sure 
the commit message is very clear it's a verbatim copy.

Then in the next commit you modify mesa-pvr_25.inc for your needs and 
plug it into meta-ti BSP framework.

That way the focus of reviews will be on your changes mostly, not what's 
already in upstream.


> If this is still of interest, I can send the formatted patch.
> 
> 
> Kind Regards,
> 
> Antonios
> 
> On 6/10/26 6:05 PM, Denys Dmytriyenko wrote:
> >Please use -C and/or -M options when generating the patch, so there's a clear
> >diff between 24 and 25 .inc files. Thanks.
> >
> >
> >On Wed, Jun 10, 2026 at 05:58:44PM -0500, Antonios Christidis via lists.yoctoproject.org wrote:
> >>Dear Ryan Denys,
> >>
> >>
> >>Let me know your thoughts on the overall patch. I am particularly
> >>interested on your opinions on the following change:
> >>
> >>On 6/10/26 5:51 PM, Antonios Christidis via lists.yoctoproject.org wrote:
> >>>BSP_MESA_PVR_VERSION:bsp-ti-6_18: = "2%"
> >>
> >>I wish there was a way to use syntax like
> >>"BSP_MESA_PVR_VERSION:bsp-ti-6_18 = "24%|25%" or even
> >>"24.0.1|25.2.8". Is there a better way of enabling this logic ?
> >>
> >>Also already aware of the extra ":" post-pended to the variable, I
> >>can send a v3 if that's all the feedback.
> >>
> >>
> >>Kind Regards,
> >>
> >>Antonios


  reply	other threads:[~2026-06-11 13:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <18B7DA0BBD971E15.267903@lists.yoctoproject.org>
2026-06-10 22:58 ` [meta-ti][wrynose/master][PATCH V2] mesa-pvr: Migration from v24.0.1 -> v25.2.8 Antonios Christidis
2026-06-10 23:05   ` Denys Dmytriyenko
2026-06-10 23:10     ` Antonios Christidis
2026-06-11 13:35       ` Denys Dmytriyenko [this message]
2026-06-11  2:17   ` Ryan Eatmon
2026-06-11 13:23     ` Denys Dmytriyenko
2026-06-11 16:30       ` Antonios Christidis
2026-06-11 16:50         ` Denys Dmytriyenko
2026-06-11 18:29           ` Antonios Christidis
2026-06-15 19:33             ` Andrew Davis
2026-06-17 14:07               ` Antonios Christidis
2026-06-17 14:30                 ` Ryan Eatmon
2026-06-10 22:51 a-christidis
2026-06-10 22:55 ` PRC Automation
2026-06-10 23:28   ` Ryan Eatmon
2026-06-10 23:32     ` Antonios Christidis

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=20260611133501.GN23325@denix.org \
    --to=denis@denix.org \
    --cc=a-christidis@ti.com \
    --cc=denys@konsulko.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.