From: Bob Tracy <rct@frus.com>
To: linux-alpha@vger.kernel.org
Cc: richard.henderson@linaro.org, ink@jurassic.park.msu.ru,
mattst88@gmail.com
Subject: Re: [PATCH] alpha: Fix double word in comments
Date: Wed, 31 Aug 2022 17:09:09 -0500 [thread overview]
Message-ID: <Yw/cBRA2FIsW7QhN@gherkin.frus.com> (raw)
In-Reply-To: <20220830074202.11274-1-dengshaomin@cdjrlc.com>
On Tue, Aug 30, 2022 at 03:42:02AM -0400, Shaomin Deng wrote:
> Delete the rebundant word "and" in comments.
>
> Signed-off-by: Shaomin Deng <dengshaomin@cdjrlc.com>
> ---
> arch/alpha/kernel/irq_i8259.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/alpha/kernel/irq_i8259.c b/arch/alpha/kernel/irq_i8259.c
> index 1dcf0d9038fd..db574dcd6675 100644
> --- a/arch/alpha/kernel/irq_i8259.c
> +++ b/arch/alpha/kernel/irq_i8259.c
> @@ -147,7 +147,7 @@ isa_no_iack_sc_device_interrupt(unsigned long vector)
> */
> /*
> * The first read of gives you *all* interrupting lines.
> - * Therefore, read the mask register and and out those lines
> + * Therefore, read the mask register and out those lines
> * not enabled. Note that some documentation has 21 and a1
> * write only. This is not true.
> */
> --
> 2.35.1
This may have been beaten to death elsewhere, but the comment without
the second "and" doesn't make any sense, so I conclude the second "and"
is a logic operation. As in, "... and AND out those lines...". If that
is the case, capitalization will help disambiguate, much as I would expect
to see "OR" if that was the intended operation. The code following the
read of the mask register (not included in the diff fragment above) should
make the meaning clear.
Accordingly, I would reject this proposed patch.
Respectfully,
--Bob
prev parent reply other threads:[~2022-08-31 22:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 7:42 [PATCH] alpha: Fix double word in comments Shaomin Deng
2022-08-30 14:52 ` Richard Henderson
2022-08-31 21:00 ` Michael Cree
2022-08-31 22:09 ` Bob Tracy [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=Yw/cBRA2FIsW7QhN@gherkin.frus.com \
--to=rct@frus.com \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-alpha@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=richard.henderson@linaro.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