public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Youngjun Park <youngjun.park@lge.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH v3 1/5] mm: swap: introduce swap tier infrastructure
Date: Mon, 2 Feb 2026 15:50:17 +0800	[thread overview]
Message-ID: <202602021529.0NRBWccf-lkp@intel.com> (raw)
In-Reply-To: <20260131125454.3187546-2-youngjun.park@lge.com>

Hi Youngjun,

[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:

[auto build test WARNING on 5a3704ed2dce0b54a7f038b765bb752b87ee8cc2]

url:    https://github.com/intel-lab-lkp/linux/commits/Youngjun-Park/mm-swap-introduce-swap-tier-infrastructure/20260201-005914
base:   5a3704ed2dce0b54a7f038b765bb752b87ee8cc2
patch link:    https://lore.kernel.org/r/20260131125454.3187546-2-youngjun.park%40lge.com
patch subject: [RFC PATCH v3 1/5] mm: swap: introduce swap tier infrastructure
config: i386-buildonly-randconfig-003-20260202 (https://download.01.org/0day-ci/archive/20260202/202602021529.0NRBWccf-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260202/202602021529.0NRBWccf-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/202602021529.0NRBWccf-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> mm/swap_tier.c:95:10: warning: format specifies type 'long' but the argument has type 'int' [-Wformat]
      93 |                 len += sysfs_emit_at(buf, len, "%-16s %-5ld %-11d %-11d\n",
         |                                                       ~~~~~
         |                                                       %-5d
      94 |                                      tier->name,
      95 |                                      TIER_IDX(tier),
         |                                      ^~~~~~~~~~~~~~
   mm/swap_tier.c:30:24: note: expanded from macro 'TIER_IDX'
      30 | #define TIER_IDX(tier)  ((tier) - swap_tiers)
         |                         ^~~~~~~~~~~~~~~~~~~~~
   1 warning generated.


vim +95 mm/swap_tier.c

    82	
    83	ssize_t swap_tiers_sysfs_show(char *buf)
    84	{
    85		struct swap_tier *tier;
    86		ssize_t len = 0;
    87	
    88		len += sysfs_emit_at(buf, len, "%-16s %-5s %-11s %-11s\n",
    89				 "Name", "Idx", "PrioStart", "PrioEnd");
    90	
    91		spin_lock(&swap_tier_lock);
    92		for_each_active_tier(tier) {
    93			len += sysfs_emit_at(buf, len, "%-16s %-5ld %-11d %-11d\n",
    94					     tier->name,
  > 95					     TIER_IDX(tier),
    96					     tier->prio,
    97					     TIER_END_PRIO(tier));
    98			if (len >= PAGE_SIZE)
    99				break;
   100		}
   101		spin_unlock(&swap_tier_lock);
   102	
   103		return len;
   104	}
   105	

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

           reply	other threads:[~2026-02-02  7:50 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20260131125454.3187546-2-youngjun.park@lge.com>]

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=202602021529.0NRBWccf-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=youngjun.park@lge.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox