[pm:intel_idle+acpi 4/10] acpi_processor.c:undefined reference to `acpi_processor_ffh_cstate_probe'

[pm:intel_idle+acpi 4/10] acpi_processor.c:undefined reference to `acpi_processor_ffh_cstate_probe'

[kbuild test robot]

[-- Attachment #1: Type: text/plain, Size: 978 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git intel_idle+acpi
head:   dcedc03145600b929a32acb85b212131b079bc46
commit: 0300cf31f061e6287810c894337f29df2e200e2d [4/10] ACPI: processor: Export acpi_processor_evaluate_cst()
config: x86_64-randconfig-b002-20191216 (attached as .config)
compiler: gcc-7 (Debian 7.5.0-1) 7.5.0
reproduce:
        git checkout 0300cf31f061e6287810c894337f29df2e200e2d
        # save the attached .config to linux build tree
        make ARCH=x86_64 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   ld: drivers/acpi/acpi_processor.o: in function `acpi_processor_evaluate_cst':
>> acpi_processor.c:(.text+0x542): undefined reference to `acpi_processor_ffh_cstate_probe'

---
0-DAY kernel test infrastructure                 Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 41075 bytes --]

Re: [pm:intel_idle+acpi 4/10] acpi_processor.c:undefined reference to `acpi_processor_ffh_cstate_probe'

[Rafael J. Wysocki]

On Mon, Dec 16, 2019 at 2:26 PM kbuild test robot <lkp@intel.com> wrote:
>
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git intel_idle+acpi
> head:   dcedc03145600b929a32acb85b212131b079bc46
> commit: 0300cf31f061e6287810c894337f29df2e200e2d [4/10] ACPI: processor: Export acpi_processor_evaluate_cst()

Outdated.  Please stop sending these.

> config: x86_64-randconfig-b002-20191216 (attached as .config)
> compiler: gcc-7 (Debian 7.5.0-1) 7.5.0
> reproduce:
>         git checkout 0300cf31f061e6287810c894337f29df2e200e2d
>         # save the attached .config to linux build tree
>         make ARCH=x86_64
>
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
>    ld: drivers/acpi/acpi_processor.o: in function `acpi_processor_evaluate_cst':
> >> acpi_processor.c:(.text+0x542): undefined reference to `acpi_processor_ffh_cstate_probe'
>
> ---
> 0-DAY kernel test infrastructure                 Open Source Technology Center
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation

RE: [kbuild-all] Re: [pm:intel_idle+acpi 4/10] acpi_processor.c:undefined reference to `acpi_processor_ffh_cstate_probe'

[Li, Philip]

> Subject: [kbuild-all] Re: [pm:intel_idle+acpi 4/10] acpi_processor.c:undefined
> reference to `acpi_processor_ffh_cstate_probe'
> 
> On Mon, Dec 16, 2019 at 2:26 PM kbuild test robot <lkp@intel.com> wrote:
> >
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
> intel_idle+acpi
> > head:   dcedc03145600b929a32acb85b212131b079bc46
> > commit: 0300cf31f061e6287810c894337f29df2e200e2d [4/10] ACPI: processor:
> Export acpi_processor_evaluate_cst()
> 
> Outdated.  Please stop sending these.
thanks for the input Rafael, we will ignore the following tests on it.

> 
> > config: x86_64-randconfig-b002-20191216 (attached as .config)
> > compiler: gcc-7 (Debian 7.5.0-1) 7.5.0
> > reproduce:
> >         git checkout 0300cf31f061e6287810c894337f29df2e200e2d
> >         # save the attached .config to linux build tree
> >         make ARCH=x86_64
> >
> > If you fix the issue, kindly add following tag
> > Reported-by: kbuild test robot <lkp@intel.com>
> >
> > All errors (new ones prefixed by >>):
> >
> >    ld: drivers/acpi/acpi_processor.o: in function `acpi_processor_evaluate_cst':
> > >> acpi_processor.c:(.text+0x542): undefined reference to
> `acpi_processor_ffh_cstate_probe'
> >
> > ---
> > 0-DAY kernel test infrastructure                 Open Source Technology Center
> > https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
> _______________________________________________
> kbuild-all mailing list -- kbuild-all@lists.01.org
> To unsubscribe send an email to kbuild-all-leave@lists.01.org

Re: [kbuild-all] Re: [pm:intel_idle+acpi 4/10] acpi_processor.c:undefined reference to `acpi_processor_ffh_cstate_probe'

[Rafael J. Wysocki]

On Tue, Dec 17, 2019 at 1:31 AM Li, Philip <philip.li@intel.com> wrote:
>
> > Subject: [kbuild-all] Re: [pm:intel_idle+acpi 4/10] acpi_processor.c:undefined
> > reference to `acpi_processor_ffh_cstate_probe'
> >
> > On Mon, Dec 16, 2019 at 2:26 PM kbuild test robot <lkp@intel.com> wrote:
> > >
> > > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
> > intel_idle+acpi
> > > head:   dcedc03145600b929a32acb85b212131b079bc46
> > > commit: 0300cf31f061e6287810c894337f29df2e200e2d [4/10] ACPI: processor:
> > Export acpi_processor_evaluate_cst()
> >
> > Outdated.  Please stop sending these.
> thanks for the input Rafael, we will ignore the following tests on it.

Well, the branch has been rebased since then and effectively it is a new one.

My point is that if something like that happens, the script should
discard the old branch and pull the new one from scratch.

Re: [kbuild-all] Re: [pm:intel_idle+acpi 4/10] acpi_processor.c:undefined reference to `acpi_processor_ffh_cstate_probe'

[Philip Li]

On Tue, Dec 17, 2019 at 09:23:14AM +0100, Rafael J. Wysocki wrote:
> On Tue, Dec 17, 2019 at 1:31 AM Li, Philip <philip.li@intel.com> wrote:
> >
> > > Subject: [kbuild-all] Re: [pm:intel_idle+acpi 4/10] acpi_processor.c:undefined
> > > reference to `acpi_processor_ffh_cstate_probe'
> > >
> > > On Mon, Dec 16, 2019 at 2:26 PM kbuild test robot <lkp@intel.com> wrote:
> > > >
> > > > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
> > > intel_idle+acpi
> > > > head:   dcedc03145600b929a32acb85b212131b079bc46
> > > > commit: 0300cf31f061e6287810c894337f29df2e200e2d [4/10] ACPI: processor:
> > > Export acpi_processor_evaluate_cst()
> > >
> > > Outdated.  Please stop sending these.
> > thanks for the input Rafael, we will ignore the following tests on it.
> 
> Well, the branch has been rebased since then and effectively it is a new one.
> 
> My point is that if something like that happens, the script should
> discard the old branch and pull the new one from scratch.
Got it, sorry for wrong understanding. We will add logic to judge the rebase
to reduce the later meaningless reports. Currently we only support the checking
of new patch set version in mailing list.