From: "Sapp, Randolph" <rs@ti.com>
To: Paul Barker <paul.barker@sancloud.com>
Cc: <reatmon@ti.com>, <denys@ti.com>, <detheridge@ti.com>,
<meta-ti@lists.yoctoproject.org>
Subject: Re: [EXTERNAL] Re: [EXTERNAL] Re: [master][PATCH v4] meta-ti-bsp: Graphics recipe overhaul
Date: Tue, 27 Dec 2022 11:55:30 -0600 [thread overview]
Message-ID: <IS9KNR.MN0Y5UHMX769@ti.com> (raw)
In-Reply-To: <4b9d9f9f-3b1c-4584-0b57-1b3d04a2b10d@sancloud.com>
[-- Attachment #1: Type: text/plain, Size: 944 bytes --]
On Fri, Dec 23 2022 at 14:42:12 +00:00:00, Paul Barker
<paul.barker@sancloud.com> wrote:
> Understood. In the next version of this patch, please include the list
> of MACHINEs or SoC families which are addressed by these changes. I'd
> also recommend splitting this up into multiple commits if possible so
> it's easier for external subscribers to this list to understand the
> changes.
Roger. My only concern for that is making sure these patches are
bisectable, and this is a sweeping change that can't really be split up
into multiple compilable patches. Recipies being updated that rely on
other repipies and machine feature unfortunatly means this is all or
nothing.
On Fri, Dec 23 2022 at 14:42:12 +00:00:00, Paul Barker
<paul.barker@sancloud.com> wrote:
> I'm happy to review & test graphics fixes for am335x/am65xx/am62xx
> when
> they arrive as we're using those SoCs.
This patch currently applies to am62xx, j721s2, j721e.
[-- Attachment #2: Type: text/html, Size: 1341 bytes --]
prev parent reply other threads:[~2022-12-27 17:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 4:06 [master][PATCH v4] meta-ti-bsp: Graphics recipe overhaul Randolph Sapp
2022-12-20 15:02 ` Paul Barker
2022-12-21 16:41 ` [EXTERNAL] " Sapp, Randolph
2022-12-23 14:42 ` Paul Barker
2022-12-27 17:55 ` 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=IS9KNR.MN0Y5UHMX769@ti.com \
--to=rs@ti.com \
--cc=denys@ti.com \
--cc=detheridge@ti.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=paul.barker@sancloud.com \
--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.