public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: Alexander Holler <holler@ahsoftware.de>
Cc: <linux-mmc@vger.kernel.org>, <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:20:03 +0100	[thread overview]
Message-ID: <54C78273.7090700@broadcom.com> (raw)
In-Reply-To: <1422359304-30321-1-git-send-email-holler@ahsoftware.de>

On 01/27/15 12:48, Alexander Holler 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));
> +

If you want to expose this info you could also consider doing it in the 
debugfs folder that is created below.

>   #ifdef CONFIG_DEBUG_FS
>   	mmc_add_card_debugfs(card);
>   #endif

Regards,
Arend

[1] http://lxr.free-electrons.com/ident?i=mmc_add_card_debugfs

      parent reply	other threads:[~2015-01-27 12:23 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
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 [this message]

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=54C78273.7090700@broadcom.com \
    --to=arend@broadcom.com \
    --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