Currently, the top of the aosp/external/libchrome repository includes these patches:

8263a04 libchrome: Removed Chrome OS license check
5943df7 Cherry-pick "Allow PolicyLoadStatusSample to override reporting method"
c3f34a3 libchrome: Uprev the library to r456626 from Chromium
7b88bc8 Add build options to skip some libraries

Patch c3f34a3 was a partial full-scale update of libchrome to latest code from Chromium [partial due to no crypto update, b/c Chromium now uses boringssl instead of openssl].  The patch was reviewed at:
https://chromium-review.googlesource.com/#/c/479777/

However, libchrome is a very funny cros_workon package, that requires a manual update to "CROS_WORKON_COMMIT" for changes in the repository to take effect.
Since there was never a corresponding revbump in the libchrome, the libchrome ebuild still points to 7b88bc8, and all patches beyond that are not being used.

In fact, this was noticed by ljusten when landing 5943df7 (https://chromium-review.googlesource.com/#/c/497433/), so this patch is actually now being applied by the libchrome ebuild itself (see https://chromium-review.googlesource.com/#/c/497434/).

It isn't clear from CL:479777 why there was no ebuild revbump, and there is no BUG=, so the trail grew cold.
If it will take a while longer before we plan to update CROS_WORKON_COMMIT in the ebuild, perhaps we can just revert c3f34a3 for now, and then we can also remove the ebuild-applied patch for 5943df7.