public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Rolland <rol@witbe.net>
To: Zack Rusin <zack.rusin@broadcom.com>
Cc: Andreas Piesk <a.piesk@mailbox.org>,
	bcm-kernel-feedback-list@broadcom.com, christian@heusel.eu,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	maaz.mombasawala@broadcom.com, martin.krastev@broadcom.com,
	rdkehn@gmail.com, regressions@lists.linux.dev,
	spender@grsecurity.net, rol@witbe.net
Subject: Re: [REGRESSION][BISECTED] vmwgfx crashes with command buffer error after update
Date: Mon, 2 Sep 2024 10:34:36 +0200	[thread overview]
Message-ID: <20240902103436.5806f7ec@riri> (raw)
In-Reply-To: <CABQX2QM1A9yWCuOHV6kgi3YbPvPHz-zazkOXM6Up9RWrZ-CgPQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 285 bytes --]

Hello,

On Fri, 16 Aug 2024 14:56:19 -0400
Zack Rusin <zack.rusin@broadcom.com> wrote:

> Thanks! I see. I have a patch out that fixes it, but in general I

Any chance to see that one pushed to stable 6.10.x kernels so that we can
have a working console ?

Regards,
Paul


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  parent reply	other threads:[~2024-09-02  8:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-15 17:48 [REGRESSION][BISECTED] vmwgfx crashes with command buffer error after update Christian Heusel
2024-08-15 17:51 ` Brad Spengler
2024-08-15 18:40 ` Zack Rusin
2024-08-15 20:30   ` Andreas Piesk
2024-08-16 18:56     ` Zack Rusin
2024-08-16 20:23       ` Andreas Piesk
2024-09-02  8:34       ` Paul Rolland [this message]
2024-09-02  8:42         ` Christian Heusel
2024-09-05  7:54           ` Paul Rolland
2024-08-19 17:49 ` Paul Rolland
2024-08-19 22:48   ` Doug Kehn
2024-08-20 10:14     ` Paul Rolland

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=20240902103436.5806f7ec@riri \
    --to=rol@witbe.net \
    --cc=a.piesk@mailbox.org \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=christian@heusel.eu \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maaz.mombasawala@broadcom.com \
    --cc=martin.krastev@broadcom.com \
    --cc=rdkehn@gmail.com \
    --cc=regressions@lists.linux.dev \
    --cc=spender@grsecurity.net \
    --cc=zack.rusin@broadcom.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