From: Heiko Carstens <hca@linux.ibm.com>
To: Alexander Gordeev <agordeev@linux.ibm.com>
Cc: Jason Wang <wangborong@cdjrlc.com>,
svens@linux.ibm.com, gor@linux.ibm.com,
borntraeger@linux.ibm.com, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] s390/delay: Fix comment typo
Date: Wed, 20 Jul 2022 11:23:15 +0200 [thread overview]
Message-ID: <YtfJgyVQzgkzSouS@osiris> (raw)
In-Reply-To: <Ytb2V3ay5qMY3yt+@li-4a3a4a4c-28e5-11b2-a85c-a8d192c6f089.ibm.com>
On Tue, Jul 19, 2022 at 08:22:15PM +0200, Alexander Gordeev wrote:
> On Fri, Jul 15, 2022 at 12:36:10PM +0800, Jason Wang wrote:
> > The double `that' is duplicated in line 19, remove one.
> >
> > Signed-off-by: Jason Wang <wangborong@cdjrlc.com>
> > ---
> > arch/s390/lib/delay.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/arch/s390/lib/delay.c b/arch/s390/lib/delay.c
> > index f7f5adea8940..c32bc8f7c1fd 100644
> > --- a/arch/s390/lib/delay.c
> > +++ b/arch/s390/lib/delay.c
> > @@ -16,7 +16,7 @@ void __delay(unsigned long loops)
> > /*
> > * To end the bloody studid and useless discussion about the
> > * BogoMips number I took the liberty to define the __delay
> > - * function in a way that that resulting BogoMips number will
> > + * function in a way that resulting BogoMips number will
> > * yield the megahertz number of the cpu. The important function
> > * is udelay and that is done using the tod clock. -- martin.
> > */
>
> Applied, thanks!
Ahem :) That should have been actually "fixed" to "that the", instead
of removing the double "that". And by the way, just two lines above is
another obvious typo...
But seriously, the whole comment is entirely outdated and simply
wrong. We don't use __delay() to calculate the BogoMips number, nor
does the function return a value that correlates with the megahertz
number of the cpu nowadays. It just loops a random time (where the cpu
is free to detect the pointless loop and optimize it away anyway).
So the right thing to do would be to remove the complete comment, and
maybe add a new comment - but please don't apply this patch.
prev parent reply other threads:[~2022-07-20 9:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 4:36 [PATCH] s390/delay: Fix comment typo Jason Wang
2022-07-19 18:22 ` Alexander Gordeev
2022-07-20 9:23 ` Heiko Carstens [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=YtfJgyVQzgkzSouS@osiris \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=svens@linux.ibm.com \
--cc=wangborong@cdjrlc.com \
/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