Re: clkdev: report over-sized strings when creating clkdev entries