From: Antony Pavlov <antonynpavlov@gmail.com>
To: Sascha Hauer <sha@pengutronix.de>,
Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox <barebox@lists.infradead.org>
Subject: move dma_ops to common code
Date: Thu, 16 Jun 2022 10:53:51 +0300 [thread overview]
Message-ID: <CAA4bVAE09vnuWLv3TvKDn3t7kAPdk1Tgto-TWzyo1-qoYpfO9A@mail.gmail.com> (raw)
Hi!
In 0e885ce81d0e ('RISC-V: dma: support multiple dma_alloc_coherent backends') ,
(see https://lore.barebox.org/barebox/20210619045055.779-10-a.fatoum@pengutronix.de/)
multiple dma_alloc_coherent backends was introduced for RISC-V.
At the moment MIPS dma_alloc_coherent stuff is messy and I want to rework it.
I can reuse some parts of 0e885ce81d0e by moving it to the common code.
Any comments or suggestions?
--
Best regards,
Antony Pavlov
next reply other threads:[~2022-06-16 8:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 7:53 Antony Pavlov [this message]
2022-06-20 14:52 ` Ahmad Fatoum
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=CAA4bVAE09vnuWLv3TvKDn3t7kAPdk1Tgto-TWzyo1-qoYpfO9A@mail.gmail.com \
--to=antonynpavlov@gmail.com \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=sha@pengutronix.de \
--subject='Re: move dma_ops to common code' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox