Be careful what you wish for, Kansas City Chiefs fans.
This will be welcomed news for many Chiefs fans.
Stuck in the midst of some terrible quarterback play by starter Matt Cassel, many fans have been calling for Quinn to get his shot. This led to the "sickening" situation described by Eric Winston in this postgame interview.
It is no surprise the backup QB in Kansas City is popular. Cassel has a QB rating of 66.2 and his 14 turnovers are more than even Michael Vick.
But at some point, the reality has to sink in that the man that Chiefs fans are clamoring to take over signal-calling duties is Brady Quinn, and that is nothing to wish for.
The six-year pro out of Notre Dame got his most significant playing time in 2009 when he was the Browns' main starter and he played in 10 games.
His QB rating of 67.2 was so impressive that he has not earned a single start since.
Quinn's head coach and offensive coordinator in 2009? The same he has now: Romeo Crennel and Brian Daboll.
So the two men who are as aware of Quinn's strengths and weaknesses as anyone have felt it was best to keep Quinn on the bench while Cassel performs terribly. That is not a good sign for Quinn's chances.
The Chiefs were so down on Cassel that last week they only had Cassel throw seven first-half passes, and they ended the game running 50 rush plays vs. attempting 18 passes.
And despite having that little confidence in Cassel, they kept Quinn firmly on the bench until Cassel could no longer play.
So Chiefs fans hoping that Quinn will spark some life into the passing game are going to be severely disappointed. It will be more of the same, just a shade worse.
In fact, as Moore points out, in Quinn's last start, the play calling was shockingly similar to last week's game. Cleveland had 49 rushing attempts while Quinn only threw 17 passes.
Kansas City fans will be best served just to ignore who is playing QB this year and focus their energy on wishing running back Jamaal Charles good health.