From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM vf610: add compatibilty strings of supported Vybrid SoC's
Date: Tue, 2 Dec 2014 22:12:17 +0800 [thread overview]
Message-ID: <20141202141215.GK2411@dragon> (raw)
In-Reply-To: <1417130825-2818-1-git-send-email-stefan@agner.ch>
On Fri, Nov 28, 2014 at 12:27:05AM +0100, Stefan Agner wrote:
> The Vybrid SoC family (in the kernel known as vf610) is a familiy
> of multiple similar SoC's. The VF5xx series comes without secondary
> Cortex-M4 core, while the second number VFx1x indicates the presence
> of a L2 cache controller.
>
> Signed-off-by: Stefan Agner <stefan@agner.ch>
Applied, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawn.guo@linaro.org>
To: Stefan Agner <stefan@agner.ch>
Cc: kernel@pengutronix.de, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM vf610: add compatibilty strings of supported Vybrid SoC's
Date: Tue, 2 Dec 2014 22:12:17 +0800 [thread overview]
Message-ID: <20141202141215.GK2411@dragon> (raw)
In-Reply-To: <1417130825-2818-1-git-send-email-stefan@agner.ch>
On Fri, Nov 28, 2014 at 12:27:05AM +0100, Stefan Agner wrote:
> The Vybrid SoC family (in the kernel known as vf610) is a familiy
> of multiple similar SoC's. The VF5xx series comes without secondary
> Cortex-M4 core, while the second number VFx1x indicates the presence
> of a L2 cache controller.
>
> Signed-off-by: Stefan Agner <stefan@agner.ch>
Applied, thanks.
next prev parent reply other threads:[~2014-12-02 14:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 23:27 [PATCH] ARM vf610: add compatibilty strings of supported Vybrid SoC's Stefan Agner
2014-11-27 23:27 ` Stefan Agner
2014-11-27 23:27 ` Stefan Agner
2014-12-02 14:12 ` Shawn Guo [this message]
2014-12-02 14:12 ` Shawn Guo
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=20141202141215.GK2411@dragon \
--to=shawn.guo@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.