-
Notifications
You must be signed in to change notification settings - Fork 165
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
chore(drivers): add a warning for not officially supported archs #421
chore(drivers): add a warning for not officially supported archs #421
Conversation
fae8122
to
973b32f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
IMHO this is a big step forward: declaring the officially supported architectures with a cmake warning is the best possible.
LGTM label has been added. Git tree hash: 7fddc769352f93242bacf23b00d513a2510ed7ee
|
Signed-off-by: Andrea Terzolo <andrea.terzolo@polito.it>
973b32f
to
7491566
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Andreagit97, FedeDP The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
LGTM label has been added. Git tree hash: d8ece2a8ef04f3f1b92171a9a709d4e59e72c1e9
|
/cc @leogr |
Signed-off-by: Andrea Terzolo andrea.terzolo@polito.it
What type of PR is this?
/kind documentation
Any specific area of the project related to this PR?
/area build
What this PR does / why we need it:
This pull request wants to clarify which are officially supported. This doesn't mean that all other architectures won't work it only suggest that we are focusing our efforts on the officially supported ones.
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?: