linux-kernel - Re: [PATCH] dmaengine: pl330: rename

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: <ZGzI+gsYdF6kEHFk@matsya>
Date:   Tue, 23 May 2023 19:38:58 +0530
From:   Vinod Koul <vkoul@...nel.org>
To:     Randy Dunlap <rdunlap@...radead.org>
Cc:     linux-kernel@...r.kernel.org,
        Jaswinder Singh <jassisinghbrar@...il.com>,
        Jaswinder Singh <jassi.brar@...sung.com>,
        Boojin Kim <boojin.kim@...sung.com>,
        Krzysztof Kozlowski <krzk@...nel.org>,
        Russell King <rmk+kernel@....linux.org.uk>,
        dmaengine@...r.kernel.org, linux-riscv@...ts.infradead.org
Subject: Re: [PATCH] dmaengine: pl330: rename _start to prevent build error

On 22-05-23, 17:06, Randy Dunlap wrote:
> "_start" is used in several arches and proably should be reserved
> for ARCH usage. Using it in a driver for a private symbol can cause
> a build error when it conflicts with ARCH usage of the same symbol.
> 
> Therefore rename pl330's "_start" to "_start_thread" so that there
> is no conflict and no build error.

Why not rename to pl330_start or pl330_start_thread to ensure we will
might not conflict ever!

-- 
~Vinod