linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [GIT PULL FOR renesas-drivers] DU LVDS dual-link mode support
Date: Tue, 30 Apr 2019 12:39:40 +0200	[thread overview]
Message-ID: <CAMuHMdULgs_s4Ba+hqBwZfqMJQfQt9muepiJON1U+V0ka7XG=A@mail.gmail.com> (raw)
In-Reply-To: <20190317021954.GA4912@pendragon.ideasonboard.com>

Hi Laurent,

On Sun, Mar 17, 2019 at 3:20 AM Laurent Pinchart
<laurent.pinchart@ideasonboard.com> wrote:
> The following changes since commit 3a7d2f4f4427f4b241f8240e370099e2ec1fd307:
>
>   Merge branch 'etnaviv/next' of https://git.pengutronix.de/git/lst/linux into drm-next (2019-03-12 15:20:57 +1000)
>
> are available in the Git repository at:
>
>   git://linuxtv.org/pinchartl/media.git b3ddd36a2b05
>
> for you to fetch changes up to b3ddd36a2b05074db0810a0f6508562f80045323:
>
>   arm64: dts: renesas: r8a7799[05]: Point LVDS0 to its companion LVDS1 (2019-03-13 03:42:41 +0200)
>
> The above commit is part of a branch name drm/du/lvds/dual-link in the
> same tree. The two top-most commits of the branch are hacks meant for
> testing only, so I didn't want to include them in this pull request.

Please rebase your branch. It conflicts due to newer versions of some commits
having been accepted in an upstream integration tree.

Thanks!

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

      reply	other threads:[~2019-04-30 10:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-17  2:19 [GIT PULL FOR renesas-drivers] DU LVDS dual-link mode support Laurent Pinchart
2019-04-30 10:39 ` Geert Uytterhoeven [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='CAMuHMdULgs_s4Ba+hqBwZfqMJQfQt9muepiJON1U+V0ka7XG=A@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --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 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).