All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: John Johansen <john.johansen@canonical.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [linux-next:master 9669/10024] security/apparmor/lib.c:33:22: sparse: sparse: symbol 'debug_values_table' was not declared. Should it be static?
Date: Tue, 21 Jan 2025 13:51:04 +0800	[thread overview]
Message-ID: <202501211337.WG9ibiKv-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   1573c8d4cb206a2d1454ff711e79f8df2353290b
commit: 71e6cff3e0dde6f6a3355d6c73ca3e176567995e [9669/10024] apparmor: Improve debug print infrastructure
config: sparc-randconfig-r111-20250121 (https://download.01.org/0day-ci/archive/20250121/202501211337.WG9ibiKv-lkp@intel.com/config)
compiler: sparc-linux-gcc (GCC) 14.2.0
reproduce: (https://download.01.org/0day-ci/archive/20250121/202501211337.WG9ibiKv-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202501211337.WG9ibiKv-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> security/apparmor/lib.c:33:22: sparse: sparse: symbol 'debug_values_table' was not declared. Should it be static?

vim +/debug_values_table +33 security/apparmor/lib.c

    32	
  > 33	struct val_table_ent debug_values_table[] = {
    34		{ "N", DEBUG_NONE },
    35		{ "none", DEBUG_NONE },
    36		{ "n", DEBUG_NONE },
    37		{ "0", DEBUG_NONE },
    38		{ "all", DEBUG_ALL },
    39		{ "Y", DEBUG_ALL },
    40		{ "y", DEBUG_ALL },
    41		{ "1", DEBUG_ALL },
    42		{ "abs_root", DEBUG_LABEL_ABS_ROOT },
    43		{ "label", DEBUG_LABEL },
    44		{ "domain", DEBUG_DOMAIN },
    45		{ "policy", DEBUG_POLICY },
    46		{ "interface", DEBUG_INTERFACE },
    47		{ NULL, 0 }
    48	};
    49	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2025-01-21  5:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202501211337.WG9ibiKv-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=john.johansen@canonical.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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.