From: Eric Anholt <eric@anholt.net>
To: dri-devel@lists.freedesktop.org
Cc: linux-kernel@vger.kernel.org,
Boris Brezillon <boris.brezillon@bootlin.com>
Subject: Re: [PATCH] drm/vc4: Fix oops dereferencing DPI's connector since panel_bridge.
Date: Wed, 02 May 2018 10:01:20 -0700 [thread overview]
Message-ID: <87vac63sbj.fsf@anholt.net> (raw)
In-Reply-To: <20180309233256.1667-1-eric@anholt.net>
[-- Attachment #1: Type: text/plain, Size: 405 bytes --]
Eric Anholt <eric@anholt.net> writes:
> In the cleanup, I didn't notice that we needed to dereference the
> connector for the bus_format. Fix the regression by looking up the
> first (and only) connector attached to us, and assume that its
> bus_format is what we want. Some day it would be good to have that
> part of display_info attached to the bridge, instead.
Could anyone comment on this patch?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-05-02 17:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 23:32 [PATCH] drm/vc4: Fix oops dereferencing DPI's connector since panel_bridge Eric Anholt
2018-05-02 17:01 ` Eric Anholt [this message]
2018-05-02 20:03 ` Sean Paul
2018-05-02 20:29 ` Boris Brezillon
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=87vac63sbj.fsf@anholt.net \
--to=eric@anholt.net \
--cc=boris.brezillon@bootlin.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
/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