From: Bjorn Helgaas <helgaas@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
linux-pci@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ghennadi Procopciuc <ghennadi.procopciuc@oss.nxp.com>,
NXP S32 Linux Team <s32@nxp.com>,
"imx@lists.linux.dev" <imx@lists.linux.dev>,
linux-arm-kernel@lists.infradead.org
Subject: Re: linux-next: Tree for Nov 28 (drivers/pci/controller/dwc/pcie-nxp-s32g.o)
Date: Mon, 1 Dec 2025 11:23:11 -0600 [thread overview]
Message-ID: <20251201172311.GA3019571@bhelgaas> (raw)
In-Reply-To: <63e1daf7-f9a3-463e-8a1b-e9b72581c7af@infradead.org>
On Sat, Nov 29, 2025 at 07:00:04PM -0800, Randy Dunlap wrote:
> On 11/27/25 9:29 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20251127:
> >
>
> on i386 (allmodconfig):
>
> WARNING: modpost: vmlinux: section mismatch in reference: s32g_init_pcie_controller+0x2b (section: .text) -> memblock_start_of_DRAM (section: .init.text)
Thanks, I'll drop the pci/controller/s32g branch until this is
resolved.
next prev parent reply other threads:[~2025-12-01 17:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 5:29 linux-next: Tree for Nov 28 Stephen Rothwell
2025-11-28 13:11 ` [linux-next: vfs - regression] - merge error? Heiko Carstens
2025-11-28 15:52 ` Christian Brauner
2025-11-30 3:00 ` linux-next: Tree for Nov 28 (drivers/pci/controller/dwc/pcie-nxp-s32g.o) Randy Dunlap
2025-12-01 17:23 ` Bjorn Helgaas [this message]
2025-12-02 4:24 ` Manivannan Sadhasivam
2025-12-02 8:54 ` Vincent Guittot
2025-12-02 9:53 ` Manivannan Sadhasivam
2025-12-02 10:03 ` Vincent Guittot
2025-12-02 10:12 ` Manivannan Sadhasivam
2025-12-02 10:24 ` Vincent Guittot
2025-12-02 22:37 ` Randy Dunlap
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=20251201172311.GA3019571@bhelgaas \
--to=helgaas@kernel.org \
--cc=ghennadi.procopciuc@oss.nxp.com \
--cc=imx@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=s32@nxp.com \
--cc=sfr@canb.auug.org.au \
/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