On Thursday 30 October 2014 12:52:58 Daniel Mack wrote: > On 10/30/2014 12:26 PM, Arnd Bergmann wrote: > > On Thursday 30 October 2014 12:02:39 Tom Gundersen wrote: > > >> The nice thing about enums is of course that it helps with debugging > >> as gdb can show the string representation rather than the number, > >> because in contrast to #defines, an enum is something the compliler > >> knows about. > > > > This doesn't get passed as an enum in user space though, and when debugging > > the kernel it only helps within one function. > > Hmm, this is the header exported to userspace, so having enums in would > make our lives easier, right? My point was that you never use the enum by type and the only place in user space where it's referenced would be something like ret = ioctl(fd, KDBUS_CMD_BUS_MAKE, &make); In the debugger, you will see the source line here. If you trace into the glibc ioctl function, you no longer know the type because that just has an 'int'. > Hence, for now, I'd propose we keep it the way it is, and add new ioctls > with defines once they are implemented. Are you okay with this? I'll add > a comment to the file to give a heads-up. It's certainly not a show-stopped, but I have yet to see a good reason why it would help anyone. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
