I'd prefer just plain ASCII 'I2C' here, but either way: Acked-by: Rob Herring <robh@xxxxxxxxxx> Rob -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a message to
checkpatch works on patches so I think the test isn't really relevant. It has to use the appropriate email header that sets the charset. perhaps: -- scripts/checkpatch.pl | 10 +++++++-- 1 file change
There are a couple of files that my version of 'find' incorrectly identified as something completely different, like: Documentation/devicetree/bindings/pinctrl/pinctrl-sx150x.txt: SemOne archive data
... ... Acked-by: Michael Ellerman <mpe@xxxxxxxxxxxxxx> (powerpc) cheers -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx
I'm using this, seems to work. if ! file $p | grep -q -P ", ASCII text|, UTF-8 Unicode text" then echo $p: weird charset fi -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in
[] How would that be done? -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/
For IIO, Acked-by: Jonathan Cameron <Jonathan.Cameron@xxxxxxxxxx> Thanks for tidying this up. Jonathan -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a message
kconfig tools prefer ASCII or utf-8. email tools probably likewise. user sanity? -- ~Randy -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a message to majordom
Was "consistency" the only rationale? The discussion is now outside my memory horizon but I thought there were other reasons. Will we be getting a checkpatch rule to keep things this way? -- To unsub
IPVS portion: Acked-by: Simon Horman <horms@xxxxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo
Almost all files in the kernel are either plain text or UTF-8 encoded. A couple however are ISO_8859-1, usually just a few characters in a C comments, for historic reasons. This converts them all to