From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Neil Armstrong <narmstrong@baylibre.com>
Subject: Re: [linux-next:master 3720/8237] mips64el-linux-ld: warning: orphan section `.ctors.65436' from `drivers/pinctrl/meson/pinctrl-meson.o' being placed in section `.ctors.65436'
Date: Wed, 4 May 2022 12:01:26 +0300 [thread overview]
Message-ID: <YnJA5mlXAa/F1orG@smile.fi.intel.com> (raw)
In-Reply-To: <202205041350.Pws5tIo2-lkp@intel.com>
On Wed, May 04, 2022 at 02:00:26PM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 44a2f39e611ac0bc1f17c288a583d7f2e5684aa7
> commit: 6671d0bc17866f71b8ca7ea3fb7e6dfc2a8069d2 [3720/8237] pinctrl: meson: Enable COMPILE_TEST
> config: mips-randconfig-r014-20220502 (https://download.01.org/0day-ci/archive/20220504/202205041350.Pws5tIo2-lkp@intel.com/config)
> compiler: mips64el-linux-gcc (GCC) 11.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
> # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=6671d0bc17866f71b8ca7ea3fb7e6dfc2a8069d2
> git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git fetch --no-tags linux-next master
> git checkout 6671d0bc17866f71b8ca7ea3fb7e6dfc2a8069d2
> # save the config file
> mkdir build_dir && cp config build_dir/.config
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=mips SHELL=/bin/bash
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All warnings (new ones prefixed by >>):
Looking at this list the "new" warning is not new and not related to the patch
in question. I.o.w. it's a false positive (to some extent).
--
With Best Regards,
Andy Shevchenko
next parent reply other threads:[~2022-05-04 9:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202205041350.Pws5tIo2-lkp@intel.com>
2022-05-04 9:01 ` Andy Shevchenko [this message]
2022-05-06 8:22 ` Chen, Rong A
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=YnJA5mlXAa/F1orG@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=narmstrong@baylibre.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