From: Linus Walleij <linus.walleij@linaro.org>
To: Baolin Wang <baolin.wang@linaro.org>
Cc: Chris Ball <chris@printf.net>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Mark Brown <broonie@kernel.org>,
Sebastian Rasmussen <sebras@gmail.com>
Subject: Re: [PATCH v2] mmc-utils: Merge the lsmmc tool into mmc-utils
Date: Fri, 5 Feb 2016 10:29:51 +0100 [thread overview]
Message-ID: <CACRpkdZjJ1nOmFcznXx-RXVcwKgbp0rhPSy85cyui5_2x8X4zw@mail.gmail.com> (raw)
In-Reply-To: <32aeb1c8c24a29aabe3f58bcdf60faf7a39c6491.1454660477.git.baolin.wang@linaro.org>
On Fri, Feb 5, 2016 at 9:23 AM, Baolin Wang <baolin.wang@linaro.org> wrote:
> From: Sebastian Rasmussen <sebras@gmail.com>
>
> The lsmmc tools contains an extensive parser of the CID, CSD, SCR, EXT_CSD
> registers from userspace. The utility works as-is and uses sysfs to read
> the register values.
>
> The original code is created by Sebastian Rasmussen and still lives in
> an attachment in the mail archive of linux-mmc. It need to be merged into
> mmc-utils repository, which is convenient for testing MMC device from userspace.
>
> Signed-off-by: Sebastian Rasmussen <sebras@gmail.com>
> Signed-off-by: Chris Ball <chris@printf.net>
> Signed-off-by: Baolin Wang <baolin.wang@linaro.org>
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Yours,
Linus Walleij
next prev parent reply other threads:[~2016-02-05 9:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 8:23 [PATCH v2] mmc-utils: Merge the lsmmc tool into mmc-utils Baolin Wang
2016-02-05 9:29 ` Linus Walleij [this message]
2016-02-05 15:17 ` Sebastian Rasmussen
2016-02-16 20:02 ` Chris Ball
2016-02-17 2:31 ` Baolin Wang
-- strict thread matches above, loose matches on Subject: below --
2016-02-02 8:21 Baolin Wang
2016-02-02 21:39 ` Linus Walleij
2016-02-03 2:26 ` Baolin Wang
2016-02-02 22:04 ` Sebastian Rasmussen
2016-02-03 2:34 ` Baolin Wang
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=CACRpkdZjJ1nOmFcznXx-RXVcwKgbp0rhPSy85cyui5_2x8X4zw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=baolin.wang@linaro.org \
--cc=broonie@kernel.org \
--cc=chris@printf.net \
--cc=linux-mmc@vger.kernel.org \
--cc=sebras@gmail.com \
--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.