From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] openblas: bump version to v0.2.20
Date: Sun, 1 Apr 2018 12:04:01 +0200 [thread overview]
Message-ID: <20180401120401.3c0c6cbb@windsurf> (raw)
In-Reply-To: <20180401084642.15199-2-peter@korsgaard.com>
Hello,
On Sun, 1 Apr 2018 10:46:42 +0200, Peter Korsgaard wrote:
> +The other flags, such as -mfpu=vfp or -mfloat-abi=hard are kept, as they
> +are actually required for the build to proceed (OpenBLAS uses VFP
> +instructions, and assume an EABIhf ABI).
> +
> +[Peter: update for v0.2.20
This is going to be the most useless e-mail, but here is a minor nit:
missing closing bracket.
I'm just going to add a few more sentences here, just to pretend this
e-mail is not just about this small nit. But I don't have much else to
say about this patch. Oh well, the length of this text starts to justify
this e-mail. I can probably stop here, and put my usual closing Best
regards, so let's do this.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-04-01 10:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-01 8:46 [Buildroot] [PATCH 1/2] openblass: drop SSE_GENERIC target Peter Korsgaard
2018-04-01 8:46 ` [Buildroot] [PATCH 2/2] openblas: bump version to v0.2.20 Peter Korsgaard
2018-04-01 10:04 ` Thomas Petazzoni [this message]
2018-04-01 10:28 ` Peter Korsgaard
2018-04-01 10:45 ` Peter Korsgaard
2018-04-01 9:51 ` [Buildroot] [PATCH 1/2] openblass: drop SSE_GENERIC target Arnout Vandecappelle
2018-04-01 10:38 ` Peter Korsgaard
2018-04-01 10:45 ` Peter Korsgaard
2018-04-08 15:08 ` Peter Korsgaard
2018-04-11 15:46 ` Peter Korsgaard
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=20180401120401.3c0c6cbb@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.