linux-kernel - Re: dma_declare_coherent

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20210628162934.GA29578@lst.de>
Date:   Mon, 28 Jun 2021 18:29:34 +0200
From:   Christoph Hellwig <hch@....de>
To:     Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:     Christoph Hellwig <hch@....de>,
        Yoshinori Sato <ysato@...rs.sourceforge.jp>,
        Rich Felker <dalias@...c.org>,
        Linux-sh list <linux-sh@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: dma_declare_coherent_memory and SuperH

On Mon, Jun 28, 2021 at 04:29:18PM +0200, Geert Uytterhoeven wrote:
> On Wed, Jun 23, 2021 at 3:33 PM Christoph Hellwig <hch@....de> wrote:
> > I have a vague recollection that you were planning on dropping support
> > for non-devicetree platforms, is that still the case?
> >
> > The reason I'm asking is because all but one users of
> > dma_declare_coherent_memory are in the sh platform setup code, and
> > I'd really like to move towards killing this function off.
> 
> I guess you mean drivers/remoteproc/remoteproc_virtio.c?
> 
> BeagleV Starlight Beta will be adding two more in
> drivers/nvdla/nvdla_gem.c.
> https://github.com/esmil/linux/commit/ce5cffcc8e618604a0d442758321fc5577751c9d

As clearly documented adding new callers is not acceptable.  But I
don't really care about of of tree code anyway.