From: Phil Auld <pauld@redhat.com>
To: Paul Sherwood <paul.sherwood@codethink.co.uk>
Cc: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
bristot@redhat.com, vschneid@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched/deadline: Fix grammar and typos in comments
Date: Mon, 13 May 2024 12:25:19 -0400 [thread overview]
Message-ID: <20240513162519.GC9998@lorien.usersys.redhat.com> (raw)
In-Reply-To: <ef7021835015a5bdd5bf5404ee712853@codethink.co.uk>
On Mon, May 13, 2024 at 04:19:10PM +0100 Paul Sherwood wrote:
> On 2024-05-13 14:58, Phil Auld wrote:
> > On Sat, May 11, 2024 at 09:26:44AM +0100 Paul Sherwood wrote:
> > > - conjugate verb to match subject of sentence
> > > - s/a entity/an entity/g
> > > - s/this misbehave/this misbehaviour/
> > > - a few typos
> > >
> > - not starting all the lines of a commit message with "-", priceless.
> >
> > Plus, you're just repeating what's in the actual patch.
> >
> > Otherwise, these changes themselves look good to me.
>
> Thanks for the feedback - would you like me to re-submit without the
> bullet-points, or without the text entirely?
>
Personally I'd rather a sentence or two saying something like
"Fix some types and grammar issues in sched deadline comments."
Or something. I know that's basically same as the title, but
that gets lost in the subject line, so maybe worded a little
differently? For this it probably doesn't need much but does
need something.
I'm not the one to merge it though so I don't know if the
maintainer wanted to just fix it up at the time. Just my
opinion...
For the changes themselves, fwiw,
Reviewed-by: Phil Auld <pauld@redhat.com>
Cheers,
Phil
> br
> Paul
>
--
next prev parent reply other threads:[~2024-05-13 16:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-11 8:26 [PATCH] sched/deadline: Fix grammar and typos in comments Paul Sherwood
2024-05-11 11:01 ` Bagas Sanjaya
2024-05-13 13:58 ` Phil Auld
2024-05-13 15:19 ` Paul Sherwood
2024-05-13 16:25 ` Phil Auld [this message]
2024-05-14 8:25 ` Daniel Bristot de Oliveira
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=20240513162519.GC9998@lorien.usersys.redhat.com \
--to=pauld@redhat.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=paul.sherwood@codethink.co.uk \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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