From: kernel test robot <lkp@intel.com>
To: chenhuguanshen <chenhgs@chinatelecom.cn>
Cc: oe-kbuild-all@lists.linux.dev,
Marek Szyprowski <m.szyprowski@samsung.com>,
Jun Miao <jun.miao@intel.com>, Fan Du <fan.du@intel.com>,
Michael Kelley <mhklinux@outlook.com>
Subject: [linux-next:master 14865/15183] kernel/dma/swiotlb.c:1393 mem_used() warn: inconsistent indenting
Date: Sat, 15 Aug 2026 01:08:44 +0800 [thread overview]
Message-ID: <202608150003.3CvGdtWA-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 2697ef8943c9985c14708a6429e21812693857b2
commit: 121f9fd1c3083312055126205f3e40b8ee999fe6 [14865/15183] dma/swiotlb: decouple high watermark tracking from CONFIG_DEBUG_FS
config: x86_64-randconfig-161-20260814 (https://download.01.org/0day-ci/archive/20260815/202608150003.3CvGdtWA-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
smatch: v0.5.0-9187-g5189e3fb
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/202608150003.3CvGdtWA-lkp@intel.com/
smatch warnings:
kernel/dma/swiotlb.c:1393 mem_used() warn: inconsistent indenting
vim +1393 kernel/dma/swiotlb.c
121f9fd1c30833 kernel/dma/swiotlb.c chenhuguanshen 2026-08-12 1381
1aaa736815eb04 kernel/dma/swiotlb.c Petr Tesarik 2023-08-01 1382 #ifdef CONFIG_SWIOTLB_DYNAMIC
1aaa736815eb04 kernel/dma/swiotlb.c Petr Tesarik 2023-08-01 1383 struct io_tlb_pool *pool;
1aaa736815eb04 kernel/dma/swiotlb.c Petr Tesarik 2023-08-01 1384 unsigned long used = 0;
1aaa736815eb04 kernel/dma/swiotlb.c Petr Tesarik 2023-08-01 1385
1aaa736815eb04 kernel/dma/swiotlb.c Petr Tesarik 2023-08-01 1386 rcu_read_lock();
1aaa736815eb04 kernel/dma/swiotlb.c Petr Tesarik 2023-08-01 1387 list_for_each_entry_rcu(pool, &mem->pools, node)
1aaa736815eb04 kernel/dma/swiotlb.c Petr Tesarik 2023-08-01 1388 used += mem_pool_used(pool);
1aaa736815eb04 kernel/dma/swiotlb.c Petr Tesarik 2023-08-01 1389 rcu_read_unlock();
1aaa736815eb04 kernel/dma/swiotlb.c Petr Tesarik 2023-08-01 1390
1aaa736815eb04 kernel/dma/swiotlb.c Petr Tesarik 2023-08-01 1391 return used;
1aaa736815eb04 kernel/dma/swiotlb.c Petr Tesarik 2023-08-01 1392 #else
158dbe9c9a3d36 kernel/dma/swiotlb.c Petr Tesarik 2023-08-01 @1393 return mem_pool_used(&mem->defpool);
1aaa736815eb04 kernel/dma/swiotlb.c Petr Tesarik 2023-08-01 1394 #endif
^1da177e4c3f41 arch/ia64/lib/swiotlb.c Linus Torvalds 2005-04-16 1395 }
^1da177e4c3f41 arch/ia64/lib/swiotlb.c Linus Torvalds 2005-04-16 1396
:::::: The code at line 1393 was first introduced by commit
:::::: 158dbe9c9a3d36da824139e5304169326550c6c9 swiotlb: separate memory pool data from other allocator data
:::::: TO: Petr Tesarik <petr.tesarik.ext@huawei.com>
:::::: CC: Christoph Hellwig <hch@lst.de>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-14 17:09 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=202608150003.3CvGdtWA-lkp@intel.com \
--to=lkp@intel.com \
--cc=chenhgs@chinatelecom.cn \
--cc=fan.du@intel.com \
--cc=jun.miao@intel.com \
--cc=m.szyprowski@samsung.com \
--cc=mhklinux@outlook.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.