Linux PCI subsystem development
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Mario Limonciello <superm1@kernel.org>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
	linux-pci@vger.kernel.org,  kernel test robot <lkp@intel.com>
Subject: Re: [pci:for-linus] BUILD REGRESSION f0bfeb2c51e44bee7876f2a0eda3518bd2c30a01
Date: Thu, 16 Oct 2025 20:45:55 +0300 (EEST)	[thread overview]
Message-ID: <e31f6ac5-ebb6-9989-60ac-014054f1fd73@linux.intel.com> (raw)
In-Reply-To: <bdee889f-b154-4532-ba8d-ae5910ce1613@kernel.org>

On Thu, 16 Oct 2025, Mario Limonciello wrote:

> On 10/16/25 11:28 AM, Bjorn Helgaas wrote:
> > On Thu, Oct 16, 2025 at 11:18:38AM -0500, Mario Limonciello wrote:
> > > On 10/16/25 11:15 AM, Bjorn Helgaas wrote:
> > > > On Thu, Oct 16, 2025 at 07:26:50AM +0800, kernel test robot wrote:
> > > > > tree/branch:
> > > > > https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git for-linus
> > > > > branch HEAD: f0bfeb2c51e44bee7876f2a0eda3518bd2c30a01  PCI/VGA: Select
> > > > > SCREEN_INFO on X86
> > > > 
> > > > Just making sure you've seen this, Mario.
> > > 
> > > I didn't see this, thanks for including me.
> > > 
> > > > I *think* f0bfeb2c51e4 is
> > > > the most recent version, and it was on pci/for-linus, so I'll drop it
> > > > for now.
> > > 
> > > Are you sure the failure is caused by "PCI/VGA: Select SCREEN_INFO on
> > > X86"?
> > 
> > I'm not sure.  I looked briefly for a more detailed report but didn't
> > find it.  Maybe didn't look hard enough.  This email seems like a
> > summary that could possibly have included a link to details.
> 
> I looked at https://lore.kernel.org/oe-kbuild-all/ and don't see one there
> either.
> 
> I think you should keep the patch in.  As it pertains to arch specific stuff
> it behaves identically to pre-337bf13aa9dda.
> 
> If I'm wrong and there is actually still a problem we'll get more build robot
> reports as they come.
> 
> > 
> > > I wouldn't expect the below error to be:
> > > 
> > > > 
> > > > > Error/Warning ids grouped by kconfigs:
> > > > > 
> > > > > recent_errors
> > > > > `-- mips-allyesconfig
> > > > >       |--
> > > > > (.head.text):relocation-truncated-to-fit:R_MIPS_26-against-kernel_entry
> > > > >       `--
> > > > > (.ref.text):relocation-truncated-to-fit:R_MIPS_26-against-start_secondary

Looks unrelated to me. These "summary" reports from lkp often contain 
unrelated errors, I think there's even mention about it somewhere in 
the report text (probably before the part which was quoted to the list).

-- 
 i.


  parent reply	other threads:[~2025-10-16 17:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-15 23:26 [pci:for-linus] BUILD REGRESSION f0bfeb2c51e44bee7876f2a0eda3518bd2c30a01 kernel test robot
2025-10-16 16:15 ` Bjorn Helgaas
2025-10-16 16:18   ` Mario Limonciello
2025-10-16 16:28     ` Bjorn Helgaas
2025-10-16 16:35       ` Mario Limonciello
2025-10-16 17:14         ` Bjorn Helgaas
2025-10-16 17:45         ` Ilpo Järvinen [this message]
2025-10-17  3:13           ` Philip Li

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=e31f6ac5-ebb6-9989-60ac-014054f1fd73@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=helgaas@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=superm1@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