From: kernel test robot <lkp@intel.com>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Paul Burton <paul.burton@mips.com>
Subject: arch/mips/kernel/setup.c:459 early_parse_elfcorehdr() warn: inconsistent indenting
Date: Wed, 5 Aug 2020 11:04:00 +0800 [thread overview]
Message-ID: <202008051159.LIvlSvDO%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1683 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 442489c219235991de86d0277b5d859ede6d8792
commit: a94e4f24ec836c8984f839594bad7454184975b1 MIPS: init: Drop boot_mem_map
date: 12 months ago
config: mips-randconfig-m031-20200805 (attached as .config)
compiler: mips-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>
smatch warnings:
arch/mips/kernel/setup.c:459 early_parse_elfcorehdr() warn: inconsistent indenting
vim +459 arch/mips/kernel/setup.c
450
451 #ifdef CONFIG_PROC_VMCORE
452 unsigned long setup_elfcorehdr, setup_elfcorehdr_size;
453 static int __init early_parse_elfcorehdr(char *p)
454 {
455 struct memblock_region *mem;
456
457 setup_elfcorehdr = memparse(p, &p);
458
> 459 for_each_memblock(memory, mem) {
460 unsigned long start = mem->base;
461 unsigned long end = mem->end;
462 if (setup_elfcorehdr >= start && setup_elfcorehdr < end) {
463 /*
464 * Reserve from the elf core header to the end of
465 * the memory segment, that should all be kdump
466 * reserved memory.
467 */
468 setup_elfcorehdr_size = end - setup_elfcorehdr;
469 break;
470 }
471 }
472 /*
473 * If we don't find it in the memory map, then we shouldn't
474 * have to worry about it, as the new kernel won't use it.
475 */
476 return 0;
477 }
478 early_param("elfcorehdr", early_parse_elfcorehdr);
479 #endif
480
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 23654 bytes --]
next reply other threads:[~2020-08-05 3:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 3:04 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-06-30 19:12 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=202008051159.LIvlSvDO%lkp@intel.com \
--to=lkp@intel.com \
--cc=jiaxun.yang@flygoat.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.burton@mips.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
all inboxes | Powered by JetHome®