From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: [ragnatech:media-next 128/278] drivers/media/rc/meson-ir-tx.c:327:2-9: line 327 is redundant because platform_get_irq() already prints an error
Date: Mon, 23 Aug 2021 12:40:36 +0800 [thread overview]
Message-ID: <202108231244.lcyTTeJc-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1207 bytes --]
CC: kbuild-all(a)lists.01.org
CC: linux-kernel(a)vger.kernel.org
TO: Viktor Prutyanov <viktor.prutyanov@phystech.edu>
CC: Mauro Carvalho Chehab <mchehab@kernel.org>
CC: linux-media(a)vger.kernel.org
CC: Sean Young <sean@mess.org>
tree: git://git.ragnatech.se/linux media-next
head: d62cd4d277cc711f781a7bdec4109c6148529b25
commit: 49be1c78d575eedf862a05aebfd5ab5c24193f61 [128/278] media: rc: introduce Meson IR TX driver
:::::: branch date: 2 days ago
:::::: commit date: 3 weeks ago
config: sparc64-randconfig-c024-20210822 (attached as .config)
compiler: sparc64-linux-gcc (GCC) 11.2.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
Reported-by: Julia Lawall <julia.lawall@lip6.fr>
cocci warnings: (new ones prefixed by >>)
>> drivers/media/rc/meson-ir-tx.c:327:2-9: line 327 is redundant because platform_get_irq() already prints an error
--
>> drivers/media/rc/meson-ir-tx.c:398:3-8: No need to set .owner here. The core will do it.
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 34356 bytes --]
next reply other threads:[~2021-08-23 4:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 4:40 kernel test robot [this message]
2021-08-23 4:40 ` [PATCH] media: rc: fix platform_get_irq.cocci warnings kernel test robot
2021-08-23 4:40 ` [PATCH] media: rc: fix platform_no_drv_owner.cocci warnings kernel test robot
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=202108231244.lcyTTeJc-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild@lists.01.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.