[riot-notifications] [RIOT-OS/RIOT] Possible memset optimized out in crypto code (#10751)

Martine Lenders notifications at github.com
Wed Jan 16 20:18:01 CET 2019

> Do we have a general policy in RIOT for this? It's fine
to include a lump of vendor code in RIOT, but there will
always a time that it needs to be modified or updated.
> I see at least two problems.
> 1. you don't want to duplicate upstream work
> 2. you don't want to make too many changes that complicate
future updates
We want a simple update procedure for upstream changes.
Do we have that? (Not just the wpa-supplicant, but all vendor
> Did we record exactly where the code came from and what version
it was when it was copied?

The canonical way to include external code are `pkg`s. But I understand that for vendor files this might not possible (usually this were just headers though in the past). On the other hand we do this for `efm32`-based boards to a degree already with `gecko_sdk`.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190116/8b971e10/attachment.html>

More information about the notifications mailing list