On Thu, Sep 28, 2023, Michal Luczaj wrote: > On 9/27/23 22:10, Sean Christopherson wrote: > > On Tue, Aug 15, 2023, Michal Luczaj wrote: > >> On 8/15/23 00:08, Michal Luczaj wrote: > >>> I understand that typo fixes are not always welcomed, but this > >>> kvm_vcpu_event(s) did actually bit me, causing minor irritation. > >> ^^^ > > > > FWIW, my bar for fixing typos is if the typo causes any amount of confusion or > > wasted time. If it causes one person pain, odds are good it'll cause others pain > > in the future. > > OK, do you want me to resend just the kvm_vcpu_event(s) fix? > (and, empathetically, introduce a typo in the changelog proper :P) Oh, no, sorry. I'll take this as-is. Opportunistically fixing misspellings like you did it totally fine, especially since this is documentation. What I was trying to say is that if a patch fixes a real issue for someone, I'll definitely take the time to get it applied. I didn't mean to say I wouldn't take other typo fixes (though I am inclined to leave code/comments alone if a typo is benign, in order to reduce the churn in git history).
