From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Dave Airlie <airlied@gmail.com>
Cc: horms@verge.net.au, dri-devel@lists.freedesktop.org
Subject: Re: [GIT PULL FOR v3.12] R-Car DU DRM support for R8A7790 SoC
Date: Thu, 08 Aug 2013 03:34:17 +0200 [thread overview]
Message-ID: <1475596.86340mGHPd@avalon> (raw)
In-Reply-To: <CAPM=9tyQG1g70wjNy2tm4-uvnrguXBOfyGOiNEG1rAePkDJp-Q@mail.gmail.com>
Hi Dave,
(CC'ing Simon Horman, the shmobile tree maintainer)
On Thursday 08 August 2013 10:57:33 Dave Airlie wrote:
> On Thu, Aug 8, 2013 at 10:43 AM, Laurent Pinchart wrote:
> > Hi Dave,
> >
> > I've got a couple of arch/arm/ patches that depend on this series and that
> > I would like to get merged in v3.12. They should go upstream through the
> > arm-soc tree. Would you be able to provide a stable branch with this
> > patch set based on one of the 3.11-rcX tags ? Ideally that branch should
> > have as little patches as possible other than this set.
>
> Yeah that shouldn't be a problem, though is there any interface changes or
> things with this wrt drm-next?
>
> i.e. will this tree build on v3.11-rcX and drm-next?
They depend on a fix that went in between -rc1 and -rc2. You can base the
branch on any -rc >= 2.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-08-08 1:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 11:23 [GIT PULL FOR v3.12] R-Car DU DRM support for R8A7790 SoC Laurent Pinchart
2013-08-08 0:43 ` Laurent Pinchart
2013-08-08 0:57 ` Dave Airlie
2013-08-08 1:34 ` Laurent Pinchart [this message]
2013-08-08 1:39 ` Simon Horman
2013-08-09 20:45 ` Dave Airlie
2013-08-09 21:25 ` Laurent Pinchart
2013-08-09 21:28 ` Dave Airlie
2013-08-13 2:18 ` Simon Horman
2013-08-21 8:36 ` Simon Horman
2013-08-21 11:31 ` Laurent Pinchart
2013-08-22 2:29 ` Simon Horman
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=1475596.86340mGHPd@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=horms@verge.net.au \
/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.