From: Valentin Schneider <vschneid@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Morten Rasmussen <morten.rasmussen@arm.com>,
Vincent Donnefort <vincent.donnefort@arm.com>,
Beata Michalska <beata.michalska@arm.com>,
Lukasz Luba <lukasz.luba@arm.com>,
Ionela Voinescu <ionela.voinescu@arm.com>,
Daniel Bristot de Oliveira <bristot@redhat.com>
Subject: [PATCH 0/2] MAINTAINERS, mailmap: tweaks for yours truly
Date: Wed, 6 Apr 2022 15:13:13 +0100 [thread overview]
Message-ID: <20220406141315.732473-1-vschneid@redhat.com> (raw)
Hi folks,
I've had a nice long shoreleave inbetween switching ships, but it's time I got
back to work!
I faintly recall some objections to editing the mailmap if one isn't named in
either a file header or in MAINTAINERS itself. The only files I can remember
creating are include/linux/sched/sd_flags.h and
Documentation/scheduler/sched-capacity.rst, which now that I look at it aren't
covered by any MAINTAINERS entry...
Anywho, I do want to keep a presence on the list, and this gives me an excuse to
mess with the mailmap :)
Valentin Schneider (2):
MAINTAINERS: Add myself as scheduler topology reviewer
mailmap: Update my email address to @redhat.com
.mailmap | 1 +
MAINTAINERS | 1 +
2 files changed, 2 insertions(+)
--
2.27.0
next reply other threads:[~2022-04-06 16:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 14:13 Valentin Schneider [this message]
2022-04-06 14:13 ` [PATCH 1/2] MAINTAINERS: Add myself as scheduler topology reviewer Valentin Schneider
2022-04-22 10:27 ` [tip: sched/core] " tip-bot2 for Valentin Schneider
2022-04-06 14:13 ` [PATCH 2/2] mailmap: Update my email address to @redhat.com Valentin Schneider
2022-04-22 10:27 ` [tip: sched/core] " tip-bot2 for Valentin Schneider
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=20220406141315.732473-1-vschneid@redhat.com \
--to=vschneid@redhat.com \
--cc=beata.michalska@arm.com \
--cc=bristot@redhat.com \
--cc=dietmar.eggemann@arm.com \
--cc=ionela.voinescu@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=mingo@redhat.com \
--cc=morten.rasmussen@arm.com \
--cc=peterz@infradead.org \
--cc=vincent.donnefort@arm.com \
--cc=vincent.guittot@linaro.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®