From: Florian Mickler <florian@mickler.org>
To: Keith Packard <keithp@keithp.com>
Cc: Chris Wilson <chris@chris-wilson.co.uk>,
Dave Airlie <airlied@redhat.com>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 2/2] drm: record monitor status in output_poll_execute
Date: Wed, 8 Dec 2010 17:34:24 +0100 [thread overview]
Message-ID: <20101208173424.76ec4041@schatten.dmk.lab> (raw)
In-Reply-To: <yunpqtgexml.fsf@aiko.keithp.com>
On Sun, 05 Dec 2010 13:08:18 -0800
Keith Packard <keithp@keithp.com> wrote:
> On Sun, 5 Dec 2010 13:27:43 +0100, Florian Mickler <florian@mickler.org> wrote:
> > On Fri, 26 Nov 2010 10:45:59 -0800
> > Keith Packard <keithp@keithp.com> wrote:
> >
> > > In order to correctly report monitor connected status changes, the
> > > previous monitor status must be recorded in the connector->status
> > > value instead of being discarded.
> > >
> > > Signed-off-by: Keith Packard <keithp@keithp.com>
> >
> > Keith, am I right to assume that these address
> > https://bugzilla.kernel.org/show_bug.cgi?id=22672
> > and probably:
> > https://bugzilla.kernel.org/show_bug.cgi?id=23472
>
> Yes, this is part of the patch for that. The other piece is in the 2D
> driver which has a matching bug. That patch is already on master.
>
Does that mean that the kernel regression will not be
fixed/worked-around for old userspace?
Regards,
Flo
next prev parent reply other threads:[~2010-12-08 16:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-26 18:45 [PATCH 1/2] drm: Set connector DPMS status to ON in drm_crtc_helper_set_config Keith Packard
2010-11-26 18:45 ` [PATCH 2/2] drm: record monitor status in output_poll_execute Keith Packard
2010-12-05 12:27 ` [Intel-gfx] " Florian Mickler
2010-12-05 21:08 ` Keith Packard
2010-12-08 16:34 ` Florian Mickler [this message]
2010-12-08 17:08 ` Chris Wilson
2010-12-08 17:30 ` Keith Packard
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=20101208173424.76ec4041@schatten.dmk.lab \
--to=florian@mickler.org \
--cc=airlied@redhat.com \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=keithp@keithp.com \
--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