Nah, I just took an example from the file that defines the device & vendor ID; if you look at the actual driver it’s very clearly an intentional obfuscation:
if
(
l1000000001
==
NULL
)
{
printk
(
"\045\144\040\157o\160s \165sb\137s\145ri\141l_\160o\162\164 \160\157i\156t\145r\040i\163 \116UL\114\012"
,
__LINE__
)
;
return
;
}
l1000001100
=
l1000000001
->
serial
;
so you’re right that it’s sticking a newline after each token, but it’s also replacing those indentifiers that it can with generated ones, scrambing strings, etc.