On Thu, 2018-03-15 at 13:29 +0100, Ulf Hansson wrote: > On 15 March 2018 at 11:26, Andy Shevchenko > <andriy.shevchenko@xxxxxxxxxxxxxxx> wrote: > > On Thu, 2018-03-15 at 11:12 +0100, Ulf Hansson wrote: > > > On 13 March 2018 at 06:10, Harish Jenny K N <harish_kandiga@mentor > > > .com > > > > wrote: > > > > > > > Honestly, I don't like this, but maybe other people do, then I am > > > fine > > > with this approach. > > > > > > If were to decide, I would just rather print the caps field in a > > > hexadecimal bit form and leave the translation to the user. > > > > A compromise would be to print both: > > > > 0xHHHHHHHH\n > > Description of each enabled field, one per line > > > > > > Another format would be: > > > > Bit XX: Description of a field > > If we were to print the description, there is no point in printing the > bits in hex. Or is it? It is helpful for scripting (since it's debugfs, under scripting I mean something rather for test suites than for actual use). > As I said, if you and other folkz thinks this is valuable, then I am > fine as well. Just saying, it's not my preferred option. -- Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx> Intel Finland Oy -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html