Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: Francis Laniel <flaniel@linux.microsoft.com>,
	buildroot@buildroot.org,
	Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Angelo Compagnucci <angelo.compagnucci@gmail.com>,
	Samuel Martin <s.martin49@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/2] package/tbb: bump to version 2021.5.0
Date: Tue, 19 Apr 2022 22:48:03 +0200	[thread overview]
Message-ID: <cbe24936-565a-09fb-d649-1e4b28cf2078@mind.be> (raw)
In-Reply-To: <4391488.LvFx2qVVIh@pwmachine>



On 19/04/2022 18:32, Francis Laniel wrote:
> Hi.
> 
> Le samedi 16 avril 2022, 22:07:49 BST Fabrice Fontaine a écrit :
>> - Switch to cmake-package
>> - Drop DO_ITT_NOTIFY which is only used in example and test
>> - license file has been renamed to LICENSE.txt
>> - Add upstream patches to fix musl build
>>
>> https://www.intel.com/content/www/us/en/developer/articles/release-notes/int
>> el-oneapi-threading-building-blocks-release-notes.html
>>
>> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>

  Applied to master, thanks.

[snip]
> 
> I tested your patch and it builds succesfully and sysdig (0.27.1) is still
> running like a charm.

  Please formally declare when you reviewed or tested a patch, e.g.

Reviewed-by: Francis Laniel <flaniel@linux.microsoft.com>
Tested-by: Francis Laniel <flaniel@linux.microsoft.com>

This gets picked up by patchwork and tells us it's a patch we should prioritize 
(since someone else already looked at it, we don't need to review it in detail 
any more).


  (Also, if you put text below a very long piece of quoted text, it's nice to 
remove part of the quoted text so the reader doesn't need to scroll as much.)

  Regards,
  Arnout

> So, thank you for the bumping (I should have do it...) and the simplification
> of tbb.mk.
> 
> 
> Best regards.
> 
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-04-19 20:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-16 21:07 [Buildroot] [PATCH 1/2] package/tbb: bump to version 2021.5.0 Fabrice Fontaine
2022-04-16 21:07 ` [Buildroot] [PATCH 2/2] package/opencv4: add tbb support Fabrice Fontaine
2022-04-21 20:53   ` Arnout Vandecappelle
2022-04-19 16:32 ` [Buildroot] [PATCH 1/2] package/tbb: bump to version 2021.5.0 Francis Laniel
2022-04-19 20:48   ` Arnout Vandecappelle [this message]

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=cbe24936-565a-09fb-d649-1e4b28cf2078@mind.be \
    --to=arnout@mind.be \
    --cc=angelo.compagnucci@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=flaniel@linux.microsoft.com \
    --cc=fontaine.fabrice@gmail.com \
    --cc=s.martin49@gmail.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