linux-kernel - Re: [PATCH] staging: fbtft: use guard() to simplify code

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] [day] [month] [year] [list]

Message-ID: <2026012929-disprove-certified-4057@gregkh>
Date: Thu, 29 Jan 2026 05:38:01 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Paul Retourné <paul.retourne@...nge.fr>
Cc: andy@...nel.org, dri-devel@...ts.freedesktop.org,
	linux-fbdev@...r.kernel.org, linux-staging@...ts.linux.dev,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging: fbtft: use guard() to simplify code

On Wed, Jan 28, 2026 at 10:26:42PM +0100, Paul Retourné wrote:
> Use guard() to simplify mutex locking. No functional change.

It's best to use guard() for new code, not touching existing code as:

>  3 files changed, 8 insertions(+), 8 deletions(-)

This made no change overall at all :(

thanks,

greg k-h