From: Harish Jenny K N <harish_kandiga@mentor.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Shawn Lin <shawn.lin@rock-chips.com>,
Avri Altman <avri.altman@wdc.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-mmc <linux-mmc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mmc: Export host capabilities to debugfs.
Date: Fri, 2 Mar 2018 18:47:42 +0530 [thread overview]
Message-ID: <09fabc35-438c-2634-b582-bf5a7888b930@mentor.com> (raw)
In-Reply-To: <CACRpkda26vE3vfuX3ioJduuTh8fyWOZgsZ-e1BbQiwAf=3ZuAg@mail.gmail.com>
On Thursday 01 March 2018 07:54 PM, Linus Walleij wrote:
> On Thu, Mar 1, 2018 at 2:17 PM, Harish Jenny K N
> <harish_kandiga@mentor.com> wrote:
>
> Thanks for your patch!
>
>> This patch exports the host capabilities to debugfs
>>
>> Signed-off-by: Andrew Gabbasov <andrew_gabbasov@mentor.com>
>> Signed-off-by: Harish Jenny K N <harish_kandiga@mentor.com>
> Is there a corresponding patch to the mmc utils to make use
> of the exported information? An opaque u32 seems pretty hard
> to interpret.
>
> Yours,
> Linus Walleij
A sample patch "[RFC PATCH] mmc-utils: host_caps: Add parser to read host capabilities" is submitted.
Thanks,
Harish Jenny K N
next prev parent reply other threads:[~2018-03-02 13:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 13:17 Harish Jenny K N
2018-03-01 14:24 ` Linus Walleij
2018-03-02 13:17 ` Harish Jenny K N [this message]
2018-03-02 13:24 ` Linus Walleij
2018-03-03 16:32 ` Vladimir Zapolskiy
2018-03-05 4:07 ` Harish Jenny K N
2018-03-05 13:38 Harish Jenny K N
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=09fabc35-438c-2634-b582-bf5a7888b930@mentor.com \
--to=harish_kandiga@mentor.com \
--cc=adrian.hunter@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=avri.altman@wdc.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=shawn.lin@rock-chips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®