Re: [PATCH] mmc: print message if a card supports secure erase/trim

[Alexander Holler <holler@ahsoftware.de>]

Am 27.01.2015 um 18:48 schrieb Steven Rostedt:
> On Tue, 27 Jan 2015 18:38:36 +0100
> Alexander Holler <holler@ahsoftware.de> wrote:
>
>> Anyway, I like(d) Linux because it didn't had a splash screen and used
>> to spit out all types of information on the screen where it could be
>> easily seen or found (in contrast other OS which try to hide all
>> technical details from users).
>
> Yes, I like those days too, but as you say, times are changing, and we
> must adapt.
>
>>
>> Of course, times are changing, including the amount of stuff printed on
>> screen. But I still find it much much easier to grep on the output of
>> dmesg than to search through thousands files in sysfs. Even if that can
>> be done with grep too (kind of). But it's much more complicated because
>> grep doesn't connect the file name with the content, so you need more
>> complicated stuff to combine both in order to search for and find
>> something in sysfs.
>
> Come on, it's not that more complex. If you know the name of the file,
> just do:
>
> find /sys -print -name <name> -exec cat {} \;
>
> And you'll get the data you want.
>
> Basically, what you are saying is "printk is more convenient for me and
> I do not care about the other cases that make much more sense with
> sysfs". The kernel does not work that way.

No. First I don't know the name of one of the thousands file in sysfs, 
just like I don't know all the possible kernel messages.

And second I still believe that KISS is the right way and frameworks 
aren't the right choice for everything.

But because I still don't refuse to learn, I will attach the output of

find /sys -type f -print -exec cat {} \;

to future bug reports instead of the output of dmesg.

Alexander Holler