From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next] package/fftw: bump version to 3.3.6-pl2
Date: Sun, 28 May 2017 15:42:32 +0200 [thread overview]
Message-ID: <20170528154232.012cf26b@free-electrons.com> (raw)
In-Reply-To: <20170528133151.6604-1-bernd.kuhls@t-online.de>
Hello,
On Sun, 28 May 2017 15:31:51 +0200, Bernd Kuhls wrote:
> Added sha256 hash.
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
Applied to next.
> Platform options need major rework, please refer to
> http://patchwork.ozlabs.org/patch/661673/ for details.
Would indeed be nice to solve this problem at some point in the future.
The best would be if fftw build system was fixed to be able to generate
the different "versions" in one build pass rather than having to create
multiple Buildroot packages.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-05-28 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-28 13:31 [Buildroot] [PATCH/next] package/fftw: bump version to 3.3.6-pl2 Bernd Kuhls
2017-05-28 13:42 ` Thomas Petazzoni [this message]
2017-05-28 13:43 ` Thomas Petazzoni
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=20170528154232.012cf26b@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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