Update nss_revision to 90c5f9a8b8980fe60165813f578bbeb4fe20b18d.

Update nss_revision to 90c5f9a8b8980fe60165813f578bbeb4fe20b18d.

Include the following CLs:

Avoids MSVC warnings about possible value truncation.
https://codereview.chromium.org/515383002/

TBR=agl@chromium.org,pkasting@chromium.org
BUG=

Committed: https://crrev.com/f18c55f27791d672d4b8d4f30e960a912c7899cc
Cr-Commit-Position: refs/heads/master@{#292688}

[wtc, 2014-08-28 23:30:18]

My NSS source tree was configured to use git-svn. I looked up the git commit
revision at
http://git.chromium.org/gitweb/?p=chromium/deps/nss.git;a=commit;h=90c5f9a8b8...

[wtc, 2014-08-29 18:12:20]

The CQ bit was checked by wtc@chromium.org

[commit-bot: I haz the power, 2014-08-29 18:13:36]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/wtc@chromium.org/521463002/1

[commit-bot: I haz the power, 2014-08-29 19:30:38]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  win_chromium_x64_rel_swarming on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[commit-bot: I haz the power, 2014-08-29 22:20:43]

Committed patchset #1 (id:1) as 6ffb4d6df7cef361dcb56900adf828fdb37c3ecd

[commit-bot: I haz the power, 2014-09-10 03:10:43]

Patchset 1 (id:??) landed as
https://crrev.com/f18c55f27791d672d4b8d4f30e960a912c7899cc
Cr-Commit-Position: refs/heads/master@{#292688}