From: Greg KH <gregkh@linuxfoundation.org>
To: "Paul Retourné" <paul.retourne@orange.fr>
Cc: andy@kernel.org, dri-devel@lists.freedesktop.org,
linux-fbdev@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: fbtft: use guard() to simplify code
Date: Thu, 29 Jan 2026 05:38:01 +0100 [thread overview]
Message-ID: <2026012929-disprove-certified-4057@gregkh> (raw)
In-Reply-To: <20260128212644.1170970-1-paul.retourne@orange.fr>
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
prev parent reply other threads:[~2026-01-29 4:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 21:26 [PATCH] staging: fbtft: use guard() to simplify code Paul Retourné
2026-01-28 22:08 ` Andy Shevchenko
2026-01-29 9:18 ` Paul Retourne
2026-01-29 4:38 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026012929-disprove-certified-4057@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andy@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=paul.retourne@orange.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox