From: Harish Jenny K N <harish_kandiga@mentor.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Avri Altman <Avri.Altman@wdc.com>,
"ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
"shawn.lin@rock-chips.com" <shawn.lin@rock-chips.com>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Vladimir_Zapolskiy@mentor.com" <Vladimir_Zapolskiy@mentor.com>
Subject: Re: [PATCH v9] mmc: Export host capabilities to debugfs.
Date: Mon, 12 Mar 2018 19:04:17 +0530 [thread overview]
Message-ID: <5e038945-a09c-5c64-2152-5d2783a249ec@mentor.com> (raw)
In-Reply-To: <1520859807.10722.591.camel@linux.intel.com>
On Monday 12 March 2018 06:33 PM, Andy Shevchenko wrote:
> On Mon, 2018-03-12 at 18:00 +0530, Harish Jenny K N wrote:
>
>
>>>>>>> + 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.
>>>>> Also maybe use sizeof(mmc_host_capabilities) instead of
>>>>> BITS_PER_LONG?
>>>> You mean sizeof(caps) and not sizeof(mmc_host_capabilities) .
>>>> Right ?
>>> meant ARRAY_SIZE(mmc_host_capabilities)
>> ARRAY_SIZE(mmc_host_capabilities) will be 32 and this will be my old
>> change for which I got a comment from Andy Shevchenko asking me to
>> replace u32 with unsigned long.
>>
>> This is the old comment:
>>
>>>> + int size = sizeof(u32) * BITS_PER_BYTE;
>>> This is redundant. Use BITS_PER_LONG (why's that, see below) in the
> There is nothing about ARRAY_SIZE().
> ARRAY_SIZE() will work quite good as well.
Yes. Definitely it works. I was only mentioning about changing u32 to unsigned long for caps and passing BITS_PER_LONG as size in for_each_set_bit.
>
>> for_each_set_bit().
>>
>>>> + for_each_set_bit(bit, (const unsigned long *)&caps, size)
>>>> + for_each_set_bit(bit, (const unsigned long *)&caps2, size)
>>> These are UB cases.
>>> Fix is simple, replace u32 by unsigned long in (1) above.
>> Note: Without typecasting &caps to(const unsigned long *) will give
>> compilation error in this case.
> What kind of?
>
Sorry for I was not clear that the compilation error is for the following case
> u32 caps = host->caps;
> for_each_set_bit(bit, &caps, ARRAY_SIZE(mmc_host_capabilities))
example: compilation for arm gives this error for the following lines:
drivers/mmc/core/debugfs.c: In function 'mmc_caps_show':
./include/linux/bitops.h:41:30: error: passing argument 1 of '_find_first_bit_le' from incompatible pointer type [-Werror=incompatible-pointer-types]
for ((bit) = find_first_bit((addr), (size)); \
^
./arch/arm/include/asm/bitops.h:202:50: note: in definition of macro 'find_first_bit'
#define find_first_bit(p,sz) _find_first_bit_le(p,sz)
^
drivers/mmc/core/debugfs.c:318:2: note: in expansion of macro 'for_each_set_bit'
for_each_set_bit(bit, &caps, ARRAY_SIZE(mmc_host_capabilities))
^
./arch/arm/include/asm/bitops.h:165:12: note: expected 'const long unsigned int *' but argument is of type 'u32 * {aka unsigned int *}'
extern int _find_first_bit_le(const unsigned long *p, unsigned size);
^
Thanks,
Harish Jenny K N
next prev parent reply other threads:[~2018-03-12 13:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 4:31 Harish Jenny K N
2018-03-12 10:07 ` Andy Shevchenko
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 [this message]
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=5e038945-a09c-5c64-2152-5d2783a249ec@mentor.com \
--to=harish_kandiga@mentor.com \
--cc=Avri.Altman@wdc.com \
--cc=Vladimir_Zapolskiy@mentor.com \
--cc=adrian.hunter@intel.com \
--cc=andriy.shevchenko@linux.intel.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®