From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH] dma: return NULL on dma_alloc_coherent failure
Date: Fri, 10 Jul 2026 23:35:20 +0200 [thread overview]
Message-ID: <178371932090.3542258.1570601136067314894.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20260709134111.3314089-1-a.fatoum@pengutronix.de>
On Thu, 09 Jul 2026 15:41:05 +0200, Ahmad Fatoum wrote:
> The majority of our calls to dma_alloc_coherent check for a NULL return
> that would indicate an error as that's the Linux API as well.
>
> In barebox, dma_alloc_coherent panics though. This mostly doesn't matter,
> because these are mostly fixed size allocations at driver probe time,
> but we have some older code like the Freescale UDC driver that allocates
> coherent memory out of a poller context.
>
> [...]
Applied, thanks!
[1/1] dma: return NULL on dma_alloc_coherent failure
https://git.pengutronix.de/cgit/barebox/commit/?id=467f5e1cc300 (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2026-07-10 21:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 13:41 Ahmad Fatoum
2026-07-10 21:35 ` 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=178371932090.3542258.1570601136067314894.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