devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Magnus Damm <magnus.damm@gmail.com>,
	linux-sh@vger.kernel.org, linux-serial@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 0/7] ARM: shmobile: dtsi: Add SCIF fallback compatibility strings
Date: Fri, 18 Dec 2015 12:20:12 +0900	[thread overview]
Message-ID: <20151218032011.GA9704@verge.net.au> (raw)
In-Reply-To: <1450119475-1183-1-git-send-email-geert+renesas@glider.be>

On Mon, Dec 14, 2015 at 07:57:48PM +0100, Geert Uytterhoeven wrote:
> 	Hi Simon, Magnus,
> 
> This patch series adds fallback compatibility strings for SCIF and HSCIF
> to the DTS files for R-Car Gen1, Gen2, and Gen3, as defined in
> "[PATCH v3 02/27] serial: sh-sci: Add fallback compatibility strings" of
> series "[PATCH v3 00/27] serial: sh-sci: External Clock Support".
> This will allow the sh-sci driver to match on family-specific compatible
> values to enable BGR support later.
> 
> Note that fallback compatibility strings for SCIFA/SCIFB are not added
> yet.
> 
> Dependencies:
>   - This series is against renesas-devel-20151214-v4.4-rc5,
>   - It can be applied independently, as soon as the aforementioned DT
>     binding patch has been accepted,
>   - Later series depend on this:
>       - "[PATCH v3 00/12] ARM: shmobile: dtsi: Rename the serial port
> 	 clock to fck",
>       - "[PATCH v2 0/7] ARM: shmobile: dtsi: Add BRG support for (H)SCIF",
>       - "[PATCH v2 0/9] ARM: shmobile: dts: Enable SCIF_CLK frequency and
> 	 pins".

I have marked this and the above series as deferred pending
acceptance of the driver changes.

      parent reply	other threads:[~2015-12-18  3:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-14 18:57 [PATCH 0/7] ARM: shmobile: dtsi: Add SCIF fallback compatibility strings Geert Uytterhoeven
2015-12-14 18:57 ` [PATCH 1/7] ARM: shmobile: r8a7778 " Geert Uytterhoeven
     [not found] ` <1450119475-1183-1-git-send-email-geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>
2015-12-14 18:57   ` [PATCH 2/7] ARM: shmobile: r8a7779 " Geert Uytterhoeven
2015-12-14 18:57   ` [PATCH 7/7] arm64: renesas: r8a7795 " Geert Uytterhoeven
2015-12-14 18:57 ` [PATCH 3/7] ARM: shmobile: r8a7790 " Geert Uytterhoeven
2015-12-14 18:57 ` [PATCH 4/7] ARM: shmobile: r8a7791 " Geert Uytterhoeven
2015-12-14 18:57 ` [PATCH 5/7] ARM: shmobile: r8a7793 " Geert Uytterhoeven
2015-12-14 18:57 ` [PATCH 6/7] ARM: shmobile: r8a7794 " Geert Uytterhoeven
2015-12-18  3:20 ` Simon Horman [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=20151218032011.GA9704@verge.net.au \
    --to=horms@verge.net.au \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    /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).