From: Peter Zijlstra <peterz@infradead.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Borislav Petkov <bp@alien8.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-tip-commits <linux-tip-commits@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>, x86 <x86@kernel.org>,
stable <stable@vger.kernel.org>
Subject: Re: [tip: core/urgent] rseq: Reject unknown flags on rseq unregister
Date: Tue, 7 Jan 2020 14:35:10 +0100 [thread overview]
Message-ID: <20200107133510.GB2844@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1732849021.873.1578338087928.JavaMail.zimbra@efficios.com>
On Mon, Jan 06, 2020 at 02:14:47PM -0500, Mathieu Desnoyers wrote:
> For the records, I had stable in CC in my original patch submission. The stable CC has
> been stripped when it was merged into the tip tree.
Argh, lemme go fix my scripts _again_..
I was recently made aware that we should not have spurious Cc: tags in
commit messages, but obviously the stable thing is an exception there.
next prev parent reply other threads:[~2020-01-07 13:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 16:17 [PATCH for 5.5 0/3] Restartable Sequences Fixes Mathieu Desnoyers
2019-12-11 16:17 ` [PATCH for 5.5 1/3] rseq: Fix: Reject unknown flags on rseq unregister Mathieu Desnoyers
2019-12-25 10:38 ` [tip: core/urgent] rseq: " tip-bot2 for Mathieu Desnoyers
2019-12-25 11:39 ` Borislav Petkov
2019-12-26 22:32 ` Mathieu Desnoyers
2020-01-06 19:14 ` Mathieu Desnoyers
2020-01-07 13:35 ` Peter Zijlstra [this message]
2019-12-11 16:17 ` [PATCH for 5.5 2/3] rseq: Fix: Unregister rseq for clone CLONE_VM Mathieu Desnoyers
2019-12-25 10:38 ` [tip: core/urgent] rseq: " tip-bot2 for Mathieu Desnoyers
2019-12-11 16:17 ` [PATCH for 5.5 3/3] rseq/selftests: Fix: Namespace gettid() for compatibility with glibc 2.30 Mathieu Desnoyers
2019-12-20 1:44 ` Shuah Khan
2019-12-20 14:48 ` [PATCH for 5.5 0/3] Restartable Sequences Fixes 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=20200107133510.GB2844@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/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®