He changed the code. He did commit. He pushed it. Then you pulled it. And now you see his commit in the log. Why would you want to inform him that he did a change that you see? It's 100% normal. Move on.
If you are worried because you were in the middle of some changes, and in the meantime he changed something - OK. It's normal too. But he was faster. It is now up to you to review and merge/rebase/commit such code that will be safe and valid not only with your 'starting point' but also with his changes. That's the basic assumption of 'merge' that must happen at some point of time between branches (or even the same branch when different people work on it).
The most important thing is that if you were working on different files/lines, then GIT will probably merge them automatically. It may go silently. Still, it's your business logic, so you should review, just for the small probability of him doing something that breaks your current unpublished code.