Linux wireless drivers development
 help / color / mirror / Atom feed
From: Yujie Liu <yujie.liu@intel.com>
To: Kalle Valo <kvalo@kernel.org>
Cc: kernel test robot <lkp@intel.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	<linux-wireless@vger.kernel.org>
Subject: Re: [wireless-next:main] BUILD REGRESSION db7fac15eaf0f09d675730d7002edabe27fe9e1d
Date: Mon, 11 Dec 2023 13:51:22 +0800	[thread overview]
Message-ID: <ZXajWhhIJlSjanrA@yujie-X299> (raw)
In-Reply-To: <87cyvfn0jb.fsf@kernel.org>

Hi Kalle,

On Sat, Dec 09, 2023 at 12:16:40PM +0200, Kalle Valo wrote:
> 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.

Sorry this is a wrong info due to a bug of the bot. We've found the root
cause and fixed it just now. Sorry for the noise and please kindly
ignore it.

Best Regards,
Yujie

      reply	other threads:[~2023-12-11  5:55 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
2023-12-11  5:51   ` Yujie Liu [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=ZXajWhhIJlSjanrA@yujie-X299 \
    --to=yujie.liu@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=kvalo@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox