Fabio Baltieri

Hi Doka, unfortunately I've never written a proper documentation for this project, and I realized it's a bit misleading, but I actually never built the rev2 of this project -...

Yes, that code was written with a proper interrupt implementation in mind, but just by keeping the ISR code in the main loop (with irq disabled), so when you set...

> 2. I was asked to keep the steps separate in different commits. You can get a single top level view at https://github.com/zephyrproject-rtos/zephyr/pull/48846/files but other people find it easier to...

Hey I tagged this for v3.3.0, let us know if the update is to fix a security issue or something that should go for v3.2.0 instead.

The release is scheduled for the 30th (https://github.com/zephyrproject-rtos/zephyr/wiki/Release-Management), it's more a matter of whether there's something critical in there.

@ektor5 we don't use fixup patches in Zephyr PRs, patch series that represent the development history or aid reviewability are good, but review fixup should get amended to the original...

> @fabiobaltieri no problem, I thought it could be done from Github once approved. It could in this case since this would be a single patch PR, but in general...

@yperess can you re-review this? (you have a pending blocking comment)

> @cfriedt, @fabiobaltieri any chance of this gets merged in this release, we are organizing an Zephyr session based on this educational board. We are in stabilization phase so we'd...

TSC decided to hold this for after the release. Updated the milestone tag accordingly.