From: Kalle Valo <kvalo@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: Re: [wireless-next:main] BUILD REGRESSION db7fac15eaf0f09d675730d7002edabe27fe9e1d
Date: Sat, 09 Dec 2023 12:16:40 +0200 [thread overview]
Message-ID: <87cyvfn0jb.fsf@kernel.org> (raw)
In-Reply-To: <202312090036.jwmcWv2Y-lkp@intel.com> (kernel test robot's message of "Sat, 09 Dec 2023 00:59:40 +0800")
kernel test robot <lkp@intel.com> writes:
> tree/branch:
> https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git
> main
> branch HEAD: db7fac15eaf0f09d675730d7002edabe27fe9e1d wifi: rtw89:
> mac: refine SER setting during WiFi CPU power on
>
> Error/Warning ids grouped by kconfigs:
>
> gcc_recent_errors
> `-- mips-allyesconfig
> |-- (.ref.text):relocation-truncated-to-fit:R_MIPS_26-against-start_secondary
> |-- (.text):relocation-truncated-to-fit:R_MIPS_26-against-kernel_entry
> |--
> | main.c:(.init.text):relocation-truncated-to-fit:R_MIPS_26-against-__sanitizer_cov_trace_pc
> `-- main.c:(.init.text):relocation-truncated-to-fit:R_MIPS_26-against-_mcount
I assume this is a bug in build servers or elsewhere. I don't think a
wireless patch could cause this.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-12-09 10:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 16:59 [wireless-next:main] BUILD REGRESSION db7fac15eaf0f09d675730d7002edabe27fe9e1d kernel test robot
2023-12-09 10:16 ` Kalle Valo [this message]
2023-12-11 5:51 ` Yujie Liu
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=87cyvfn0jb.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=lkp@intel.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 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.