linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: rmk@arm.linux.org.uk (Russell King)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] msm drm update for component changes
Date: Tue, 22 Jul 2014 09:51:20 +0100	[thread overview]
Message-ID: <20140722085119.GA15250@rmk-PC.arm.linux.org.uk> (raw)
In-Reply-To: <20140709093458.GA17540@rmk-PC.arm.linux.org.uk>

On Wed, Jul 09, 2014 at 10:34:58AM +0100, Russell King wrote:
> David,
> 
> Please incorporate the latest msm drm update for component changes, which can be found at:
> 
>   git://ftp.arm.linux.org.uk/~rmk/linux-arm.git component-for-drm

Ping?

> 
> with SHA1 84448288546d13d7e06fd6638fb78ddff559b399.
> 
> This updates the MSM's DRM driver for the updates merged in Greg's
> driver-core tree, converting MSM to use the pre-declared array of
> matches rather than walking the device tree each time we try to bind.
> 
> This will update the following files:
> 
>  drivers/base/component.c      | 192 ++++++++++++++++++++++++++++++++++--------
>  drivers/gpu/drm/msm/msm_drv.c |  83 ++++++++----------
>  include/linux/component.h     |   7 ++
>  3 files changed, 199 insertions(+), 83 deletions(-)
> 
> through these changes:
> 
> Russell King (5):
>       component: fix missed cleanup in case of devres failure
>       component: ignore multiple additions of the same component
>       component: add support for component match array
>       component: fix bug with legacy API
>       drm: msm: update to use component match support
> 
> Many thanks.

      parent reply	other threads:[~2014-07-22  8:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-09  9:34 [GIT PULL] msm drm update for component changes Russell King
2014-07-09 10:56 ` Rob Clark
2014-07-09 12:26   ` Russell King - ARM Linux
2014-07-09 13:28     ` Rob Clark
2014-07-22  8:51 ` Russell King [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=20140722085119.GA15250@rmk-PC.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).