From: Joe Perches <joe@perches.com>
To: Sebastian Fricke <sebastian.fricke@posteo.net>
Cc: linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-pm@vger.kernel.org
Subject: Re: [PATCH] base: power: runtime.c: Remove a unnecessary space
Date: Sun, 18 Apr 2021 02:22:35 -0700 [thread overview]
Message-ID: <3886b37dacd9fcf84d5211322807128e638a8222.camel@perches.com> (raw)
In-Reply-To: <20210418091143.6h466qqd52uf766z@basti-TUXEDO-Book-XA1510>
On Sun, 2021-04-18 at 09:11 +0000, Sebastian Fricke wrote:
> Hey Joe,
Hi Sebastian.
> On 18.04.2021 00:09, Joe Perches wrote:
> > On Sun, 2021-04-18 at 06:08 +0000, Sebastian Fricke wrote:
> > > Remove a redundant space to improve the quality of the comment.
> > I think this patch is not useful.
> > It's not redundant.
>
> Thank you, I actually found this pattern a few more times but I wanted
> to check first if this is a mistake or chosen consciously.
[]
> > For drivers/base/power/runtime.c, that 2 space after period style is used
> > dozens of times and changing a single instance of it isn't very useful.
Even in that single file it's not consistent.
It's something like 3:1 for 2 spaces over 1 space after period.
I believe it's done more by habit and author age than anything.
If you learned to type using a typewriter and not a keyboard, then
you likely still use 2 spaces after a period.
> True and if I understand you correctly you would rather keep it as is
> right?
Yes. IMO: Whitespace in comments like this should not be changed
unless there's some other significant benefit like better alignment.
cheers, Joe
> > > ---
> > > Side-note:
> > > I found this while reading the code, I don't believe it is important but
> > > I thought it doesn't hurt to fix it.
[]
> > > diff --git a/drivers/base/power/runtime.c b/drivers/base/power/runtime.c
[]
> > > @@ -786,7 +786,7 @@ static int rpm_resume(struct device *dev, int rpmflags)
> > > }
> > >
> > > /*
> > > - * See if we can skip waking up the parent. This is safe only if
> > > + * See if we can skip waking up the parent. This is safe only if
> > > * power.no_callbacks is set, because otherwise we don't know whether
> > > * the resume will actually succeed.
> > > */
next prev parent reply other threads:[~2021-04-18 9:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-18 6:08 Sebastian Fricke
2021-04-18 7:09 ` Joe Perches
2021-04-18 9:11 ` Sebastian Fricke
2021-04-18 9:18 ` Pavel Machek
2021-04-18 9:22 ` Joe Perches [this message]
2021-04-19 15:16 ` Rafael J. Wysocki
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=3886b37dacd9fcf84d5211322807128e638a8222.camel@perches.com \
--to=joe@perches.com \
--cc=gregkh@linuxfoundation.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
--cc=sebastian.fricke@posteo.net \
/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
all inboxes | Powered by JetHome®