From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/6] arch/ar: add cortex-m7, and cortex-M FPUs
Date: Sun, 20 May 2018 19:22:43 +0200 [thread overview]
Message-ID: <20180520192243.207524ca@windsurf> (raw)
In-Reply-To: <cover.1519589817.git.yann.morin.1998@free.fr>
Hello,
On Sun, 25 Feb 2018 21:18:14 +0100, Yann E. MORIN wrote:
> Yann E. MORIN (6):
> arch/arm: add cortex-m7 core
> arch/arm: introduce generic FPU internal option
> arch/arm: add option for FPv4 FPU
> arch/arm: add options for FPv5 FPU
> arch/arm: cortex-m4 may have an FPv4 FPU
> arch/arm: cortex-m7 may have a FPv5 FPU
Entire series applied to next.
As discussed on IRC, I initially screwed up and applied PATCH 1/6 on
the master branch, so I reverted it, and applied the whole thing on the
next branch.
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 17:22 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
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 ` Thomas Petazzoni [this message]
2018-05-20 17:27 ` [Buildroot] [PATCH 0/6] arch/ar: add cortex-m7, and cortex-M FPUs 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=20180520192243.207524ca@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 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.