src/SPILock.cpp

#include "SPILock.h"
#include "configuration.h"
#include <Arduino.h>
#include <assert.h>

concurrency::Lock *spiLock;

void initSPI()
{
    assert(!spiLock);
    spiLock = new concurrency::Lock();
}
If display is on on the @BigCorvus board and we xmit the board browns out? 2020-08-28 17:38:23 -07:00			`#include "SPILock.h"`
trunk roundhouse kick 2023-01-21 14:34:29 +01:00			`#include "configuration.h"`
If display is on on the @BigCorvus board and we xmit the board browns out? 2020-08-28 17:38:23 -07:00			`#include <Arduino.h>`
			`#include <assert.h>`

			`concurrency::Lock *spiLock;`

Revert "add a .clang-format file (#9154)" (#9172) I thought git would be smart enough to understand all the whitespace changes but even with all the flags I know to make it ignore theses it still blows up if there are identical changes on both sides. I have a solution but it require creating a new commit at the merge base for each conflicting PR and merging it into develop. I don't think blowing up all PRs is worth for now, maybe if we can coordinate this for V3 let's say. This reverts commit 0d11331d185a60adf84e64ec98642baf6a15a95a. 2026-01-04 12:15:53 +01:00			`void initSPI()`
			`{`
			`assert(!spiLock);`
			`spiLock = new concurrency::Lock();`
If display is on on the @BigCorvus board and we xmit the board browns out? 2020-08-28 17:38:23 -07:00			`}`