From: Frederic Weisbecker <frederic@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Anna-Maria Behnsen <anna-maria@linutronix.de>,
Gabriele Monaco <gmonaco@redhat.com>,
Ingo Molnar <mingo@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Marcelo Tosatti <mtosatti@redhat.com>,
Marco Crivellari <marco.crivellari@suse.com>,
Michal Hocko <mhocko@kernel.org>,
"Paul E . McKenney" <paulmck@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Phil Auld <pauld@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Valentin Schneider <vschneid@redhat.com>,
Vlastimil Babka <vbabka@suse.cz>,
Waiman Long <longman@redhat.com>,
linux-doc@vger.kernel.org,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: Re: [PATCH v2] doc: Add CPU Isolation documentation
Date: Thu, 2 Apr 2026 11:15:01 +0200 [thread overview]
Message-ID: <ac4zlSfRpGp_xzMQ@pavilion.home> (raw)
In-Reply-To: <20260401130855.02c161d8@gandalf.local.home>
Le Wed, Apr 01, 2026 at 01:08:55PM -0400, Steven Rostedt a écrit :
> On Wed, 1 Apr 2026 18:27:03 +0200
> Frederic Weisbecker <frederic@kernel.org> wrote:
>
> > > > +"CPU Isolation" means leaving a CPU exclusive to a given workload
> > > > +without any undesired code interference from the kernel.
> > > > +
> > > > +Those interferences, commonly pointed out as "noise", can be triggered
> > >
> > > nit: "noise,"
> >
> > Thanks! I have applied all your suggestions, except this one for now because I don't
> > really understand the typo rule behind. Any hint?
>
> So this looks to be an American English thing (placing commas within the
> quote), but from what I read, British English places the comma outside the
> quote.
So does french english :-)
>
> Here's one case I much rather go the British English way. This also means
> it's only incorrect to Americans ;-)
Ok thank you both!
--
Frederic Weisbecker
SUSE Labs
next prev parent reply other threads:[~2026-04-02 9:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 14:00 [PATCH v2] doc: Add CPU Isolation documentation Frederic Weisbecker
2026-03-26 19:17 ` Waiman Long
2026-04-01 15:47 ` Frederic Weisbecker
2026-04-01 17:58 ` Waiman Long
2026-03-26 21:42 ` Randy Dunlap
2026-03-26 23:00 ` Steven Rostedt
2026-03-26 23:01 ` Steven Rostedt
2026-03-26 23:03 ` Randy Dunlap
2026-03-26 23:06 ` Steven Rostedt
2026-03-26 23:09 ` Randy Dunlap
2026-03-26 23:16 ` Steven Rostedt
2026-04-01 16:27 ` Frederic Weisbecker
2026-04-01 17:08 ` Steven Rostedt
2026-04-01 18:25 ` Randy Dunlap
2026-04-02 9:15 ` Frederic Weisbecker [this message]
2026-03-27 16:01 ` Valentin Schneider
2026-04-02 7:38 ` Sebastian Andrzej Siewior
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=ac4zlSfRpGp_xzMQ@pavilion.home \
--to=frederic@kernel.org \
--cc=anna-maria@linutronix.de \
--cc=bagasdotme@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=corbet@lwn.net \
--cc=gmonaco@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=marco.crivellari@suse.com \
--cc=mhocko@kernel.org \
--cc=mingo@kernel.org \
--cc=mtosatti@redhat.com \
--cc=pauld@redhat.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=vbabka@suse.cz \
--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