dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: airlied@linux.ie, dri-devel@lists.freedesktop.org
Subject: [GIT PULL] Armada DRM fixes
Date: Mon, 27 Jan 2014 23:58:20 +0000	[thread overview]
Message-ID: <20140127235820.GA29323@rmk-PC.arm.linux.org.uk> (raw)

David,

Please incorporate the latest Armada DRM fix, which can be found at:

  git://ftp.arm.linux.org.uk/~rmk/linux-cubox.git drm-armada-fixes

with SHA1 bed86f15bdc23436fb30d09e2faa3dfb7d3834e1.

Just one-liner which corrects a select statement for DRM_KMS_FB_HELPER
which looks like it was missed in the initial merge.  Based on 3.13.

This will update the following files:

 drivers/gpu/drm/armada/Kconfig | 1 +
 1 file changed, 1 insertion(+)

through these changes:

Russell King (1):
      DRM: armada: fix missing DRM_KMS_FB_HELPER select

Thanks.

             reply	other threads:[~2014-01-27 23:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-27 23:58 Russell King [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-10-24 18:25 [GIT PULL] Armada DRM fixes Russell King
2016-10-19 16:30 Russell King

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=20140127235820.GA29323@rmk-PC.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.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