From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: [zen-kernel-zen-kernel:5.13/lru 9/14] mm/vmscan.c:2911:3-8: WARNING use flexible-array member instead (https://www.kernel.org/doc/html/latest/process/deprecated.html#zero-length-and-one-element-arrays)
Date: Tue, 29 Jun 2021 19:53:27 +0800 [thread overview]
Message-ID: <202106291915.I3w71RTu-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]
CC: kbuild-all(a)lists.01.org
TO: steven(a)liquorix.net
tree: https://github.com/zen-kernel/zen-kernel 5.13/lru
head: 6c0599d8df2c91043cffba0fbdd8c0fdc3297551
commit: 0c09e5f119fe208b6abf362197df921a81c18eea [9/14] mm: multigenerational lru: mm_struct list
:::::: branch date: 14 hours ago
:::::: commit date: 14 hours ago
config: sparc64-randconfig-c023-20210629 (attached as .config)
compiler: sparc64-linux-gcc (GCC) 9.3.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 >>)
>> mm/vmscan.c:2911:3-8: WARNING use flexible-array member instead (https://www.kernel.org/doc/html/latest/process/deprecated.html#zero-length-and-one-element-arrays)
mm/vmscan.c:3067:15-21: WARNING use flexible-array member instead (https://www.kernel.org/doc/html/latest/process/deprecated.html#zero-length-and-one-element-arrays)
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: 28756 bytes --]
next reply other threads:[~2021-06-29 11:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 11:53 kernel test robot [this message]
2021-06-29 11:53 ` [PATCH] mm: multigenerational lru: fix flexible_array.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=202106291915.I3w71RTu-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.