From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: [tobetter:odroid-5.15.y 21/75] drivers/char/exynos-gpiomem.c:231:9-13: ERROR: reference preceded by free on line 229
Date: Wed, 03 Nov 2021 21:33:37 +0800 [thread overview]
Message-ID: <202111032116.26fBuuru-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]
CC: kbuild-all(a)lists.01.org
CC: linux-kernel(a)vger.kernel.org
TO: Brian Kim <brian.kim@hardkernel.com>
CC: Dongjin Kim <tobetter@gmail.com>
CC: memeka <mihailescu2m@gmail.com>
CC: Yang Deokgyu <secugyu@gmail.com>
tree: https://github.com/tobetter/linux odroid-5.15.y
head: 49f1393b8740941fa5176620b302f25ab5f786dc
commit: 61f45d975621becb00c0aef303769f10428b9cd8 [21/75] ODROID-XU4: char: exynos: add /dev/gpiomem device for rootless user GPIO access
:::::: branch date: 4 hours ago
:::::: commit date: 6 hours ago
config: arm-randconfig-c023-20211103 (attached as .config)
compiler: arm-linux-gnueabi-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/char/exynos-gpiomem.c:231:9-13: ERROR: reference preceded by free on line 229
--
>> drivers/char/exynos-gpiomem.c:258: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: 52831 bytes --]
next reply other threads:[~2021-11-03 13:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 13:33 kernel test robot [this message]
2021-11-03 13:33 ` [PATCH] ODROID-XU4: char: exynos: 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=202111032116.26fBuuru-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.