Everyone has very well explained, how you should handle this scenario. And trust me; at some point almost every tester come across similar situation.
So, my suggestion is:
1. Don't get upset about it. And don't get discouraged. Keep yourself motivated.
2. Ideally, project team (which includes both developers and testers) is responsible for delivering high quality end product. So, QA should not be discouraged from raising bugs. Even if he is not logging bugs in a particular way, then message should be passed politely ensuring that QA doesn't get discouraged.
I had a QA friend who faced similar situation. He talked to his manager about it. Manager reviewed the defects logged by him and suggested to club the similar bugs into 1.
My friend was doing a great job and reporting everything that was valid.
But, after this incident, he changed a lot. He would quickly give up any discussion around bugs with the development team, instead of bringing in logical points in the discussion. Sometimes, he would give in to the pressure from developers and even once closed the bugs under pressure.
These things are not good.
So, just wanted to share this with you. Whatever happens, just stay strong and keep reporting bugs as you have always done so far.
You have to do your job whether this particular developer like it or not.
And from my experience of working with developers, I can confidently tell you that good developers always encourage the tester to raise bugs. I have instances where even developers ask you to log a bug if they see any unexpected behavior. And this is how it should be. The end goal for both developers and testers is to improve the quality together