From: Richard Weinberger <richard@nod.at>
To: Alexander Holler <holler@ahsoftware.de>
Cc: 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 13:06:53 +0100 [thread overview]
Message-ID: <54C77F5D.30302@nod.at> (raw)
In-Reply-To: <54C77E69.7050600@ahsoftware.de>
Am 27.01.2015 um 13:02 schrieb Alexander Holler:
> Am 27.01.2015 um 12:55 schrieb Richard Weinberger:
>> On Tue, Jan 27, 2015 at 12:48 PM, Alexander Holler <holler@ahsoftware.de> wrote:
>>> It's an interesting detail, so inform the user about it.
>>>
>>> Signed-off-by: Alexander Holler <holler@ahsoftware.de>
>>> ---
>>> drivers/mmc/core/bus.c | 4 ++++
>>> 1 file changed, 4 insertions(+)
>>>
>>> diff --git a/drivers/mmc/core/bus.c b/drivers/mmc/core/bus.c
>>> index 8a1f124..4a60028 100644
>>> --- a/drivers/mmc/core/bus.c
>>> +++ b/drivers/mmc/core/bus.c
>>> @@ -347,6 +347,10 @@ int mmc_add_card(struct mmc_card *card)
>>> uhs_bus_speed_mode, type, card->rca);
>>> }
>>>
>>> + if (mmc_can_secure_erase_trim(card))
>>> + pr_info("%s: card supports secure erase/trim\n",
>>> + mmc_hostname(card->host));
>>> +
>>
>> Please make this a sysfs attribute.
>> Exposing such properties as log messages is horrible.
>
> Look at the source at the message which is printed just before and decide which one you find more informational / useful.
-ENOPARSE
Thanks,
//richard
next prev parent reply other threads:[~2015-01-27 12:06 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 [this message]
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 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=54C77F5D.30302@nod.at \
--to=richard@nod.at \
--cc=chris@printf.net \
--cc=holler@ahsoftware.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox