From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Peter Seiderer <ps.report@gmx.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1] package/fft_eval: new package
Date: Sat, 12 Aug 2023 00:23:45 +0200 [thread overview]
Message-ID: <20230812002345.660aea04@windsurf> (raw)
In-Reply-To: <20230811212220.52d4ffb9@gmx.net>
On Fri, 11 Aug 2023 21:22:20 +0200
Peter Seiderer <ps.report@gmx.net> wrote:
> > I've use "make install" instead of doing the manual installation here.
>
> Looks nicer..., but now the variable FFT_EVAL_TARGETS is unused?
Dammit, indeed. One of us needs to send a follow-up patch :-)
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-08-11 22:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 16:34 [Buildroot] [PATCH v1] package/fft_eval: new package Peter Seiderer
2023-08-10 22:07 ` Thomas Petazzoni via buildroot
2023-08-11 19:22 ` Peter Seiderer
2023-08-11 22:23 ` Thomas Petazzoni via buildroot [this message]
2023-08-12 13:33 ` 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=20230812002345.660aea04@windsurf \
--to=buildroot@buildroot.org \
--cc=ps.report@gmx.net \
--cc=thomas.petazzoni@bootlin.com \
/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