This is probably the last thing to do, submitting now, so we had an overview of what lies ahead ;-).
So, Zephyr codestyle is to use tabs for indentation. Stuff in samples/net/google_iot_device/ uses 2 spaces for indentation. I doubt there's way around adhering to Zephyr codestyle (check runs as initial phase of CI, which will mark it red).
Hopefully reformatting is acceptable for bsp/ too, because otherwise we'd have to make it a west submodule too.
Beyond whitespace, there're other minor (but noticeable) style discrepancies, e.g. Zephyr function style is:
This is probably the last thing to do, submitting now, so we had an overview of what lies ahead ;-).
So, Zephyr codestyle is to use tabs for indentation. Stuff in samples/net/google_iot_device/ uses 2 spaces for indentation. I doubt there's way around adhering to Zephyr codestyle (check runs as initial phase of CI, which will mark it red).
Hopefully reformatting is acceptable for bsp/ too, because otherwise we'd have to make it a west submodule too.
Beyond whitespace, there're other minor (but noticeable) style discrepancies, e.g. Zephyr function style is:
(Open brace placement.)