| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 2 Sep 2010 17:23:16 -0300 From: Lucas De Marchi <lucas.de.marchi@...il.com> To: Mike Frysinger <vapier.adi@...il.com> Cc: Randy Dunlap <randy.dunlap@...cle.com>, linux-kernel@...r.kernel.org Subject: Re: [RFC] Fix typos On Thu, Sep 2, 2010 at 17:16, Mike Frysinger <vapier.adi@...il.com> wrote: > On Thu, Sep 2, 2010 at 16:08, Lucas De Marchi wrote: >> On Thu, Sep 2, 2010 at 17:00, Randy Dunlap wrote: >>> It looks good for Documentation/. >>> >>> And fixing typos is certainly something that we want to do in >>> user-visible messages, like printk strings. >> >> What about comments and code? > > i think it's useful to fix typos in those things, but this would def > require a human to review things. it might also be saner to start I agree. This is me :-) > with a whitelist of common typos (doesnt checkpatch have this ?) > rather than doing it against a dictionary. I'm running a script with a dictionary of common typos, not a "normal dictionary". > for example, we've committed a few drivers that used "platfrom" in > their structure names when it should have been "platform". I didn't have this typo, but I can add it as well. -- Lucas De Marchi -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists