public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Alexander Holler <holler@ahsoftware.de>
Cc: Borislav Petkov <bp@alien8.de>,
	Richard Weinberger <richard@nod.at>,
	linux-mmc@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Chris Ball <chris@printf.net>,
	Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: [PATCH] mmc: print message if a card supports secure erase/trim
Date: Tue, 27 Jan 2015 12:48:17 -0500	[thread overview]
Message-ID: <20150127124817.608db508@gandalf.local.home> (raw)
In-Reply-To: <54C7CD1C.1060601@ahsoftware.de>

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.

-- Steve

  reply	other threads:[~2015-01-27 17:48 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-27 11:48 [PATCH] mmc: print message if a card supports secure erase/trim Alexander Holler
2015-01-27 11:55 ` Richard Weinberger
2015-01-27 12:02   ` Alexander Holler
2015-01-27 12:06     ` Richard Weinberger
2015-01-27 18:56       ` Joe Perches
2015-01-27 12:08     ` Borislav Petkov
2015-01-27 12:15       ` Alexander Holler
2015-01-27 12:31         ` Richard Weinberger
2015-01-27 12:44           ` Alexander Holler
2015-01-27 14:21             ` Borislav Petkov
2015-01-27 16:55               ` Alexander Holler
2015-01-27 17:24                 ` Steven Rostedt
2015-01-27 17:38                   ` Alexander Holler
2015-01-27 17:48                     ` Steven Rostedt [this message]
2015-01-27 18:13                       ` Alexander Holler
2015-01-27 18:21                         ` Steven Rostedt
2015-01-27 18:33                           ` Alexander Holler
2015-01-27 18:42                             ` Steven Rostedt
2015-01-27 19:14                               ` Alexander Holler
2015-01-27 17:53                     ` Arend van Spriel
2015-01-27 18:04                       ` Alexander Holler
2015-01-27 18:09                         ` Richard Weinberger
2015-01-27 18:12                         ` Borislav Petkov
2015-01-27 12:20 ` Arend van Spriel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150127124817.608db508@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=bp@alien8.de \
    --cc=chris@printf.net \
    --cc=holler@ahsoftware.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=richard@nod.at \
    --cc=ulf.hansson@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox