mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: chalianis1@gmail.com, barebox@lists.infradead.org
Subject: Re: [PATCH] drivers: dma: refactor: rename dma_ops to dma_device_ops.
Date: Tue, 16 Sep 2025 08:33:56 +0200	[thread overview]
Message-ID: <aMkE1GgopPGoyHOA@pengutronix.de> (raw)
In-Reply-To: <bb89fc4d-fdf6-4a23-80bc-53b14ad9b30d@pengutronix.de>

On Mon, Sep 15, 2025 at 11:02:12AM +0200, Ahmad Fatoum wrote:
> Hi,
> 
> On 9/14/25 9:32 PM, chalianis1@gmail.com wrote:
> > From: Chali Anis <chalianis1@gmail.com>
> > 
> > This patch is an esthetic cleanup, rename the dma_ops to dma_device_ops
> > to be sure that the struct in drivers/dma is different from one used in
> > arch/riscv/cpu. I accidentally faced the issue telling that the struct is
> > defined in the two places but it is not supposed to happen since the
> > the driver is never selected from riscv.
> 
> If it's only about resolving the conflicting names, I'd rather rename
> dma_ops for RISC-V to dma_map_ops instead.

I thought about this as well, but I actually like using dma_device_ops.
We have a struct dma_device, so it's consistent to use a struct
dma_device_ops * in there.

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



      reply	other threads:[~2025-09-16  6:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-14 19:32 chalianis1
2025-09-15  9:00 ` Sascha Hauer
2025-09-15  9:02 ` Ahmad Fatoum
2025-09-16  6:33   ` 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=aMkE1GgopPGoyHOA@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=chalianis1@gmail.com \
    /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