[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <73d3d8ed2cb4ca1b06902b767fe529c3@walle.cc>
Date: Thu, 10 Feb 2022 09:04:26 +0100
From: Michael Walle <michael@...le.cc>
To: Tudor.Ambarus@...rochip.com
Cc: linux-mtd@...ts.infradead.org, linux-kernel@...r.kernel.org,
p.yadav@...com, miquel.raynal@...tlin.com, richard@....at,
vigneshr@...com
Subject: Re: [PATCH v1 05/14] mtd: spi-nor: xilinx: rename vendor specific
functions and defines
Am 2022-02-10 04:08, schrieb Tudor.Ambarus@...rochip.com:
> On 2/2/22 16:58, Michael Walle wrote:
>> EXTERNAL EMAIL: Do not click links or open attachments unless you know
>> the content is safe
>>
>> Drop the generic spi_nor prefix for all the xilinx functions.
>
> mm, no, I would keep the spi_nor prefix because xilinx_sr_ready is too
> generic and can conflict with methods from other subsystems.
But all the other functions in this file start with xilinx_ ;)
I don't have a strong opinion here, other than it shouldn't
be called spi_nor_read_blaba() because that looks like a
standard spi nor function belonging in core.c
-michael
Powered by blists - more mailing lists