mac: s/UINT32_MAX/kuint32max/

mac: s/UINT32_MAX/kuint32max/

Needed to build on 10.5, which is in turn needed for coverity.

BUG=none
TEST=none

[Ryan Sleevi, 2011-12-07 00:43:40]

LGTM, but you'll need to get a net/ OWNERs to rubberstamp or TBR it.

[willchan no longer on Chromium, 2011-12-07 00:45:03]

LGTM

On Tue, Dec 6, 2011 at 4:43 PM, <rsleevi@chromium.org> wrote:

> LGTM, but you'll need to get a net/ OWNERs to rubberstamp or TBR it.
>
>
http://codereview.chromium.**org/8828010/<http://codereview.chromium.org/8828...
>

[commit-bot: I haz the power, 2011-12-07 00:45:49]

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

[commit-bot: I haz the power, 2011-12-07 02:51:19]

Commit queue had an internal error.
Something went really wrong, probably a crash, a hickup or
simply the monkeys went out for diner.
The relevant dude was pinged already.

[commit-bot: I haz the power, 2011-12-07 02:52:56]

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

[commit-bot: I haz the power, 2011-12-07 02:52:57]

Can't apply patch for file net/base/x509_certificate_mac.cc.
While running patch -p1 --forward --force;
patching file net/base/x509_certificate_mac.cc
Hunk #1 FAILED at 722.
1 out of 1 hunk FAILED -- saving rejects to file
net/base/x509_certificate_mac.cc.rej

[ramant (doing other things), 2012-02-14 04:56:21]

looks like commit-bot failed to commit. Should we consider manually committing
or give commit-bot one more chance? thx

[Nico, 2012-02-14 16:16:19]

Looks like the change did make it into the file somehow. Maybe I committed this
manually, I don't remember. Closing this issue.