What about lib/comms or lib/net ?

Are there continuous builds of the SDK in jenkins? Not seeing anything and was hoping to grab a “nightly” snapshot out of there. - k

Shouldn’t all of ext/ be excluded from checkpatch? Seems like ext/lib will have same issues. - k

We should probably document rules on import in ext/README. Mostly around documenting to origins of the code import (i.e., what should be in a commit message, what meta file that documents the source o

Why do we need this change if we intend to point the include path to be cmsis/Include. I don’t think we should be changing this. It should get hidden by something like: subdir-ccflags-$(CONFIG_CMSIS)

Anas, I’ve got a patch that cleans up all the whitespace issues is the Kconfig files. Think we should try and merge this sooner than later, to reduce propagation of this issue going forward. I think b

I think this should really just be posted on the list. We are taking gerrit too far for an RFC of this nature. - k

This appears to be taken directly from the Linux Kernel makefile, any idea why that was added over there? What all is in CLANG_FLAGS? Guessing this might be best added in scripts/Makefile.toolchain.cl

Anas, Do you know why the fstat and _fstat implementations are slightly different in lib/libc/newlib/libc-hooks.c. Specifically why fstat() sets buf->st_blksize = 0? int fstat(int fd, struct stat *buf

Great, sent a patch series that does that and fixes up the newlib support to deal with other toolchains better. - k

KBUILD_ZEPHYR_APP isn’t documented anywhere so wondering what’s it intent was and how it differs from SOURCE_DIR? - k

Not sure I get exactly what the point of KBUILD_ZEPHYR_APP based on the github you pointed at. Are we ok with removing it for now, maybe enter a new Jira ticket with the details of what functionality

I was wondering who was best to ask about the toolchains in the Zephyr SDK. One question I had was what is the history behind the following patch in meta-zephyr-sdk: recipes-devtools/gcc/files/0042-ar

I think the application of this API needs to be much clearer. What use cases are their from the application side? - k

I still don’t see the point of this API at all. In the ZEP it mentions using for entropy source or for MAC address creation. I don’t think this ID is a good choice for either purpose. I still don’t se

When you say unique target identity, how unique are you meaning. The sense I got was this API would give me the same value for two different instances of the same board (HW, SoC, assuming same rev’s o

The use case you specify of picking SOC-version-specific code at run-time should be using features and not an ID for determining such things. This goes directly to Tixy’s email thread which I agree wi

If what you are talking about is really for errata than I think we should solve that specific problem. I think a combination of a consistent #define naming and usage convention: #define CONFIG_ERRATUM

Was it expected that the interface was for kernel code only? If so, I think its fair game to remove. If this was intended for some application code, we should probably come up with with a documented p

What version of the SDK are we using in CI? - k