USC stuns Ohio State as Riley shows emotional side after win
Summarised from 2 outlets · Updated 1 Nov, 21:26 · Archive
USC defeated second-ranked Ohio State 30-18 on Saturday, with coach Lincoln Riley displaying animated reactions on the sideline.
USC defeated second-ranked Ohio State 30-18 on Saturday at the Los Angeles Coliseum. The Trojans' (7-2) victory was particularly notable given the Buckeyes' strength, as Ohio State (6-2) deployed a top-three defence and started backup quarterback Luke Fahey, though the team still entered as favourites.
The win reversed a tumultuous period for USC and coach Lincoln Riley. The previous Saturday, the Trojans scored just seven points in a loss to Wisconsin, prompting speculation about Riley's future at the programme. Fox News reports that USC's athletic department had begun arranging funds for a potential $70 million buyout.
Riley's emotions were evident after the final whistle. Video captured him saying 'Are you kidding me? F*** you!' as players and staff rushed into the tunnel. He appeared to exchange words with Ohio State coaches during the commotion. Addressing media afterwards, Riley said 'This program is built on internal joy, not external applause.'

How it is being reported
- Lincoln Riley has confrontation with Ohio State AD, reads prepared statement to media after huge USC winThe USC Trojans stunned the No. 2 Ohio State Buckeyes just days after a dismal loss to Wisconsin, capping a wild week for Lincoln Riley's program.Fox News · 1 Nov, 20:05
- USC head coach Lincoln Riley caught in foul-mouthed 'f*** you' tirade at after upsetting Ohio StateTrojans head coach Lincoln Riley had some notable words after USC's stunning upset of injury-plagued Ohio State on Saturday at the Los Angeles Coliseum.Daily Mail Sport · 1 Nov, 15:06
In this story: Lincoln Riley · USC · Ohio State · Los Angeles Coliseum · Wisconsin · Luke Fahey
This summary was written by AI from the headlines and standfirsts above, and states as fact only what at least two outlets report. How we use AI · Report a problem · Corrections log
Comments (0)