All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Dave Airlie <airlied@gmail.com>
Cc: linux-tegra@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: [PULL] drm/tegra: Fixes for v3.14-rc3
Date: Wed, 12 Feb 2014 08:06:58 +0100	[thread overview]
Message-ID: <20140212070656.GA26778@ulmo.nvidia.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1264 bytes --]

Hi Dave,

The following changes since commit 38dbfb59d1175ef458d006556061adeaa8751b72:

  Linus 3.14-rc1 (2014-02-02 16:42:13 -0800)

are available in the git repository at:

  git://anongit.freedesktop.org/tegra/linux tags/drm/for-3.14-rc3

for you to fetch changes up to b18915379071b31ea819a36ca67761620decba06:

  drm/tegra: Add guard to avoid double disable/enable of RGB outputs (2014-02-12 07:50:38 +0100)

Thanks,
Thierry

----------------------------------------------------------------
drm/tegra: Fixes for v3.14-rc3

These patches contain a fix for a potential hang when the RGB output is
disabled twice, a typofix that prevents the framebuffer console from
being restored on ->lastclose() and an optimization to do as little work
as possible during host1x job submission.

----------------------------------------------------------------
Dmitry Osipenko (1):
      drm/tegra: Add guard to avoid double disable/enable of RGB outputs

Erik Faye-Lund (1):
      gpu: host1x: do not check previously handled gathers

Paul Bolle (1):
      drm/tegra: fix typo 'CONFIG_TEGRA_DRM_FBDEV'

 drivers/gpu/drm/tegra/drm.c |  2 +-
 drivers/gpu/drm/tegra/rgb.c | 11 +++++++++++
 drivers/gpu/host1x/job.c    |  2 +-
 3 files changed, 13 insertions(+), 2 deletions(-)

[-- Attachment #1.2: Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

                 reply	other threads:[~2014-02-12  7:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20140212070656.GA26778@ulmo.nvidia.com \
    --to=thierry.reding@gmail.com \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-tegra@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.