Linux Renesas SOC kernel development
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Cc: linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: renesas: salvator-x: Configure pins for the DU RGB output
Date: Wed, 17 Aug 2016 09:13:36 +0200	[thread overview]
Message-ID: <20160817071335.GG8673@verge.net.au> (raw)
In-Reply-To: <1470993535-11795-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>

On Fri, Aug 12, 2016 at 12:18:55PM +0300, Laurent Pinchart wrote:
> Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
> ---
>  arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> This patch depends on "[PATCH] pinctrl: sh-pfc: r8a7795: Add DU support"
> posted a few minutes ago to the linux-renesas-soc mailing list, as well as on
> the "[PATCH v2 0/4] R-Car Gen3 DU enablement on Salvator-X board" series
> posted yesterday to the same list.
> 
> As the boot loader configures the DU pins on Salvator-X we can safely delay
> this patch by one kernel version to let the pinctrl dependency hit mainling
> first.

I'm not entirely sure it is necessary to defer this patch by a kernel
release but if that is your wish then I'm happy to do so. If so
please repost at the appropriate time.

  parent reply	other threads:[~2016-08-17  7:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-12  9:18 [PATCH] arm64: dts: renesas: salvator-x: Configure pins for the DU RGB output Laurent Pinchart
2016-08-16  8:24 ` Geert Uytterhoeven
2016-08-17  7:13 ` Simon Horman [this message]
2016-08-17  9:00   ` Geert Uytterhoeven
2016-08-17  9:17     ` Laurent Pinchart
2016-08-18  7:12       ` Simon Horman
2016-09-06 10:28         ` 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=20160817071335.GG8673@verge.net.au \
    --to=horms@verge.net.au \
    --cc=laurent.pinchart+renesas@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