From: Arnd Bergmann <arnd@arndb.de>
To: Liviu Dudau <Liviu.Dudau@arm.com>
Cc: arm@kernel.org, Olof Johansson <olof@lixom.net>,
Kevin Hilman <khilman@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Pawel Moll <pawel.moll@arm.com>,
Will Deacon <will.deacon@arm.com>,
device tree <devicetree@vger.kernel.org>,
LAKML <linux-arm-kernel@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>
Subject: Re: [PATCH v3 0/2] arm64: Add support for Juno development board
Date: Thu, 20 Nov 2014 17:52:47 +0100 [thread overview]
Message-ID: <201411201752.47955.arnd@arndb.de> (raw)
In-Reply-To: <1415727131-4572-1-git-send-email-Liviu.Dudau@arm.com>
On Tuesday 11 November 2014, Liviu Dudau wrote:
> Hi,
>
> This patchset adds device tree support for ARM's AArch64 Juno development
> board. It enables use of various peripherals on the board, from USB and
> networking to I2C and PL011 UART.
>
> The patches can also be found in the repository at:
>
> git://github.com/ARM-software/linux.git juno/dts-for-armsoc
Applied both on the arm64 tree, on top of the directory cleanup branch.
Thanks,
Arnd
prev parent reply other threads:[~2014-11-20 16:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 17:32 [PATCH v3 0/2] arm64: Add support for Juno development board Liviu Dudau
2014-11-11 17:32 ` [PATCH v3 1/2] arm64: Create link to include/dt-bindings to enable C preprocessor use Liviu Dudau
2014-11-27 8:34 ` [v3, " Pankaj Dubey
2014-11-27 11:24 ` Liviu Dudau
2014-11-11 17:32 ` [PATCH v3 2/2] arm64: Add Juno board device tree Liviu Dudau
2014-11-26 10:30 ` Marc Zyngier
2014-11-26 10:59 ` Liviu Dudau
2014-11-26 11:36 ` Marc Zyngier
2014-11-20 10:54 ` [PATCH v3 0/2] arm64: Add support for Juno development board Liviu Dudau
2014-11-20 16:52 ` Arnd Bergmann [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=201411201752.47955.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=Liviu.Dudau@arm.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=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=olof@lixom.net \
--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