Most of my lint warnings aren't false positives though, they're potential issues. Most of my time sorting through lint warnings is addressing the warnings for potential issues.
The potential for an issue may be legitimate, but that doesn't make it a false positive.
Some lint tools are better than others about it. Potential is not enough - there needs to be a clear fix that shuts up the warning and makes the code function as intended (which may be different than as I wrote it!). The tool I'm thinking of didn't have that, so we regularly silenced warnings, and then a few years of that and the habit became to not even bother looking at what the warning was, just silence it.
If there is a clear fix that makes the code objectively better then I'm for the tool. However if it warns about correct code because of a potential issue that doesn't even apply that is a false positive.
Don't forget that real errors you fix will disappear so even a few false positives are bad because you see them all the time and so they seem worse than they are.
Now that our tools have a zero false positive policy we can require all attempts to silence warnings are allowed only after a bug report is opened with the tool. Everytime we upgrade we grep and remove the silence warning comments for things fixed.