From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH master 1/2] dma: fix fixup warning for SoCs without /soc node
Date: Tue, 21 Jan 2025 09:22:18 +0100 [thread overview]
Message-ID: <173744773828.252265.8162965528675452631.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20250116141148.301230-1-a.fatoum@pengutronix.de>
On Thu, 16 Jan 2025 15:11:47 +0100, Ahmad Fatoum wrote:
> For SoCs without a /soc node, any DMA coherency fixups happen at the
> device tree root. The root's full name is an empty string in barebox, so
> this expectedly fails.
>
> Handle this case specially.
>
>
> [...]
Applied, thanks!
[1/2] dma: fix fixup warning for SoCs without /soc node
https://git.pengutronix.de/cgit/barebox/commit/?id=599fac02a837 (link may not be stable)
[2/2] kbuild: remove stale references to README
https://git.pengutronix.de/cgit/barebox/commit/?id=da7191a3fd74 (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2025-01-21 8:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 14:11 Ahmad Fatoum
2025-01-16 14:11 ` [PATCH master 2/2] kbuild: remove stale references to README Ahmad Fatoum
2025-01-21 8:22 ` Sascha Hauer [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=173744773828.252265.8162965528675452631.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.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