From: Andrei Warkentin <awarkentin@vmware.com>
To: Namjae Jeon <linkinjeon@gmail.com>
Cc: linux-kernel@vger.kernel.org, cjb@laptop.org, linux-mmc@vger.kernel.org
Subject: Re: [PATCH] mmc : export hw reset function info to user
Date: Mon, 19 Sep 2011 09:19:48 -0700 (PDT) [thread overview]
Message-ID: <108743536.474964.1316449188347.JavaMail.root@zimbra-prod-mbox-2.vmware.com> (raw)
In-Reply-To: <1316359225-2224-1-git-send-email-linkinjeon@gmail.com>
Hi Namjae, others,
----- Original Message -----
> From: "Namjae Jeon" <linkinjeon@gmail.com>
> To: cjb@laptop.org, linux-mmc@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org, "Namjae Jeon" <linkinjeon@gmail.com>
> Sent: Sunday, September 18, 2011 11:20:25 AM
> Subject: [PATCH] mmc : export hw reset function info to user
>
> user app should know whether hw reset function is enable to use it.
> so I try to add sysfs file of hw reset function like enhanced area.
>
If we're going to be adding a bunch of attributes from ext_csd, why not
just allow dumping the entire ext_csd in a semi-readable form? Via something like
hex_dump_to_buffer. This will allow easy human an machine parsing, and be more
lightweight then adding a sysfs attr for each EXT_CSD byte (of which there are a lot).
I'm basing this on the thought that the only clients of these attrbutes would
either be developers or engineers involved with MMC media, or very specialized
software.
Thoughts?
A
next prev parent reply other threads:[~2011-09-19 16:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-18 15:20 Namjae Jeon
2011-09-19 16:19 ` Andrei Warkentin [this message]
2011-09-19 23:51 ` NamJae Jeon
2011-09-20 12:21 ` Adrian Hunter
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=108743536.474964.1316449188347.JavaMail.root@zimbra-prod-mbox-2.vmware.com \
--to=awarkentin@vmware.com \
--cc=cjb@laptop.org \
--cc=linkinjeon@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.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
Powered by JetHome