Closed jamesmunns closed 6 years ago
bors r+
It seems this never ran because the svd2rust PR took too long.
bors r+
Actually I forgot to commit the bors-ng integration
bors r+
Not awaiting review
bors r-
bors r+
pushed a no-op change to see if that unstucks bors
bors r+
bors r-
Found a problem in the bors.toml file. It should be fixed now.
bors r+
For higher frequency devices (such as the nRF52 at 64MHz),
1 << 24
ticks is only 250ms or so. Allow longer delays if necessary.