From: Arnd Bergmann <arnd@arndb.de>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>,
Mark Rutland <Mark.Rutland@arm.com>,
Will Deacon <Will.Deacon@arm.com>,
Marc Zyngier <Marc.Zyngier@arm.com>,
Liviu Dudau <Liviu.Dudau@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Thomas Lendacky <Thomas.Lendacky@amd.com>,
Joel Schopp <Joel.Schopp@amd.com>,
arm@kernel.org
Subject: Re: [PATCH V3] arm64: amd-seattle: Adding device tree for AMD Seattle platform
Date: Thu, 20 Nov 2014 13:33:43 +0100 [thread overview]
Message-ID: <201411201333.44180.arnd@arndb.de> (raw)
In-Reply-To: <20141113110002.GE20652@localhost>
On Thursday 13 November 2014, Catalin Marinas wrote:
> On Tue, Nov 11, 2014 at 01:24:39AM +0000, Suravee Suthikulpanit wrote:
> > Are there any other concerns about this patch?
>
> Let's cc the arm-soc guys, they are now handling SoC code for arm64.
Any update on the submission? I had some comments, am now waiting for a new
version to put into 3.19.
Arnd
next prev parent reply other threads:[~2014-11-20 12:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 13:36 [PATCH V3] arm64: amd-seattle: Adding device tree for AMD Seattle platform suravee.suthikulpanit
2014-11-11 1:24 ` Suravee Suthikulpanit
2014-11-13 11:00 ` Catalin Marinas
2014-11-20 12:33 ` Arnd Bergmann [this message]
2014-11-13 11:29 ` Arnd Bergmann
2014-11-20 15:16 ` Rob Herring
2014-11-20 15:23 ` Arnd Bergmann
2014-11-21 12:57 ` Marc Zyngier
2014-11-21 14:40 ` Suthikulpanit, Suravee
2014-11-21 14:48 ` Marc Zyngier
2014-11-21 16:25 ` Suthikulpanit, Suravee
-- strict thread matches above, loose matches on Subject: below --
2014-11-21 1:12 Suthikulpanit, Suravee
2014-11-21 12:38 ` Arnd Bergmann
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=201411201333.44180.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=Joel.Schopp@amd.com \
--cc=Liviu.Dudau@arm.com \
--cc=Marc.Zyngier@arm.com \
--cc=Mark.Rutland@arm.com \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=Thomas.Lendacky@amd.com \
--cc=Will.Deacon@arm.com \
--cc=arm@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@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