All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [GIT PULL FOR renesas-drivers] R-Car H3 ES2.0 display support
Date: Mon, 19 Jun 2017 11:15:36 +0300	[thread overview]
Message-ID: <2212883.mR9x81Zv3F@avalon> (raw)
In-Reply-To: <CAMuHMdXREBCD9w8rkW6vXxh-Ro4waLN08Q1ePiS4uYoOMbGBGQ@mail.gmail.com>

Hi Geert,

On Friday 16 Jun 2017 10:03:57 Geert Uytterhoeven wrote:
> On Thu, Jun 15, 2017 at 8:54 PM, Laurent Pinchart wrote:
> > The following changes implement display support for the R-Car H3 ES2.0.
> > They have been split in three distinct branches:
>
> Thanks for your branches!
> 
> > - tags/drm-h3-es2-dt-20170615 contains the DT changes and is based on top
> > of topic/r8a7795es2-integration
> 
> When merging this into next-20170616, there are lots of conflicts.
> Most are due to your tag being based on a one-month old version of
> renesas-devel.
> 
> As the relevant DT changes in topic/r8a7795es2-integration have been applied
> to renesas-devel, you could rebase on top of the latter.

Do you mean renesas-devel-20170616-v4.12-rc5 ? I don't want to pull the whole 
renesas-drivers tree as a base for my development branches, I'd prefer keeping 
the out-of-mainline dependencies as small as possible.

> > - tags/drm-h3-es2-pinctrl-20170615 contains the pinctrl changes for the DU
> > and is based on top of sh-pfc-for-v4.13-tag1
> 
> Merges cleanly into next-20170616.
> 
> > - tags/drm-h3-es2-vsp-20170615 contains the VSP changes and is based on
> > top of v4.12-rc1
> 
> When merging this into next-20170616, there are two conflicts, in
> drivers/media/platform/vsp1/vsp1_dl.c and include/media/vsp1.h.

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2017-06-19  8:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-15 18:54 [GIT PULL FOR renesas-drivers] R-Car H3 ES2.0 display support Laurent Pinchart
2017-06-16  8:03 ` Geert Uytterhoeven
2017-06-19  8:15   ` Laurent Pinchart [this message]
2017-06-19  8:27     ` Geert Uytterhoeven

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=2212883.mR9x81Zv3F@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-renesas-soc@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.