ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Davidlohr Bueso <davidlohr@hp.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Josh Boyer <jwboyer@fedoraproject.org>,
	ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] Nominations for per topic people
Date: Thu, 15 May 2014 10:46:44 -0700	[thread overview]
Message-ID: <1400176004.12306.3.camel@buesod1.americas.hpqcorp.net> (raw)
In-Reply-To: <20140515173703.GA24446@thunk.org>

On Thu, 2014-05-15 at 13:37 -0400, Theodore Ts'o wrote:
> On Fri, May 09, 2014 at 12:49:07PM -0400, Josh Boyer wrote:
> > Below are people that have been nominated in the submitted topic
> > threads that aren't already on the list.
> > 
> > Josh Poimboeuf (live kernel patching)
> > Seth Jennings (live kernel patching)
> > Vojtech Pavlik (live kernel patching, trusted kernel patchset)
> > Pavel Emelyanov (live kernel patching)
> > Masami Hiramatsu (live kernel patching)
> > Jiri Slaby (live kernel patching, stable)
> > Michael Matz (live kernel patching)
> > Josh Boyer (trusted kernel patchset, stable)
> > Joey Li (trusted kernel patchset)
> > Gary Lin (trusted kernel patchset)
> > James Morris (trusted kernel patchset)
> > Matthew Garret (trusted kernel patchset)
> > Darren Hart (driver model and ACPI/DT)
> > Grant Likely (driver model and ACPI/DT, also on the ksummit committee so...)
> > Al Stone (driver model and ACPI/DT)
> > Amit Kucheria (energy conservation bias)
> > Morten Rasmussen (energy conservation bias)
> > Waiman Long (asm-generic low levels)
> > Jörg Rödel (device error handling)
> > Michael Kerrisk (API/ABI review)
> > Shuah Khan (API/ABI review)
> > Dave Jones (kernel tinification, energy conservation bias, and trinity work)
> > Andy Lutomirski (virtually every topic thread thus far)
> > 
> > Hope that helps.
> 
> It would have helped more if I had gotten e-mail addresses as well.  :-)
> 
> Here are my best guesses, although I wasn't able to find one for Joey
> Li, despite my best efforts.....  if folks could confirm whether I got
> these right and didn't grab an old one from the git commit logs, I'd
> appreciate it.

Not sure if this counts or if the topics are going to be included, but
I'd like to autonominate myself fwiw:

Davidlohr Bueso <davidlohr@hp.com> (stable issues, application performance)

  parent reply	other threads:[~2014-05-15 17:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-09 16:49 Josh Boyer
2014-05-09 16:55 ` josh
2014-05-09 17:00   ` Josh Boyer
2014-05-09 17:17     ` josh
2014-05-09 17:20 ` Hans Verkuil
2014-05-12 17:23 ` Preeti U Murthy
2014-05-15 17:37 ` Theodore Ts'o
2014-05-15 17:39   ` Jiri Kosina
2014-05-15 17:49     ` Theodore Ts'o
2014-05-15 18:05       ` Jiri Kosina
2014-05-15 17:46   ` Davidlohr Bueso [this message]
2014-05-15 17:58   ` Josh Boyer
2014-05-15 18:49   ` Shuah Khan
2014-05-16  0:13 ` josh
2014-05-16  9:19 ` Linus Walleij
2014-05-17 15:12   ` Levente Kurusa
2014-05-19  7:46     ` Teodora Băluţă
2014-06-05  6:23   ` Olof Johansson
2014-06-05 12:14     ` Rafael J. Wysocki

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=1400176004.12306.3.camel@buesod1.americas.hpqcorp.net \
    --to=davidlohr@hp.com \
    --cc=jwboyer@fedoraproject.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=tytso@mit.edu \
    /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