public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Haoxiang Li <lihaoxiang@isrc.iscas.ac.cn>, fthain@linux-m68k.org
Cc: oe-kbuild-all@lists.linux.dev, linux-m68k@lists.linux-m68k.org,
	linux-kernel@vger.kernel.org,
	Haoxiang Li <lihaoxiang@isrc.iscas.ac.cn>
Subject: Re: [PATCH] nubus: add a cleanup in nubus_init()
Date: Sat, 13 Dec 2025 10:25:49 +0800	[thread overview]
Message-ID: <202512131055.DdhG2azK-lkp@intel.com> (raw)
In-Reply-To: <20251212122930.36115-1-lihaoxiang@isrc.iscas.ac.cn>

Hi Haoxiang,

kernel test robot noticed the following build errors:

[auto build test ERROR on gerg-m68knommu/for-next]
[also build test ERROR on linus/master v6.18 next-20251212]
[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/Haoxiang-Li/nubus-add-a-cleanup-in-nubus_init/20251212-203606
base:   https://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git for-next
patch link:    https://lore.kernel.org/r/20251212122930.36115-1-lihaoxiang%40isrc.iscas.ac.cn
patch subject: [PATCH] nubus: add a cleanup in nubus_init()
config: m68k-defconfig (https://download.01.org/0day-ci/archive/20251213/202512131055.DdhG2azK-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251213/202512131055.DdhG2azK-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/202512131055.DdhG2azK-lkp@intel.com/

All errors (new ones prefixed by >>):

   drivers/nubus/nubus.c: In function 'nubus_init':
>> drivers/nubus/nubus.c:887:29: error: 'nubus_parent' undeclared (first use in this function); did you mean 'nubus_dirent'?
     887 |                 put_device(&nubus_parent);
         |                             ^~~~~~~~~~~~
         |                             nubus_dirent
   drivers/nubus/nubus.c:887:29: note: each undeclared identifier is reported only once for each function it appears in


vim +887 drivers/nubus/nubus.c

   876	
   877	static int __init nubus_init(void)
   878	{
   879		int err;
   880	
   881		if (!MACH_IS_MAC)
   882			return 0;
   883	
   884		nubus_proc_init();
   885		err = nubus_parent_device_register();
   886		if (err) {
 > 887			put_device(&nubus_parent);
   888			return err;
   889		}
   890		nubus_scan_bus();
   891		return 0;
   892	}
   893	

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

      parent reply	other threads:[~2025-12-13  2:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-12 12:29 [PATCH] nubus: add a cleanup in nubus_init() Haoxiang Li
2025-12-12 12:40 ` Daniel Palmer
2025-12-13  2:25 ` 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=202512131055.DdhG2azK-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=fthain@linux-m68k.org \
    --cc=lihaoxiang@isrc.iscas.ac.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox