Given it is a proc macro, we could take normal strings for the fields and ensure they are ASCII if/where needed.
This would make the interface a bit leaner.
For author, it would be particularly fitting anyway, because we would like to allow names requiring UTF-8, such as non-romanized names. There are kernel modules with MODULE_AUTHORs with non-ASCII characters already (and encoded as UTF-8) e.g.
|
MODULE_AUTHOR("周琰杰 (Zhou Yanjie) <zhouyanjie@wanyeetech.com>"); |
|
MODULE_AUTHOR("漆鹏振 (Qi Pengzhen) <aric.pzqi@ingenic.com>"); |
Given it is a proc macro, we could take normal strings for the fields and ensure they are ASCII if/where needed.
This would make the interface a bit leaner.
For
author, it would be particularly fitting anyway, because we would like to allow names requiring UTF-8, such as non-romanized names. There are kernel modules withMODULE_AUTHORs with non-ASCII characters already (and encoded as UTF-8) e.g.linux/drivers/phy/ingenic/phy-ingenic-usb.c
Lines 385 to 386 in 428d64a