Dear all,
I started to follow up this topic.
Found that one in sam_hsmci.c:
/* There is some unresolved issue with the SAMV7 DMA. TX DMA is currently
* disabled.
*/
#undef HSCMI_NORXDMA /* Define to disable RX DMA */
*#define HSCMI_NOTXDMA1 /* Define to disable TX
On Sat, Feb 12, 2022 at 2:32 AM 张铎(Duo Zhang) wrote:
>
> It depends. We need to start a discuss thread on the incubator-general
> mailing list to see if IPMC members have any concerns.
Hi all,
I suggest we go ahead and start that thread. Does anyone need more time first?
Cheers,
Nathan
I really think we need to address the existing feedback from the last two
releases before we go asking for more.
We also need to go through the process of a release without the WIP
disclaimer which should also solicit some of the remaining feedback.
--Brennan
On Mon, Feb 14, 2022, 9:00 AM Nathan
I am opening this discussion to widen the audience for feedback on the
rules for merging. The original interexchange was in [1]
1 ) Given the geographical and time differences should we consider that
once a review with approval* has been done the PR’s author can merge it?
2) Should we conside
my last commits will arrive this week then if there are no other concerns I
would suggest that someone runs FOSSID and verifies independently that I
did not miss anything.
If we all agree that the feedback was addressed I can start a new release
process without the WIP disclaimer
Best regards
Ali
PR 5399 adds an Kconfig option for NDEBUG. The salient discussion begins at
[2] there are mixed positions and reasoning. xiaoxiang781216 asked me to
raise a discussion on this.
The reasoning for the Default state of to be NDEBUG (n) hence undefined so
that assert() enabled is the following:
1
On Mon, Feb 14, 2022, 9:28 AM David Sidrane wrote:
> I am opening this discussion to widen the audience for feedback on the
> rules for merging. The original interexchange was in [1]
>
>
>
> 1 ) Given the geographical and time differences should we consider that
> once a review with approval* has
