From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Harish Jenny K N <harish_kandiga@mentor.com>,
ulf.hansson@linaro.org, linus.walleij@linaro.org,
adrian.hunter@intel.com, shawn.lin@rock-chips.com,
avri.altman@wdc.com
Cc: linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
Vladimir_Zapolskiy@mentor.com
Subject: Re: [PATCH v9] mmc: Export host capabilities to debugfs.
Date: Mon, 12 Mar 2018 12:07:42 +0200 [thread overview]
Message-ID: <1520849262.10722.582.camel@linux.intel.com> (raw)
In-Reply-To: <1520829090-3567-1-git-send-email-harish_kandiga@mentor.com>
On Mon, 2018-03-12 at 10:01 +0530, Harish Jenny K N wrote:
> This patch exports the host capabilities to debugfs
>
> This idea of sharing host capabilities over debugfs
> came up from Abbas Raza <Abbas_Raza@mentor.com>
> Earlier discussions:
> https://lkml.org/lkml/2018/3/5/357
> https://www.spinics.net/lists/linux-mmc/msg48219.html
>
Address below minors and, FWIW, take mine
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> + for_each_set_bit(bit, (const unsigned long *)&caps,
> BITS_PER_LONG)
> + for_each_set_bit(bit, (const unsigned long *)&caps2,
> BITS_PER_LONG)
Explicit casting is not needed anymore in both cases.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2018-03-12 10:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 4:31 [PATCH v9] mmc: Export host capabilities to debugfs Harish Jenny K N
2018-03-12 4:31 ` Harish Jenny K N
2018-03-12 10:07 ` Andy Shevchenko [this message]
2018-03-12 10:27 ` Harish Jenny K N
2018-03-12 10:27 ` Harish Jenny K N
2018-03-12 10:45 ` Avri Altman
2018-03-12 11:16 ` Harish Jenny K N
2018-03-12 11:32 ` Avri Altman
2018-03-12 12:30 ` Harish Jenny K N
2018-03-12 13:03 ` Andy Shevchenko
2018-03-12 13:34 ` Harish Jenny K N
2018-03-12 14:07 ` Harish Jenny K N
2018-03-12 14:20 ` Andy Shevchenko
2018-03-12 14:22 ` Andy Shevchenko
2018-03-12 14:27 ` Andy Shevchenko
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=1520849262.10722.582.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Vladimir_Zapolskiy@mentor.com \
--cc=adrian.hunter@intel.com \
--cc=avri.altman@wdc.com \
--cc=harish_kandiga@mentor.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 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.