From: "Liam Beguin" <liambeguin@gmail.com>
To: "kernel test robot" <lkp@intel.com>, <kishon@ti.com>, <vkoul@kernel.org>
Cc: <kbuild-all@lists.01.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/1] phy: tusb1210: use bitmasks to set VENDOR_SPECIFIC2
Date: Sat, 18 Jul 2020 16:18:25 -0400 [thread overview]
Message-ID: <C4A102A7YC2W.1LPN6MZLYYUKV@atris> (raw)
In-Reply-To: <202007150718.6LcA4qZN%lkp@intel.com>
On Wed Jul 15, 2020 at 7:48 AM kernel test robot wrote:
> Hi Liam,
>
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on 8f3d9f354286745c751374f5f1fcafee6b3f3136]
>
> url: https://github.com/0day-ci/linux/commits/Liam-Beguin/phy-tusb1210-use-bitmasks-to-set-VENDOR_SPECIFIC2/20200715-003517
> base: 8f3d9f354286745c751374f5f1fcafee6b3f3136
> config: parisc-allyesconfig (attached as .config)
> compiler: hppa-linux-gcc (GCC) 9.3.0
> reproduce (this is a W=1 build):
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=parisc
>
> 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 >>):
>
> hppa-linux-ld: drivers/phy/ti/phy-tusb1210.o: in function `tusb1210_probe':
> >> (.text+0x2f4): undefined reference to `__cmpxchg_called_with_bad_pointer'
> >> hppa-linux-ld: (.text+0x324): undefined reference to `__cmpxchg_called_with_bad_pointer'
> hppa-linux-ld: (.text+0x354): undefined reference to `__cmpxchg_called_with_bad_pointer'
>
Hi,
I sent another patch[1] to try to address this.
The issue seems to come from the fact that the parisc architecture
doesn't support cmpxchg on u8 pointers. cmpxchg is called by
set_mask_bits.
Thanks,
Liam
[1] https://lore.kernel.org/patchwork/patch/1272617/
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next prev parent reply other threads:[~2020-07-18 20:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 16:32 Liam Beguin
2020-07-14 23:48 ` kernel test robot
2020-07-18 20:18 ` Liam Beguin [this message]
[not found] ` <C4A103AM9MUU.13PG525K6BK54@atris>
2020-08-04 0:08 ` Liam Beguin
2020-08-05 6:31 ` Vinod Koul
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=C4A102A7YC2W.1LPN6MZLYYUKV@atris \
--to=liambeguin@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=vkoul@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®