From: Maxime Ripard <mripard@kernel.org>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: devbrones <jonas.cronholm@protonmail.com>,
maarten.lankhorst@linux.intel.com,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>,
Simona Vetter <simona@ffwll.ch>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/edid: Add non-desktop quirk for Playstation VR Headsets with Product ID 0xB403
Date: Tue, 25 Mar 2025 10:29:22 +0100 [thread overview]
Message-ID: <20250325-inquisitive-ebony-mouse-bdf185@houat> (raw)
In-Reply-To: <875xjxa2rk.fsf@intel.com>
[-- Attachment #1: Type: text/plain, Size: 673 bytes --]
On Tue, Mar 25, 2025 at 11:16:47AM +0200, Jani Nikula wrote:
> On Sat, 22 Mar 2025, devbrones <jonas.cronholm@protonmail.com> wrote:
> > This fixes a bug where some Playstation VR Headsets would not be assigned
> > the EDID_QUIRK_NON_DESKTOP quirk, causing them to be inaccessible by
> > certain software under Wayland.
>
> Please file a bug over at [1], and attach the EDID on that bug, so we
> have some clue what's going on.
>
> [1] https://gitlab.freedesktop.org/drm/misc/kernel/-/issues/new
I'd rather have them in the commit log. Nobody uses gitlab issues for
drm-misc, and those kind of issues are just lingering around and
becoming stale.
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-03-25 9:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-22 12:21 [PATCH] drm/edid: Add non-desktop quirk for Playstation VR Headsets with Product ID 0xB403 devbrones
2025-03-25 9:16 ` Jani Nikula
2025-03-25 9:29 ` Maxime Ripard [this message]
2025-03-25 10:47 ` Jani Nikula
2025-03-25 11:09 ` Maxime Ripard
2025-03-25 15:03 ` Jani Nikula
2025-03-25 17:00 ` Maxime Ripard
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=20250325-inquisitive-ebony-mouse-bdf185@houat \
--to=mripard@kernel.org \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=jonas.cronholm@protonmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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