public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Bjørn Mork" <bjorn@mork.no>,
	"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>
Cc: oe-kbuild-all@lists.linux.dev,
	"Steven J . Hill" <Steven.Hill@imgtec.com>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Bjørn Mork" <bjorn@mork.no>,
	stable@vger.kernel.org
Subject: Re: [PATCH] MIPS: fw: Gracefully handle unknown firmware protocols
Date: Thu, 29 Aug 2024 06:15:09 +0800	[thread overview]
Message-ID: <202408290501.kTATRaBZ-lkp@intel.com> (raw)
In-Reply-To: <20240824144133.1464835-1-bjorn@mork.no>

Hi Bjørn,

kernel test robot noticed the following build errors:

[auto build test ERROR on linus/master]
[also build test ERROR on v6.11-rc5 next-20240828]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Bj-rn-Mork/MIPS-fw-Gracefully-handle-unknown-firmware-protocols/20240826-170643
base:   linus/master
patch link:    https://lore.kernel.org/r/20240824144133.1464835-1-bjorn%40mork.no
patch subject: [PATCH] MIPS: fw: Gracefully handle unknown firmware protocols
config: mips-bigsur_defconfig (https://download.01.org/0day-ci/archive/20240829/202408290501.kTATRaBZ-lkp@intel.com/config)
compiler: mips64-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240829/202408290501.kTATRaBZ-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/202408290501.kTATRaBZ-lkp@intel.com/

All errors (new ones prefixed by >>):

   arch/mips/fw/lib/cmdline.c: In function 'fw_init_cmdline':
>> arch/mips/fw/lib/cmdline.c:25:65: error: 'CKSEG2' undeclared (first use in this function); did you mean 'CKSEG0'?
      25 |         if (fw_arg0 >= CKSEG0 || fw_arg1 < CKSEG0 || fw_arg1 >= CKSEG2) {
         |                                                                 ^~~~~~
         |                                                                 CKSEG0
   arch/mips/fw/lib/cmdline.c:25:65: note: each undeclared identifier is reported only once for each function it appears in


vim +25 arch/mips/fw/lib/cmdline.c

    18	
    19	#ifndef CONFIG_HAVE_PLAT_FW_INIT_CMDLINE
    20	void __init fw_init_cmdline(void)
    21	{
    22		int i;
    23	
    24		/* Validate command line parameters. */
  > 25		if (fw_arg0 >= CKSEG0 || fw_arg1 < CKSEG0 || fw_arg1 >= CKSEG2) {
    26			fw_argc = 0;
    27			_fw_argv = NULL;
    28		} else {
    29			fw_argc = (fw_arg0 & 0x0000ffff);
    30			_fw_argv = (int *)fw_arg1;
    31		}
    32	
    33		/* Validate environment pointer. */
    34		if (fw_arg2 < CKSEG0 || fw_arg2 >= CKSEG2)
    35			_fw_envp = NULL;
    36		else
    37			_fw_envp = (int *)fw_arg2;
    38	
    39		for (i = 1; i < fw_argc; i++) {
    40			strlcat(arcs_cmdline, fw_argv(i), COMMAND_LINE_SIZE);
    41			if (i < (fw_argc - 1))
    42				strlcat(arcs_cmdline, " ", COMMAND_LINE_SIZE);
    43		}
    44	}
    45	#endif
    46	

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

      parent reply	other threads:[~2024-08-28 22:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-24 14:41 [PATCH] MIPS: fw: Gracefully handle unknown firmware protocols Bjørn Mork
2024-08-25 12:50 ` Jiaxun Yang
2024-08-25 13:56   ` Maciej W. Rozycki
2024-08-25 14:44   ` Bjørn Mork
2024-08-25 15:18     ` Maciej W. Rozycki
2024-08-25 15:47       ` Bjørn Mork
2024-08-25 19:59         ` Maciej W. Rozycki
2024-08-26  8:52           ` Bjørn Mork
2024-08-26 13:17     ` Jiaxun Yang
2024-08-28 22:15 ` kernel test robot [this message]

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=202408290501.kTATRaBZ-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Steven.Hill@imgtec.com \
    --cc=bjorn@mork.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=tsbogend@alpha.franken.de \
    /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