From: Marc Zyngier <maz@kernel.org>
To: Alexandre Torgue <alexandre.torgue@st.com>,
kernel test robot <lkp@intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>,
kbuild-all@lists.01.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com, marex@denx.de
Subject: Re: [PATCH] irqchip/stm32-exti: map direct event to irq parent
Date: Fri, 10 Jul 2020 10:31:59 +0100 [thread overview]
Message-ID: <87imevemwg.wl-maz@kernel.org> (raw)
In-Reply-To: <202007081232.bA2RH80f%lkp@intel.com>
Alexandre,
On Wed, 08 Jul 2020 05:57:24 +0100,
kernel test robot <lkp@intel.com> wrote:
>
> [1 <text/plain; us-ascii (7bit)>]
> Hi Alexandre,
>
> I love your patch! Perhaps something to improve:
>
> [auto build test WARNING on stm32/stm32-next]
> [also build test WARNING on soc/for-next v5.8-rc4 next-20200707]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use as documented in
> https://git-scm.com/docs/git-format-patch]
>
> url: https://github.com/0day-ci/linux/commits/Alexandre-Torgue/irqchip-stm32-exti-map-direct-event-to-irq-parent/20200706-161327
> base: https://git.kernel.org/pub/scm/linux/kernel/git/atorgue/stm32.git stm32-next
> config: arm-randconfig-s031-20200707 (attached as .config)
> compiler: arm-linux-gnueabi-gcc (GCC) 9.3.0
> reproduce:
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # apt-get install sparse
> # sparse version: v0.6.2-31-gabbfd661-dirty
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=arm
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All warnings (new ones prefixed by >>):
>
> In file included from include/linux/build_bug.h:5,
> from include/linux/bits.h:23,
> from include/linux/bitops.h:5,
> from drivers/irqchip/irq-stm32-exti.c:8:
> drivers/irqchip/irq-stm32-exti.c: In function 'stm32_exti_h_domain_alloc':
> drivers/irqchip/irq-stm32-exti.c:683:23: warning: comparison of unsigned expression >= 0 is always true [-Wtype-limits]
> 683 | if (desc->irq_parent >= 0) {
> | ^~
> include/linux/compiler.h:58:52: note: in definition of macro '__trace_if_var'
> 58 | #define __trace_if_var(cond) (__builtin_constant_p(cond) ? (cond) : __trace_if_value(cond))
> | ^~~~
> >> drivers/irqchip/irq-stm32-exti.c:683:2: note: in expansion of macro 'if'
> 683 | if (desc->irq_parent >= 0) {
Do you plan to address this? Looks like an actual bug to me.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2020-07-10 9:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 8:11 [PATCH] irqchip/stm32-exti: map direct event to irq parent Alexandre Torgue
2020-07-08 4:57 ` kernel test robot
2020-07-10 9:31 ` Marc Zyngier [this message]
2020-07-10 9:37 ` Alexandre Torgue
2020-07-17 12:37 ` Marc Zyngier
2020-07-17 13:11 ` Alexandre Torgue
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=87imevemwg.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=jason@lakedaemon.net \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=lkp@intel.com \
--cc=marex@denx.de \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).