From: Giuseppe CAVALLARO <peppe.cavallaro@st.com>
To: Chris Ball <cjb@laptop.org>
Cc: linux-mmc@vger.kernel.org,
Johan RUDHOLM <johan.rudholm@stericsson.com>,
Shashidhar Hiremath <shashidharh@vayavyalabs.com>
Subject: Re: ANNOUNCE: new "mmc-utils" repository
Date: Wed, 15 Feb 2012 14:43:13 +0100 [thread overview]
Message-ID: <4F3BB671.9040208@st.com> (raw)
In-Reply-To: <m2wr7ogqxm.fsf@bob.laptop.org>
On 2/15/2012 2:35 PM, Chris Ball wrote:
> Hi,
>
> On Wed, Feb 15 2012, Giuseppe CAVALLARO wrote:
>> Hi Chris
>>
>> On 2/12/2012 6:03 PM, Chris Ball wrote:
>>> Hi,
>>>
>>> I've created a repository for userspace mmc tools now:
>>>
>>> git://git.kernel.org/pub/scm/linux/kernel/git/cjb/mmc-utils.git
>>>
>>> At the moment the only commands supported are Johan Rudholm's extcsd
>>> write-protect commands, exposed as:
>>>
>>> ./mmc extcsd read /dev/mmcblkX
>>> ./mmc extcsd write /dev/mmcblkX
>>
>>
>> Is it worth now trying to add the logic behind the patch (mmc: debugfs:
>> parse ext_csd via debug_fs (v2)) I sent time ago to parse the EXT_CSD?
>> I can do that on mmc-utils if not yet done. Pls let me know.
>
> Yes, please. (If you look farther down in the same message I did
> mention adding it!)
>
> I think you can add it all to mmc extcsd read, rather than introducing
> a new command.
Agree! I'll do that and provide a patch asap.
peppe
>
> Thanks,
>
> - Chris.
next prev parent reply other threads:[~2012-02-15 14:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-12 17:03 ANNOUNCE: new "mmc-utils" repository Chris Ball
2012-02-13 19:50 ` Linus Walleij
2012-02-14 5:56 ` Jaehoon Chung
2012-02-14 8:07 ` Johan RUDHOLM
2012-02-14 8:31 ` Jaehoon Chung
2012-02-14 14:53 ` Chris Ball
2012-02-14 15:31 ` Johan RUDHOLM
2012-02-15 10:55 ` Jaehoon Chung
2012-02-15 12:06 ` Johan RUDHOLM
2012-02-16 20:49 ` Chris Ball
2012-02-14 8:04 ` Johan RUDHOLM
2012-02-14 11:06 ` Chris Ball
2012-02-15 12:55 ` Giuseppe CAVALLARO
2012-02-15 13:35 ` Chris Ball
2012-02-15 13:43 ` Giuseppe CAVALLARO [this message]
2012-02-20 14:09 ` Giuseppe CAVALLARO
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=4F3BB671.9040208@st.com \
--to=peppe.cavallaro@st.com \
--cc=cjb@laptop.org \
--cc=johan.rudholm@stericsson.com \
--cc=linux-mmc@vger.kernel.org \
--cc=shashidharh@vayavyalabs.com \
/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.