From: Will Deacon <will@kernel.org>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: Robin Murphy <robin.murphy@arm.com>,
netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, iommu@lists.linux.dev,
linux-ext4@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
dmaengine@vger.kernel.org,
Marek Szyprowski <m.szyprowski@samsung.com>,
Theodore Ts'o <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Vinod Koul <vkoul@kernel.org>, Frank Li <Frank.Li@kernel.org>
Subject: Re: BUG: net-next (7.0-rc6 based and later) fails to boot on Jetson Xavier NX
Date: Thu, 9 Apr 2026 13:24:41 +0100 [thread overview]
Message-ID: <adeaiSAnkaggqPsA@willie-the-truck> (raw)
In-Reply-To: <adayAMR_dEA6W5vW@shell.armlinux.org.uk>
On Wed, Apr 08, 2026 at 08:52:32PM +0100, Russell King (Oracle) wrote:
> What's the status on the iommu fix? Is it merged into mainline yet?
> If it isn't already, that means net-next remains unbootable going
> into the merge window without manually carrying the fix locally.
I'll pick it up for 7.0 in the iommu tree.
Will
next prev parent reply other threads:[~2026-04-09 12:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <adZTGOjjJrVJOcT8@shell.armlinux.org.uk>
[not found] ` <adZfTi3R6jtsjXx-@shell.armlinux.org.uk>
2026-04-08 16:08 ` BUG: net-next (7.0-rc6 based and later) fails to boot on Jetson Xavier NX Russell King (Oracle)
2026-04-08 16:16 ` Russell King (Oracle)
2026-04-08 16:40 ` Robin Murphy
2026-04-08 19:52 ` Russell King (Oracle)
2026-04-09 12:24 ` Will Deacon [this message]
2026-04-09 15:37 ` Linus Torvalds
2026-04-09 16:16 ` Russell King (Oracle)
2026-04-08 16:22 ` Linus Torvalds
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=adeaiSAnkaggqPsA@willie-the-truck \
--to=will@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=adilger.kernel@dilger.ca \
--cc=dmaengine@vger.kernel.org \
--cc=iommu@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=m.szyprowski@samsung.com \
--cc=netdev@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=vkoul@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