-
-
Notifications
You must be signed in to change notification settings - Fork 3.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
[nuvo] Fix Nuvo Grand Concerto Detection #12613
Conversation
9c8a778
to
48ee3dc
Compare
Signed-off-by: Brian OConnell <broconne@gmail.com>
48ee3dc
to
19eca56
Compare
FYI - I attempted to fix the DCO - but not sure why it is still unhappy with my signoff. |
There seems to be some inconsistency:
and: |
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.
LGTM
The first dco issue was that it doesn't like my email address, so I changed it. At this point not sure how to resolve it. |
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.
LGTM
@jlaur: do you have an idea? |
@lolodomo - we can fix sign-off when squash-merging. @boc-tothefuture, which e-mail address is the correct one? |
Done. I considered broconne@gmail.com is valid. |
Signed-off-by: Brian OConnell <broconne@gmail.com> Signed-off-by: Nick Waterton <n.waterton@outlook.com>
Signed-off-by: Brian OConnell <broconne@gmail.com>
Signed-off-by: Brian OConnell <broconne@gmail.com> Signed-off-by: Andras Uhrin <andras.uhrin@gmail.com>
Signed-off-by: Brian OConnell <broconne@gmail.com>
The binding has a typo in detecting grand concerto systems - I noticed this because my clock was not being set correctly. This PR fixes the typo and also adds debug logging to determine if a GC is detected or not.