From: Peter Zijlstra <peterz@infradead.org>
To: Daniel Bristot de Oliveira <bristot@redhat.com>
Cc: Nicolas Pitre <nicolas.pitre@linaro.org>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 6/7] sched/rt: make it configurable
Date: Wed, 31 May 2017 12:40:21 +0200 [thread overview]
Message-ID: <20170531104021.ip5bycqyqdujuxxo@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <50013fad-8bcf-6da3-3756-1503c6b0f2d7@redhat.com>
On Wed, May 31, 2017 at 11:57:26AM +0200, Daniel Bristot de Oliveira wrote:
> On 05/30/2017 02:31 PM, Peter Zijlstra wrote:
> > All I see is ugly that makes maintenance worse
>
> s/maintenance/maintenance & development & understanding & .../
Just to be a total pain, '&' in the replacement string is the fully
matched regex, so what you're saying is:
"maintenance maintenance development maintenance understanding maintenance ..."
Now I do appreciate the unintended (it was, right?) emphasis on
maintenance though ;-)
next prev parent reply other threads:[~2017-05-31 10:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 21:02 [PATCH 0/7] scheduler tinification Nicolas Pitre
2017-05-29 21:02 ` [PATCH 1/7] cpuset/sched: cpuset makes sense for SMP only Nicolas Pitre
2017-05-29 21:02 ` [PATCH 2/7] sched: omit stop_sched_class when !SMP Nicolas Pitre
2017-06-08 9:30 ` [tip:sched/core] sched/core: Omit building " tip-bot for Nicolas Pitre
2017-05-29 21:02 ` [PATCH 3/7] sched/deadline: move dl related code out of sched/core.c Nicolas Pitre
2017-05-29 21:02 ` [PATCH 4/7] sched/deadline: make it configurable Nicolas Pitre
2017-05-29 21:03 ` [PATCH 5/7] sched/rt: move rt related code out of sched/core.c Nicolas Pitre
2017-05-29 21:03 ` [PATCH 6/7] sched/rt: make it configurable Nicolas Pitre
2017-05-30 8:41 ` Peter Zijlstra
2017-05-30 12:17 ` Nicolas Pitre
2017-05-30 12:31 ` Peter Zijlstra
2017-05-31 2:18 ` Nicolas Pitre
2017-05-31 9:57 ` Daniel Bristot de Oliveira
2017-05-31 10:40 ` Peter Zijlstra [this message]
2017-05-31 16:06 ` [6/7] " Rob Herring
2017-05-31 16:25 ` Nicolas Pitre
2017-05-29 21:03 ` [PATCH 7/7] rtmutex: compatibility with CONFIG_SCHED_RT=n Nicolas Pitre
2017-05-30 8:32 ` [PATCH 0/7] scheduler tinification Peter Zijlstra
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=20170531104021.ip5bycqyqdujuxxo@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bristot@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nicolas.pitre@linaro.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.