From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] msm drm update for component changes
Date: Wed, 9 Jul 2014 13:26:45 +0100 [thread overview]
Message-ID: <20140709122645.GQ21766@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAF6AEGv+hzSKuD2mRDbz-hqN1H09tW5C4a2EYuZ5sN44RABe8w@mail.gmail.com>
On Wed, Jul 09, 2014 at 06:56:14AM -0400, Rob Clark wrote:
> On Wed, Jul 9, 2014 at 5:34 AM, Russell King <rmk@arm.linux.org.uk> 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
> >
> > 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.
>
> Hey Russell, do you want me to take this for my v3.17 pull req? I
> expect there will be some minor conflicts with the DT support I'm
> working on at the moment.
>
> Or does this need to be applied together with the rest of the series?
> In which case, maybe it should go first, and then I'd rebase msm-next
> on top.
The patch for MSM is dependent on the component changes, which have
already been merged by Greg for the driver-core tree. I don't have
anything following this, so if you instead want to merge my
component-for-driver branch (which is what Greg's pulled, which is a
sub-set of this pull), and then add this patch on top of your
development, that's fine too.
The only reason it's a pull request and not a single patch is to ensure
that the previous component commits don't end up being duplicated with
different commit IDs across several trees by being applied independently
as patches (which can end up causing unnecessary git conflicts.)
--
FTTC broadband for 0.8mile line: now at 9.5Mbps down 400kbps up.
next prev parent reply other threads:[~2014-07-09 12:26 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 [this message]
2014-07-09 13:28 ` Rob Clark
2014-07-22 8:51 ` 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=20140709122645.GQ21766@n2100.arm.linux.org.uk \
--to=linux@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).