On Fri, 26 Apr 2019, Kai-Heng Feng wrote:

quoted

Ronald (Cc-ed) raised quite a good point:
what's the benefit of removing the error message if this function (and
__extract) can only report an unsigned 32 bits value?

I didn’t spot this, sorry.

quoted

My take is we should revert 94a9992f7dbdfb28976b upstream and think at
a better solution.

I think using a new fix to replace it will be a better approach, as it at
least partially solves the issue.

Guys, did this fall in between cracks? Is anyone planning to send a fixup?

Thanks,

-- 
Jiri Kosina
SUSE Labs