From: Peter Zijlstra <peterz@infradead.org>
To: Dexuan Cui <decui@microsoft.com>
Cc: Ingo Molnar <mingo@kernel.org>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
jeyu@kernel.org, Josh Poimboeuf <jpoimboe@redhat.com>,
ardb@kernel.org, Steven Rostedt <rostedt@goodmis.org>,
Jason Baron <jbaron@akamai.com>
Subject: Re: [RFC][PATCH] jump_label/static_call: Add MAINTAINERS
Date: Wed, 16 Dec 2020 14:42:49 +0100 [thread overview]
Message-ID: <20201216134249.GU3092@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20201216133014.GT3092@hirez.programming.kicks-ass.net>
On Wed, Dec 16, 2020 at 02:30:14PM +0100, Peter Zijlstra wrote:
>
> FWIW, I recently noticed we're not being Cc'ed on patches for this
> stuff, so how about we do something like the below?
>
> Anybody holler if they don't agree with the letter assigned, or if they
> feel they've been left out entirely and want in on the 'fun' :-)
>
> ---
> Subject: jump_label/static_call: Add MAINTAINERS
> From: Peter Zijlstra <peterz@infradead.org>
>
> These files don't appear to have a MAINTAINERS entry and as such
> patches miss being seen by people who know this code.
>
> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> ---
> MAINTAINERS | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -16766,6 +16766,18 @@ M: Ion Badulescu <ionut@badula.org>
> S: Odd Fixes
> F: drivers/net/ethernet/adaptec/starfire*
>
> +STATIC BRANCH/CALL
> +M: Peter Zijlstra <peterz@infradead.org>
> +M: Josh Poimboeuf <jpoimboe@redhat.com>
> +M: Jason Baron <jbaron@akamai.com>
> +R: Steven Rostedt <rostedt@goodmis.org>
> +R: Ard Biesheuvel <ardb@kernel.org>
> +S: Supported
F: arch/*/include/asm/jump_label*.h
F: arch/*/include/asm/static_call*.h
F: arch/*/kernel/jump_label.c
F: arch/*/kernel/static_call.c
These too?
> +F: include/linux/jump_label*.h
> +F: include/linux/static_call*.h
> +F: kernel/jump_label.c
> +F: kernel/static_call.c
> +
> STEC S1220 SKD DRIVER
> M: Damien Le Moal <Damien.LeMoal@wdc.com>
> L: linux-block@vger.kernel.org
next prev parent reply other threads:[~2020-12-16 13:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 3:54 static_branch_enable() does not work from a __init function? Dexuan Cui
2020-12-16 9:26 ` Peter Zijlstra
2020-12-16 10:59 ` Peter Zijlstra
2020-12-16 13:30 ` [RFC][PATCH] jump_label/static_call: Add MAINTAINERS Peter Zijlstra
2020-12-16 13:42 ` Peter Zijlstra [this message]
2020-12-16 14:23 ` Steven Rostedt
2020-12-16 16:19 ` Josh Poimboeuf
2020-12-16 16:19 ` Ard Biesheuvel
2020-12-16 21:16 ` Jason Baron
2020-12-16 13:54 ` [PATCH] jump_label: Fix usage in module __init Peter Zijlstra
2020-12-16 16:36 ` Josh Poimboeuf
2020-12-16 20:45 ` static_branch_enable() does not work from a __init function? Dexuan Cui
2020-12-16 11:55 ` Jessica Yu
2020-12-16 12:47 ` Peter Zijlstra
2020-12-16 13:10 ` Jessica Yu
2020-12-16 13:23 ` Peter Zijlstra
2020-12-16 13:27 ` Jessica Yu
2020-12-16 12:38 ` Jessica Yu
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=20201216134249.GU3092@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=ardb@kernel.org \
--cc=bristot@redhat.com \
--cc=decui@microsoft.com \
--cc=jbaron@akamai.com \
--cc=jeyu@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.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