From: Heng Qi <hengqi@linux.alibaba.com>
To: Heng Qi <hengqi@linux.alibaba.com>
Cc: oe-kbuild-all@lists.linux.dev,
"Huacai Chen" <chenhuacai@loongson.cn>,
"Xuerui Wang" <kernel@xen0n.name>,
"Jiaxun Yang" <jiaxun.yang@flygoat.com>,
"Guo Ren" <guoren@kernel.org>,
loongarch@lists.linux.dev, "Jakub Kicinski" <kuba@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
"Paolo Abeni" <pabeni@redhat.com>,
"Eric Dumazet" <edumazet@google.com>,
"Jason Wang" <jasowang@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
"Brett Creeley" <bcreeley@amd.com>,
"Ratheesh Kannoth" <rkannoth@marvell.com>,
"Alexander Lobakin" <aleksander.lobakin@intel.com>,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
"Tal Gilboa" <talgi@nvidia.com>,
"Jonathan Corbet" <corbet@lwn.net>,
linux-doc@vger.kernel.org,
"Maxime Chevallier" <maxime.chevallier@bootlin.com>,
"Jiri Pirko" <jiri@resnulli.us>,
"Paul Greenwalt" <paul.greenwalt@intel.com>,
"Ahmed Zaki" <ahmed.zaki@intel.com>,
"Vladimir Oltean" <vladimir.oltean@nxp.com>,
"Kory Maincent" <kory.maincent@bootlin.com>,
"Andrew Lunn" <andrew@lunn.ch>,
justinstitt@google.com, donald.hunter@gmail.com,
"Eugenio Pérez" <eperezma@redhat.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Linux Memory Management List" <linux-mm@kvack.org>,
"Dragos Tatulea" <dtatulea@nvidia.com>,
"Rahul Rameshbabu" <rrameshbabu@nvidia.com>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
netdev@vger.kernel.org, virtualization@lists.linux.dev,
"kernel test robot" <lkp@intel.com>
Subject: Re: [PATCH net-next v14 3/5] ethtool: provide customized dim profile management
Date: Wed, 5 Jun 2024 10:13:30 +0800 [thread overview]
Message-ID: <1717553610.6275685-4-hengqi@linux.alibaba.com> (raw)
In-Reply-To: <1717478006.038663-1-hengqi@linux.alibaba.com>
On Tue, 4 Jun 2024 13:13:26 +0800, Heng Qi <hengqi@linux.alibaba.com> wrote:
> On Tue, 4 Jun 2024 07:00:35 +0800, kernel test robot <lkp@intel.com> wrote:
> > Hi Heng,
> >
> > kernel test robot noticed the following build warnings:
> >
> > [auto build test WARNING on net-next/main]
> >
> > url: https://github.com/intel-lab-lkp/linux/commits/Heng-Qi/linux-dim-move-useful-macros-to-h-file/20240603-235834
> > base: net-next/main
> > patch link: https://lore.kernel.org/r/20240603154727.31998-4-hengqi%40linux.alibaba.com
> > patch subject: [PATCH net-next v14 3/5] ethtool: provide customized dim profile management
> > config: loongarch-defconfig (https://download.01.org/0day-ci/archive/20240604/202406040645.6z95FW1f-lkp@intel.com/config)
> > compiler: loongarch64-linux-gcc (GCC) 13.2.0
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240604/202406040645.6z95FW1f-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/202406040645.6z95FW1f-lkp@intel.com/
> >
> > All warnings (new ones prefixed by >>):
> >
> > >> net/ethtool/coalesce.o: warning: objtool: unexpected relocation symbol type in .rela.discard.reachable
>
>
> I'm not sure if this seems to be related to the update of loongarch[1]?
> didn't find this warning on other architectures such as arm/openrisc/x86.
I noticed that the loongarch community has submitted a fix[1], and after applying
the fix, the robot no longer reports the warning. So the warning is specific
to the loongarch architecture.
[1] https://lore.kernel.org/all/20240604150741.30252-1-xry111@xry111.site/
Thanks.
>
> +Cc:
> loongarch@lists.linux.dev, Guo Ren <guoren@kernel.org>,
> Xuerui Wang <kernel@xen0n.name>,
> Jiaxun Yang <jiaxun.yang@flygoat.com>,
> Huacai Chen <chenhuacai@loongson.cn>
>
> [1] https://lore.kernel.org/all/20240322135619.1423490-1-chenhuacai@loongson.cn/
>
> >
> > --
> > 0-DAY CI Kernel Test Service
> > https://github.com/intel/lkp-tests/wiki
>
prev parent reply other threads:[~2024-06-05 2:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240603154727.31998-1-hengqi@linux.alibaba.com>
[not found] ` <20240603154727.31998-4-hengqi@linux.alibaba.com>
2024-06-03 23:00 ` kernel test robot
2024-06-04 5:13 ` Heng Qi
2024-06-05 2:13 ` Heng Qi [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=1717553610.6275685-4-hengqi@linux.alibaba.com \
--to=hengqi@linux.alibaba.com \
--cc=ahmed.zaki@intel.com \
--cc=akpm@linux-foundation.org \
--cc=aleksander.lobakin@intel.com \
--cc=andrew@lunn.ch \
--cc=bcreeley@amd.com \
--cc=chenhuacai@loongson.cn \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=eperezma@redhat.com \
--cc=guoren@kernel.org \
--cc=hkallweit1@gmail.com \
--cc=jasowang@redhat.com \
--cc=jiaxun.yang@flygoat.com \
--cc=jiri@resnulli.us \
--cc=justinstitt@google.com \
--cc=kernel@xen0n.name \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=loongarch@lists.linux.dev \
--cc=maxime.chevallier@bootlin.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=paul.greenwalt@intel.com \
--cc=rkannoth@marvell.com \
--cc=rrameshbabu@nvidia.com \
--cc=talgi@nvidia.com \
--cc=virtualization@lists.linux.dev \
--cc=vladimir.oltean@nxp.com \
--cc=xuanzhuo@linux.alibaba.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