From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/6] arch/arm: add cortex-m7 core
Date: Sun, 20 May 2018 18:51:45 +0200 [thread overview]
Message-ID: <20180520185145.0feb1fa4@windsurf> (raw)
In-Reply-To: <87dbe541bbacbe1cbdcacec6d1fa4cbf67585a0d.1519589817.git.yann.morin.1998@free.fr>
Hello,
On Sun, 25 Feb 2018 21:18:13 +0100, Yann E. MORIN wrote:
> Nothing fancy, just a plain Cortex-M, armv7-M core...
>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> ---
> arch/Config.in.arm | 6 ++++++
> 1 file changed, 6 insertions(+)
Applied to next, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-05-20 16:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-25 20:18 [Buildroot] [PATCH 0/6] arch/ar: add cortex-m7, and cortex-M FPUs Yann E. MORIN
2018-02-25 20:18 ` [Buildroot] [PATCH 1/6] arch/arm: add cortex-m7 core Yann E. MORIN
2018-05-20 16:51 ` Thomas Petazzoni [this message]
2018-02-25 20:18 ` [Buildroot] [PATCH 2/6] arch/arm: introduce generic FPU internal option Yann E. MORIN
2018-02-25 20:18 ` [Buildroot] [PATCH 3/6] arch/arm: add option for FPv4 FPU Yann E. MORIN
2018-02-25 20:18 ` [Buildroot] [PATCH 4/6] arch/arm: add options for FPv5 FPU Yann E. MORIN
2018-02-25 20:18 ` [Buildroot] [PATCH 5/6] arch/arm: cortex-m4 may have an FPv4 FPU Yann E. MORIN
2018-02-25 20:18 ` [Buildroot] [PATCH 6/6] arch/arm: cortex-m7 may have a FPv5 FPU Yann E. MORIN
2018-05-20 17:22 ` [Buildroot] [PATCH 0/6] arch/ar: add cortex-m7, and cortex-M FPUs Thomas Petazzoni
2018-05-20 17:27 ` Yann E. MORIN
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=20180520185145.0feb1fa4@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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