From: Kevin Hilman <khilman@kernel.org>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] self nomination: Kevin Hilman
Date: Tue, 04 Aug 2015 10:01:31 -0700 [thread overview]
Message-ID: <7hegjjyolw.fsf@deeprootsystems.com> (raw)
Sorry for the late nomination, been on vacation and just catching up on
mail....
I seem to have fallen off the auto-generated list this year, probably
because I've been helping Arnd/Olof with arm-soc and doing mostly
reviews, merges and testing, so not generating many patches of my own.
In any case, I'd like to self nominate for the following areas:
Testing: as the main kernel developer working on kernelci.org (which
has been mentioned several times on this list now) I'd like to
participate in the various discussions around kernel testing
infrastructure.
stable process: I've been using kernelci.org to test/find/report bugs
against the stable queues and the stable trees, and want be part of
the discussions on how we can do this better.
PM tunables: as an active reviewer of PM code (mainly for embedded
SoCs) and co-maintainer of the generic PM domain code, I'd like to
participate in the discussion around PM tuning/tunables.
Kevin
P.S. should the auto-generated list automatically include all those
who Linus pulls directly from?
reply other threads:[~2015-08-04 17:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=7hegjjyolw.fsf@deeprootsystems.com \
--to=khilman@kernel.org \
--cc=ksummit-discuss@lists.linuxfoundation.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