From: Christopher Harvey <charvey@matrox.com>
To: dri-devel@lists.freedesktop.org
Cc: Mathieu Larouche <mathieu.larouche@matrox.com>
Subject: Re: [PATCH 0/4] mgag200 fixes
Date: Thu, 09 May 2013 15:41:12 -0400 [thread overview]
Message-ID: <87r4hgos9z.fsf@matrox.com> (raw)
In-Reply-To: <cover.1368122227.git.charvey@matrox.com>
Christopher Harvey <charvey@matrox.com> writes:
> The Following should be CC'd to stable:
> * drm/mgag200: Fix writes into MGA1064_PIX_CLK_CTL register
> * drm/mgag200: Fix framebuffer base address programming
>
> The others are bug fixes, but aren't critical. I'm sitting on some
> hardware cursor code that depends on all of these patches before it
> can go in. I'm aiming for 3.11 for the hardware cursor support.
>
> thanks,
> Christopher Harvey (4):
> drm/mgag200: Don't change unrelated registers during modeset
> drm/mgag200: Fix writes into MGA1064_PIX_CLK_CTL register
> drm/mgag200: Convert counter delays to jiffies
> drm/mgag200: Fix framebuffer base address programming
>
> drivers/gpu/drm/mgag200/mgag200_mode.c | 90 ++++++++++++++++++++--------------
> 1 file changed, 52 insertions(+), 38 deletions(-)
please ignore this, version 2 has been posted.
-C
prev parent reply other threads:[~2013-05-09 19:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 17:57 [PATCH 0/4] mgag200 fixes Christopher Harvey
2013-04-12 20:42 ` [PATCH 1/4] drm/mgag200: Don't change unrelated registers during modeset Christopher Harvey
2013-04-12 22:24 ` [PATCH 2/4] drm/mgag200: Fix writes into MGA1064_PIX_CLK_CTL register Christopher Harvey
2013-05-06 15:56 ` [PATCH 3/4] drm/mgag200: Convert counter delays to jiffies Christopher Harvey
2013-05-08 19:10 ` [PATCH 4/4] drm/mgag200: Fix framebuffer base address programming Christopher Harvey
2013-05-09 19:41 ` Christopher Harvey [this message]
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=87r4hgos9z.fsf@matrox.com \
--to=charvey@matrox.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=mathieu.larouche@matrox.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