-
Notifications
You must be signed in to change notification settings - Fork 6.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
boards: rakwireless: Use proper vendor prefix as board folder #80160
Conversation
66eeadc
to
9a4bb5b
Compare
@AlessandroLuo @aaronyegx @RichardSWheatley could you help with the (unrelated) CI issue? AFAICT this warning in the HAL has always been there but I think it's only recently that c++ warnings have been promoted to errors
|
I was always under the assumption that our HAL would not have to conform to Zephyr standards. Why is this now an issue? |
Maybe @fabiobaltieri can chime in as he is the author of #78419 (which I think is why this PR now fails, but not actually sure) |
zephyrproject-rtos/hal_ambiq#34 it's fixed on the module but the manifest is out of date |
Ok, the fix is pending on #79547 |
Thanks much for digging this up! Guess I didn't search thoroughly enough for open issues/PRs |
Well I only found out after doing a PR to fix it myself and trying to figure why it was not mergeable :-) |
I believe the manifest has been updated and merged in #80032 by @AlessandroLuo |
9a4bb5b
to
9ce52c8
Compare
hwmv2 established a convention that boards live in a folder named after the vendor prefix. RAK Wireless boards apparently missed the memo :) Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
9ce52c8
to
d5d6321
Compare
hwmv2 established a convention that boards live in a folder named after the vendor prefix.
RAK Wireless boards apparently missed the memo.