From: Jiri Slaby <jirislaby@kernel.org>
To: Dan Carpenter <dan.carpenter@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dmitry Safonov <0x7f454c46@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] Input: sysrq: delete unnecessary check
Date: Thu, 7 Aug 2025 07:14:56 +0200 [thread overview]
Message-ID: <4db2a6cc-0520-4712-b823-df157e71e7f0@kernel.org> (raw)
In-Reply-To: <aJNAhHtKkhWjosDV@stanley.mountain>
On 06. 08. 25, 13:46, Dan Carpenter wrote:
> This code checks if (write) is true twice in a row. It's more
> readable to delete the first check.
Not sure why "Input" in $SUBJ, but regardless:
Reviewed-by: Jiri Slaby <jirislaby@kernel.org>
thanks,
--
js
suse labs
prev parent reply other threads:[~2025-08-07 5:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 11:46 [PATCH] Input: sysrq: delete unnecessary check Dan Carpenter
2025-08-07 5:14 ` Jiri Slaby [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=4db2a6cc-0520-4712-b823-df157e71e7f0@kernel.org \
--to=jirislaby@kernel.org \
--cc=0x7f454c46@gmail.com \
--cc=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
/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