From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: arm@kernel.org
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
devicetree@vger.kernel.org, Kumar Gala <galak@codeaurora.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Will Deacon <will.deacon@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64: dts: uniphier: rename PH1-LD10 to PH1-LD20
Date: Fri, 26 Feb 2016 16:22:59 +0900 [thread overview]
Message-ID: <CAK7LNAQ8smP1X613QCi2MXJ7M+v+bd4GmumXP84Ttt-40+jtUg@mail.gmail.com> (raw)
In-Reply-To: <1456202421-10857-1-git-send-email-yamada.masahiro@socionext.com>
2016-02-23 13:40 GMT+09:00 Masahiro Yamada <yamada.masahiro@socionext.com>:
> Due to the company's awful projecting, this chip has been renamed to
> PH1-LD20. It has not been shipped yet, this change would not give
> much impact on our customers.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> ---
>
> Olof, Arnd,
>
> Please apply this patch along with my series
> "[PATCH 0/9] ARM: uniphier: UniPhier updates for Linux 4.6-rc1".
>
> If it goes to a different branch, it will cause a big merge conflict later.
Note:
This patch has been included in the series,
"ARM: dts: uniphier: UniPhier DT updates for Linux 4.6-rc1 (2nd round)"
in order to clarify the patch dependency.
--
Best Regards
Masahiro Yamada
prev parent reply other threads:[~2016-02-26 7:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 4:40 [PATCH] arm64: dts: uniphier: rename PH1-LD10 to PH1-LD20 Masahiro Yamada
2016-02-26 7:22 ` Masahiro Yamada [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=CAK7LNAQ8smP1X613QCi2MXJ7M+v+bd4GmumXP84Ttt-40+jtUg@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=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).