Rohit Sharma complains to BCCI against legendary Sunil Gavaskar's negative criticism? Here's what reports say

Legendary Sunil Gavaskar is known for his straightforward analysis, whether of a match or an individual player. The former India captain was no different during the Border-Gavaskar Trophy (BGT) in Australia, where the 75-year-old criticised the Indian batters for their poor show throughout the series. India lost 1-3.

In a report by CricBlogger, Rohit Sharma complained to the BCCI top brass about Sunil Gavaskar's negative criticism in one of their meetings, stating that the external pressure impacted his performance.

“Rohit felt that it was not necessary for Sunil Gavaskar to criticise him in that fashion, and that’s why he complained to the BCCI about Gavaskar,” CricBlogger reported a source as saying.

After missing the first Test due to the birth of his second child, Rohit could score just 31 runs in the next three Tests before dropping himself from the final Test in Sydney.

As Rohit Sharma struggled with the bat, Gavaskar remarked that the right-hander might step down and not wait for the selector's call “if he doesn’t score runs in Melbourne and Sydney”.

“The skipper, Rohit Sharma, was out of his depth and having taken the brave decision to step aside, because of his form, he has also raised big questions about his future in Test cricket,” the Little Master had written in his column for The Sydney Morning Herald during the tour.

Gavaskar had also stated that Jasprit Bumrah should have led India in the series against Australia after Rohit missed the first Test in Perth. 

“All these added so much pressure that he was compelled to tell it all to BCCI,” the source added.

The development of Rohit Sharma complaining about Sunil Gavaskar came after the two shared the stage at the Wankhede Stadium during Mumbai Cricket Association's 50th-anniversary celebrations earlier this month.

Rohit's flop show continues 

To address his batting woes, Rohit Sharma played a Ranji Trophy match for Mumbai after 10 years. However, his batting woes continued as the Indian captain managed just 31 runs in a losing cause against Jammu and Kashmir.