All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chanwoo Choi <cw00.choi@samsung.com>
To: kbuild-all@lists.01.org
Subject: Re: [chanwoo:devfreq-testing 12/16] arceb-elf-ld: tegra30-devfreq.c:undefined reference to `tegra_sku_info'
Date: Thu, 26 Nov 2020 18:18:42 +0900	[thread overview]
Message-ID: <8c01dfef-1cbc-822b-575a-e12e943f9c90@samsung.com> (raw)
In-Reply-To: <20201124101105.GA25587@kozik-lap>

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

Hi Krzysztof,

On 11/24/20 7:11 PM, Krzysztof Kozlowski wrote:
> On Tue, Nov 24, 2020 at 10:34:53AM +0900, Chanwoo Choi wrote:
>> + Krzysztof Kozlowski
>>
>> On 11/23/20 8:02 PM, Dmitry Osipenko wrote:
>>> 23.11.2020 10:29, Chanwoo Choi пишет:
>>>> Hi Dmitry,
>>>>
>>>> On 11/14/20 7:16 AM, kernel test robot wrote:
>>>>> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/linux.git devfreq-testing
>>>>> head:   24353caf6d50c7ddccd48435d34f79182c0b3923
>>>>> commit: e56035f87752d8663188ca8507099f6c7172f053 [12/16] PM / devfreq: tegra30: Support interconnect and OPPs from device-tree
>>>>> config: arc-randconfig-c003-20201113 (attached as .config)
>>>>> compiler: arceb-elf-gcc (GCC) 9.3.0
>>>>> reproduce (this is a W=1 build):
>>>>>         wget https://protect2.fireeye.com/v1/url?k=7ccf28b1-235411ab-7ccea3fe-0cc47a6cba04-e2247e2fae4671e2&q=1&e=1034e496-a416-46d0-8795-74cdeb44922c&u=https%3A%2F%2Fraw.githubusercontent.com%2Fintel%2Flkp-tests%2Fmaster%2Fsbin%2Fmake.cross -O ~/bin/make.cross
>>>>>         chmod +x ~/bin/make.cross
>>>>>         # https://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/linux.git/commit/?id=e56035f87752d8663188ca8507099f6c7172f053
>>>>>         git remote add chanwoo https://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/linux.git
>>>>>         git fetch --no-tags chanwoo devfreq-testing
>>>>>         git checkout e56035f87752d8663188ca8507099f6c7172f053
>>>>>         # save the attached .config to linux build tree
>>>>>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arc 
>>>>>
>>>>> If you fix the issue, kindly add following tag as appropriate
>>>>> Reported-by: kernel test robot <lkp@intel.com>
>>>>>
>>>>> All errors (new ones prefixed by >>):
>>>>>
>>>>>    arceb-elf-ld: drivers/devfreq/tegra30-devfreq.o: in function `tegra_devfreq_probe':
>>>>>    tegra30-devfreq.c:(.text+0x10a): undefined reference to `tegra_sku_info'
>>>>
>>>>
>>>> Do you know about this build issue?
>>>
>>> It happens because yours devfreq tree doesn't have the soc/tegra patch
>>> which adds a stub for tegra_sku_info. This patch is already queued by
>>> Krzysztof Kozlowski [1] and available in linux-next [2]. Hence there is
>>> no real problem here, this COMPILE_TEST build issue will be fixed
>>> naturally once all the patches will be merged into the Linus' tree.
>>
>> Actually before merging all patches to linus git repo, it is problem.
>> And if this case, have to make the immutable branch and then send
>> the pull request to other maintainer or merge the patches to one git repo.
> 
> Chanwoo is right here, it is a problem. The merge result will not be
> bisectable (at least under compile testing).
> 
>> Hi Krzysztof,
>> The devfreq patch depends on patch[1] was already merged to linux-mem-ctrl.git.
>> Could you make the immutable branch and share it?
> 
> Of course, give me few minutes, please.

Thanks for your pull request.

-- 
Best Regards,
Chanwoo Choi
Samsung Electronics

      reply	other threads:[~2020-11-26  9:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-13 22:16 [chanwoo:devfreq-testing 12/16] arceb-elf-ld: tegra30-devfreq.c:undefined reference to `tegra_sku_info' kernel test robot
2020-11-23  7:29 ` Chanwoo Choi
2020-11-23 11:02   ` Dmitry Osipenko
2020-11-24  1:34     ` Chanwoo Choi
2020-11-24 10:11       ` Krzysztof Kozlowski
2020-11-26  9:18         ` Chanwoo Choi [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=8c01dfef-1cbc-822b-575a-e12e943f9c90@samsung.com \
    --to=cw00.choi@samsung.com \
    --cc=kbuild-all@lists.01.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.