linux-kernel - Re: [PATCH v1] spi: intel: make mem_ops comparison unique to opcode match

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: <20231118063010.GJ17433@black.fi.intel.com>
Date:   Sat, 18 Nov 2023 08:30:10 +0200
From:   Mika Westerberg <mika.westerberg@...ux.intel.com>
To:     Raag Jadav <raag.jadav@...el.com>
Cc:     broonie@...nel.org, andriy.shevchenko@...ux.intel.com,
        linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] spi: intel: make mem_ops comparison unique to opcode
 match

On Fri, Nov 17, 2023 at 08:10:53PM +0530, Raag Jadav wrote:
> Instead of comparing parameters for every supported mem_ops, only compare
> on opcode match, which is relatively more efficient.
> 
> Signed-off-by: Raag Jadav <raag.jadav@...el.com>

Reviewed-by: Mika Westerberg <mika.westerberg@...ux.intel.com>