devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: arm@kernel.org
Cc: Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org, Russell King <linux@arm.linux.org.uk>,
	Pawel Moll <pawel.moll@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	Rob Herring <robh+dt@kernel.org>,
	Kumar Gala <galak@codeaurora.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/4] arm, arm64: uniphier: add a new driver, device tree updates
Date: Thu, 26 Nov 2015 11:30:57 +0900	[thread overview]
Message-ID: <CAK7LNASKQBoSHA1WRaLYjaFfv-a8s5Vhm-wbGtQbj0kDfBT5pA@mail.gmail.com> (raw)
In-Reply-To: <1448357962-12259-1-git-send-email-yamada.masahiro@socionext.com>

2015-11-24 18:39 GMT+09:00 Masahiro Yamada <yamada.masahiro@socionext.com>:
> Hi Arnd, Olof,
>
> Here is another series for UniPhier SoC family:
>
>  - 1/4: add a new driver.  The UniPhier System Bus is an external bus
>         where on-board devices are connected to the SoC.
>         (please check if the binding specification is OK.)
>
>  - 2/4: device tree updates to use the driver added by 1/4
>
>  - 3/4: trivial rename of device node names
>
>  - 4/4: initial commit for ARMv8 SoC/Board device trees
>
> Please apply 2/4, 3/4/, 4/4 into the same branch because 4/4 depends on 2/4 and 3/4.
> (4/4 creates symbolic links to ARM device trees.)


It looks like 1/4 will take longer, so want to postpone it for now.


I will resend 4/4 as a single patch.


-- 
Best Regards
Masahiro Yamada

  parent reply	other threads:[~2015-11-26  2:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-24  9:39 [PATCH 0/4] arm,arm64: uniphier: add a new driver, device tree updates Masahiro Yamada
2015-11-24  9:39 ` [PATCH 1/4] bus: uniphier-system-bus: add UniPhier System Bus Controller driver Masahiro Yamada
2015-11-24 11:50   ` Mark Rutland
2015-11-24 16:54     ` Masahiro Yamada
     [not found]       ` <CAK7LNAR_6qwVK9fNEAX-L_v1Z5cdGMU33bP75Rdtu5bdmid-3Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-11-24 17:38         ` Mark Rutland
2015-11-26  2:27           ` Masahiro Yamada
2015-11-24  9:39 ` [PATCH 2/4] ARM: dts: uniphier: add better-matching compatible string to extbus nodes Masahiro Yamada
2015-11-24  9:39 ` [PATCH 3/4] ARM: dts: uniphier: rename nodes from extbus to system-bus Masahiro Yamada
2015-11-24  9:39 ` [PATCH 4/4] arm64: dts: uniphier: add PH1-LD10 SoC/board support Masahiro Yamada
2015-11-26  2:30 ` Masahiro Yamada [this message]
2015-12-12  0:12 ` [PATCH 0/4] arm,arm64: uniphier: add a new driver, device tree updates Arnd Bergmann
2015-12-12  6:57   ` Masahiro Yamada

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=CAK7LNASKQBoSHA1WRaLYjaFfv-a8s5Vhm-wbGtQbj0kDfBT5pA@mail.gmail.com \
    --to=yamada.masahiro@socionext.com \
    --cc=arm@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=will.deacon@arm.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).