public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
	Linux Next Mailing List <linux-next@vger•kernel.org>,
	linux-pci@vger•kernel.org
Cc: 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: Sat, 29 Nov 2025 19:00:04 -0800	[thread overview]
Message-ID: <63e1daf7-f9a3-463e-8a1b-e9b72581c7af@infradead.org> (raw)
In-Reply-To: <20251128162928.36eec2d6@canb.auug.org.au>



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)


-- 
~Randy


  parent reply	other threads:[~2025-11-30  3:00 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 ` Randy Dunlap [this message]
2025-12-01 17:23   ` linux-next: Tree for Nov 28 (drivers/pci/controller/dwc/pcie-nxp-s32g.o) Bjorn Helgaas
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=63e1daf7-f9a3-463e-8a1b-e9b72581c7af@infradead.org \
    --to=rdunlap@infradead$(echo .)org \
    --cc=ghennadi.procopciuc@oss$(echo .)nxp.com \
    --cc=imx@lists$(echo .)linux.dev \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linux-pci@vger$(echo .)kernel.org \
    --cc=s32@nxp$(echo .)com \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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