From: Narayana Murty N <nnmlinux@linux.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>, kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Vaibhav Jain <vaibhav@linux.ibm.com>
Subject: Re: [linux-next:master 10289/12187] eeh_pseries.c:undefined reference to `eeh_pe_inject_mmio_error'
Date: Tue, 17 Sep 2024 19:01:31 +0530 [thread overview]
Message-ID: <6f2158e4-f648-4d51-90e0-0816a6cc321e@linux.ibm.com> (raw)
In-Reply-To: <87ed5jqdqp.fsf@mail.lhotse>
On 17/09/24 6:48 AM, Michael Ellerman wrote:
> kernel test robot <lkp@intel.com> writes:
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>> head: 7083504315d64199a329de322fce989e1e10f4f7
>> commit: b0e2b828dfca645a228f8c89d12fbc2baecfb7ea [10289/12187] powerpc/pseries/eeh: Fix pseries_eeh_err_inject
>> config: powerpc64-randconfig-003-20231031 (https://download.01.org/0day-ci/archive/20240917/202409170509.VWC6jadC-lkp@intel.com/config)
>> compiler: powerpc64-linux-gcc (GCC) 13.3.0
>> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240917/202409170509.VWC6jadC-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/202409170509.VWC6jadC-lkp@intel.com/
>>
>> All errors (new ones prefixed by >>):
>>
>> powerpc64-linux-ld: arch/powerpc/platforms/pseries/eeh_pseries.o: in function `pseries_eeh_err_inject':
>>>> eeh_pseries.c:(.text+0x9d0): undefined reference to `eeh_pe_inject_mmio_error'
> Cause by CONFIG_DEBUG_FS=n.
>
> Looks like eeh_debugfs_break_device() needs to be moved out of the
> #ifdef CONFIG_DEBUG_FS block, and renamed.
>
> cheers
yes Michael Ellerman, it is fixed by new patch
https://lore.kernel.org/all/20240917132445.3868016-1-nnmlinux@linux.ibm.com/
.
regards,
Narayana Murty
prev parent reply other threads:[~2024-09-17 13:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 21:41 kernel test robot
2024-09-17 1:18 ` Michael Ellerman
2024-09-17 13:31 ` Narayana Murty N [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=6f2158e4-f648-4d51-90e0-0816a6cc321e@linux.ibm.com \
--to=nnmlinux@linux.ibm.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=mpe@ellerman.id.au \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vaibhav@linux.ibm.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