Fix logic bug in cache_nvidia_string_value_update()

[w0j0pl]

Checklist

• I have described the changes
• I have linked to any relevant GitHub issues, if applicable
• Documentation in doc/ has been updated
• All new code is licensed under GPLv3

Description

• Describe the changes, why they were necessary, etc
• Describe how the changes will affect existing behaviour.
• Describe how you tested and validated your changes.
• Include any relevant screenshots/evidence demonstrating that the changes work and have been tested.

[netlify]

✅ Deploy Preview for conkyweb canceled.

Name	Link
🔨 Latest commit	5851be9
🔍 Latest deploy log	https://app.netlify.com/sites/conkyweb/deploys/66cf4dc8dee60c00084cb5f0

[brndnmtthws]

Are we certain this is the correct fix?

[w0j0pl]

I read what the z1atk0 guy wrote, checked this and for me it doesn't make any sense to check if memTransferRatemax is cached or not if we want to cache perfmin or perfmax. It makes sense to check if perfmin is cached if we want to know wether or not we should cache it. And the same story with perfmax.

Also if you check all of the else ifs right above this one, you will see that the we check if something is cached, before we cache this thing. For me it looks like copy/paste, but someone forgot to change memTransferRatemax in the second place.

I won't give you 100% certainty, because I'm just a noobie and it's my 2nd change in such a big project, but for me everything looks fine.