From: "Souza, Jose" <jose.souza@intel.com>
To: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
"De Marchi, Lucas" <lucas.demarchi@intel.com>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Harrison, John C" <john.c.harrison@intel.com>,
"Filipchuk, Julia" <julia.filipchuk@intel.com>,
"thomas.hellstrom@linux.intel.com"
<thomas.hellstrom@linux.intel.com>
Subject: Re: [PATCH] Revert "drm/xe/devcoredump: Add ASCII85 dump helper function"
Date: Fri, 13 Dec 2024 15:10:05 +0000 [thread overview]
Message-ID: <a49a74a0b2ac363691f26dddde60aae60461ccbb.camel@intel.com> (raw)
In-Reply-To: <t6j573cbepbjwiclv5ulewcapwqyf7np4bvdut6gjario6wmeq@sk3cxg6mnos7>
On Fri, 2024-12-13 at 08:38 -0600, Lucas De Marchi wrote:
> On Fri, Dec 13, 2024 at 09:12:52AM -0500, Rodrigo Vivi wrote:
> > We do not break userspace.
There is other patch that also breaks Mesa parser:
drm/xe/devcoredump: Improve section headings and add tile info
> >
> > This reverts commit ec1455ce7e35a31289d2dbc1070b980538698921.
>
> But we have users calling this function.... the revert is not so simple.
> I think we need to revert the functionality rather than reverting all
> the patches, otherwise it will cause a lot of headaches.
>
> I propose we go with:
>
> a) drop the \n that broke mesa and merge that with cc stable.
>
> b) move back the entry to the previous section that broke mesa and cc
> stable.
>
> José, would it be ok to merge a patch in mesa and port that
> to mesa stable that simply looks at 2 possible sections? Or even
> drop the section checks... ?
>
> c) settle on one of the possible solutions for \n that were presented in
> this discussion. I think the sanest one is that a space in the end of a
> line printing ascii85 would signify a continuation marker. But merging
> (a) means we have time to discuss and adjust if needed.
>
> After the dust settles we may think of a better way to evolve the
> devcoredump format so it doesn't cause breakages in future updates.
>
> Lucas De Marchi
next prev parent reply other threads:[~2024-12-13 15:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 14:12 [PATCH] Revert "drm/xe/devcoredump: Add ASCII85 dump helper function" Rodrigo Vivi
2024-12-13 14:38 ` Lucas De Marchi
2024-12-13 15:10 ` Souza, Jose [this message]
2024-12-13 15:18 ` Lucas De Marchi
2024-12-13 15:24 ` Souza, Jose
2024-12-13 15:50 ` Lucas De Marchi
2024-12-13 16:28 ` Souza, Jose
2024-12-13 16:48 ` Lucas De Marchi
2024-12-13 16:56 ` John Harrison
2024-12-13 17:25 ` Souza, Jose
2024-12-13 17:38 ` John Harrison
2024-12-13 19:43 ` Souza, Jose
2024-12-13 20:26 ` John Harrison
2024-12-13 20:46 ` Souza, Jose
2024-12-13 21:39 ` Lucas De Marchi
2024-12-14 1:08 ` John Harrison
2024-12-13 16:58 ` ✓ CI.Patch_applied: success for " Patchwork
2024-12-13 16:59 ` ✗ CI.checkpatch: warning " Patchwork
2024-12-13 16:59 ` ✗ CI.KUnit: failure " Patchwork
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=a49a74a0b2ac363691f26dddde60aae60461ccbb.camel@intel.com \
--to=jose.souza@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=john.c.harrison@intel.com \
--cc=julia.filipchuk@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=thomas.hellstrom@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox