From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Syed Nayyar Waris <syednwaris@gmail.com>
Cc: kernel test robot <lkp@intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
Andrew Morton <akpm@linux-foundation.org>,
kbuild-all@lists.01.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
William Breathitt Gray <vilhelm.gray@gmail.com>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Michal Simek <michal.simek@xilinx.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
linux-arm Mailing List <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v8 4/4] gpio: xilinx: Utilize for_each_set_clump macro
Date: Fri, 19 Jun 2020 16:26:28 +0200 [thread overview]
Message-ID: <20200619142628.burfxyjoe5uouzuz@ltop.local> (raw)
In-Reply-To: <CACG_h5oiA8mDpTjtyGFYR4eptbxppN9tq+2wUj8T1hsbZ5h47A@mail.gmail.com>
On Tue, Jun 16, 2020 at 11:27:18AM +0530, Syed Nayyar Waris wrote:
Hi,
> Regarding the compilation warning reported above:
>
> "sparse: shift too big (64) for type unsigned long" at line 639
> "sparse: invalid access past the end of 'old' (8 8)" at line 638
>
> Kindly refer to the code above, at these line numbers.
>
> I am in the process of fixing this warning. But what would be the fix?
> ? At the moment can't think of a code-fix to make the compilation
> warning disappear (specially at line 639). Can anyone please explain
> to me the meaning of the compilation warning more deeply?
This error message is caused by sparse doing the check too early.
There is thus nothing to be fixed for it in this code.
Best regards,
-- Luc
WARNING: multiple messages have this Message-ID (diff)
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Syed Nayyar Waris <syednwaris@gmail.com>
Cc: kbuild-all@lists.01.org, kernel test robot <lkp@intel.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
William Breathitt Gray <vilhelm.gray@gmail.com>,
Michal Simek <michal.simek@xilinx.com>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Andrew Morton <akpm@linux-foundation.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-arm Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v8 4/4] gpio: xilinx: Utilize for_each_set_clump macro
Date: Fri, 19 Jun 2020 16:26:28 +0200 [thread overview]
Message-ID: <20200619142628.burfxyjoe5uouzuz@ltop.local> (raw)
In-Reply-To: <CACG_h5oiA8mDpTjtyGFYR4eptbxppN9tq+2wUj8T1hsbZ5h47A@mail.gmail.com>
On Tue, Jun 16, 2020 at 11:27:18AM +0530, Syed Nayyar Waris wrote:
Hi,
> Regarding the compilation warning reported above:
>
> "sparse: shift too big (64) for type unsigned long" at line 639
> "sparse: invalid access past the end of 'old' (8 8)" at line 638
>
> Kindly refer to the code above, at these line numbers.
>
> I am in the process of fixing this warning. But what would be the fix?
> ? At the moment can't think of a code-fix to make the compilation
> warning disappear (specially at line 639). Can anyone please explain
> to me the meaning of the compilation warning more deeply?
This error message is caused by sparse doing the check too early.
There is thus nothing to be fixed for it in this code.
Best regards,
-- Luc
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v8 4/4] gpio: xilinx: Utilize for_each_set_clump macro
Date: Fri, 19 Jun 2020 16:26:28 +0200 [thread overview]
Message-ID: <20200619142628.burfxyjoe5uouzuz@ltop.local> (raw)
In-Reply-To: <CACG_h5oiA8mDpTjtyGFYR4eptbxppN9tq+2wUj8T1hsbZ5h47A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 760 bytes --]
On Tue, Jun 16, 2020 at 11:27:18AM +0530, Syed Nayyar Waris wrote:
Hi,
> Regarding the compilation warning reported above:
>
> "sparse: shift too big (64) for type unsigned long" at line 639
> "sparse: invalid access past the end of 'old' (8 8)" at line 638
>
> Kindly refer to the code above, at these line numbers.
>
> I am in the process of fixing this warning. But what would be the fix?
> ? At the moment can't think of a code-fix to make the compilation
> warning disappear (specially at line 639). Can anyone please explain
> to me the meaning of the compilation warning more deeply?
This error message is caused by sparse doing the check too early.
There is thus nothing to be fixed for it in this code.
Best regards,
-- Luc
next prev parent reply other threads:[~2020-06-19 14:26 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 12:50 [PATCH v8 0/4] Introduce the for_each_set_clump macro Syed Nayyar Waris
2020-06-15 12:50 ` Syed Nayyar Waris
2020-06-15 12:50 ` Syed Nayyar Waris
2020-06-15 12:50 ` Syed Nayyar Waris
2020-06-15 12:51 ` [PATCH v8 1/4] bitops: " Syed Nayyar Waris
2020-06-15 13:56 ` Andy Shevchenko
2020-06-15 16:47 ` kernel test robot
2020-06-15 16:47 ` kernel test robot
2020-06-16 8:14 ` Andy Shevchenko
2020-06-20 13:45 ` Syed Nayyar Waris
2020-06-20 23:41 ` Syed Nayyar Waris
2020-06-17 8:00 ` kernel test robot
2020-06-17 8:00 ` kernel test robot
2020-06-15 12:52 ` [PATCH v8 2/4] lib/test_bitmap.c: Add for_each_set_clump test cases Syed Nayyar Waris
2020-06-15 12:53 ` [PATCH v8 3/4] gpio: thunderx: Utilize for_each_set_clump macro Syed Nayyar Waris
2020-06-15 12:54 ` [PATCH v8 4/4] gpio: xilinx: " Syed Nayyar Waris
2020-06-15 12:54 ` Syed Nayyar Waris
2020-06-15 20:09 ` kernel test robot
2020-06-15 20:09 ` kernel test robot
2020-06-15 20:09 ` kernel test robot
2020-06-16 5:57 ` Syed Nayyar Waris
2020-06-16 5:57 ` Syed Nayyar Waris
2020-06-19 14:26 ` Luc Van Oostenryck [this message]
2020-06-19 14:26 ` Luc Van Oostenryck
2020-06-19 14:26 ` Luc Van Oostenryck
2020-06-19 7:00 ` Syed Nayyar Waris
2020-06-19 7:00 ` Syed Nayyar Waris
2020-06-19 8:38 ` Andy Shevchenko
2020-06-19 8:38 ` Andy Shevchenko
2020-06-19 8:38 ` Andy Shevchenko
2020-06-19 9:05 ` Andy Shevchenko
2020-06-19 9:05 ` Andy Shevchenko
2020-06-19 9:05 ` Andy Shevchenko
2020-06-19 19:17 ` Robin Murphy
2020-06-19 19:17 ` Robin Murphy
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=20200619142628.burfxyjoe5uouzuz@ltop.local \
--to=luc.vanoostenryck@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bgolaszewski@baylibre.com \
--cc=kbuild-all@lists.01.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=michal.simek@xilinx.com \
--cc=syednwaris@gmail.com \
--cc=vilhelm.gray@gmail.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.