On Mon, Oct 16, 2023 at 11:25:12AM -0500, Bjorn Helgaas wrote: > On Mon, Oct 16, 2023 at 12:11:04PM -0400, Frank Li wrote: > > On Mon, Oct 16, 2023 at 10:22:11AM -0500, Bjorn Helgaas wrote: > > > > Obviously Lorenzo *could* edit all your subject lines on your behalf, > > > but it makes everybody's life easier if people look at the existing > > > code and follow the style when making changes. > > > > Understand, but simple mark 'a' and 'A' to me. I will update patches and > > take care for next time instead search whole docuemnt to guess which one > > violated. I know I make some mistakes at here. But I am working on many > > difference kernel subsystems, some require upper case, some require low > > case, someone doesn't care. > > Right, that's why I always suggest following the example of the > surrounding code and history. English is the only language I know, > but I speculate that this typographical detail probably doesn't make > sense in languages that don't have a similar upper/lowercase > distinction. If everyone thinks it is important. I suggest put it in checkpatch.pl script. The only script check can prevent to human make mistakes. I asked the same question at: https://lore.kernel.org/imx/ZSV1sINV%2F2GrAYFr@lizhi-Precision-Tower-5810/T/#t It lets teach kid mulitplication, kid did 20 questions. only 1 failure. The good teacher should tell which one is wrong and grade as 19/20 instead of just grade 19/20 without any comments. We are using email communication instead of face to face. The efficient of communication is important. We have differece background, difference native languadge, live on difference area in world and do the same jobs to make linux kernel better. The simple and straight forward's feedback can save both our time and efforts. Frank Li > > Thanks for persevering; we'd be having a lot more trouble if I tried > to send emails in your native language ;) > > Bjorn
