From: Richard Weinberger <richard@nod.at>
To: Alexander Holler <holler@ahsoftware.de>,
Arend van Spriel <arend@broadcom.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Borislav Petkov <bp@alien8.de>,
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 19:09:04 +0100 [thread overview]
Message-ID: <54C7D440.6000509@nod.at> (raw)
In-Reply-To: <54C7D31D.6090109@ahsoftware.de>
Am 27.01.2015 um 19:04 schrieb Alexander Holler:
> Am 27.01.2015 um 18:53 schrieb Arend van Spriel:
>
>> Ever used rgrep or grep -R. Anyway, if this is you use-case what about
>> the gazillion other pieces of info in the kernel. When moving in that
>> direction you can be sure dmesg will flush out.
>
> Sorry, never heard about that -R and wasn't aware that the kernel does a lot of things. ;)
>
> I don't want that ftrace stuff appears in dmesg, but I like to do
>
> dmesg | grep -i mmc (or whatever is of interest)
>
> instead of
>
> grep -Rsi mmc /sys/<a hundred tabs to search a matching direcory> or something like
>
> find /sys -iname '*mmc*' -exec <more silly complications> \;
You don't have to use grep or find.
Add a sysfs attribute, document it in Documentation/ABI and done.
By documenting stuff you'll make the world a better place.
Thanks,
//richard
next prev parent reply other threads:[~2015-01-27 18:09 UTC|newest]
Thread overview: 26+ 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
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 17:53 ` Arend van Spriel
2015-01-27 18:04 ` Alexander Holler
2015-01-27 18:09 ` Richard Weinberger [this message]
2015-01-27 18:12 ` Borislav Petkov
2015-01-27 12:20 ` Arend van Spriel
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=54C7D440.6000509@nod.at \
--to=richard@nod.at \
--cc=arend@broadcom.com \
--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=rostedt@goodmis.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.