All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: James Morse <james.morse@arm.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [morse:mpam/monitors_and_locking/v5 6/24] arch/x86/kernel/cpu/resctrl/monitor.c:47: warning: Cannot understand  * @closid_num_dirty_rmid    The number of dirty RMID each CLOSID has.
Date: Fri, 18 Aug 2023 06:17:07 +0800	[thread overview]
Message-ID: <202308180627.0oav3dHd-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/morse/linux.git mpam/monitors_and_locking/v5
head:   562c8d6543a4f032152fa2f72fc36f65bd9dae42
commit: 98252168f348d6d84ce98e9e0c92157d9988f264 [6/24] x86/resctrl: Track the number of dirty RMID a CLOSID has
config: x86_64-rhel-8.3-bpf (https://download.01.org/0day-ci/archive/20230818/202308180627.0oav3dHd-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce: (https://download.01.org/0day-ci/archive/20230818/202308180627.0oav3dHd-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/202308180627.0oav3dHd-lkp@intel.com/

All warnings (new ones prefixed by >>):

   arch/x86/kernel/cpu/resctrl/monitor.c:40: warning: Cannot understand  * @rmid_free_lru    A least recently used list of free RMIDs
    on line 40 - I thought it was a doc line
>> arch/x86/kernel/cpu/resctrl/monitor.c:47: warning: Cannot understand  * @closid_num_dirty_rmid    The number of dirty RMID each CLOSID has.
    on line 47 - I thought it was a doc line
   arch/x86/kernel/cpu/resctrl/monitor.c:54: warning: Cannot understand  * @rmid_limbo_count     count of currently unused but (potentially)
    on line 54 - I thought it was a doc line
   arch/x86/kernel/cpu/resctrl/monitor.c:63: warning: Cannot understand  * @rmid_entry - The entry in the limbo and free lists.
    on line 63 - I thought it was a doc line


vim +47 arch/x86/kernel/cpu/resctrl/monitor.c

    45	
    46	/**
  > 47	 * @closid_num_dirty_rmid    The number of dirty RMID each CLOSID has.
    48	 * Only allocated when CONFIG_RESCTRL_RMID_DEPENDS_ON_CLOSID is defined.
    49	 * Indexed by CLOSID. Protected by rdtgroup_mutex.
    50	 */
    51	static int *closid_num_dirty_rmid;
    52	

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

                 reply	other threads:[~2023-08-17 22:17 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=202308180627.0oav3dHd-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=james.morse@arm.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.