From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Grant Likely <glikely@secretlab.ca>,
Tech Board Discuss
<Tech-board-discuss@lists.linux-foundation.org>
Cc: "lwn@lwn.net" <lwn@lwn.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ksummit-discuss@lists.linuxfoundation.org,
tech-board <tech-board@lists.linux-foundation.org>
Subject: Re: [Ksummit-discuss] Linux Foundation Technical Advisory Board Elections and Nomination process
Date: Thu, 15 Oct 2015 23:56:32 +0200 [thread overview]
Message-ID: <4221154.qGPsqztETk@vostro.rjw.lan> (raw)
In-Reply-To: <CACxGe6tWRfHFtkL1TKnOHjV_+e_WFe1w3ZaKrxH5zPBF5GpqqA@mail.gmail.com>
On Tuesday, October 06, 2015 11:06:47 AM Grant Likely wrote:
> [Resending because I messed up the first one]
>
> The elections for five of the ten members of the Linux Foundation
> Technical Advisory Board (TAB) are held every year[1]. This year the
> election will be at the 2015 Kernel Summit in Seoul, South Korea
> (probably on the Monday, 26 October) and will be open to all attendees
> of both Kernel Summit and Korea Linux Forum.
>
> Anyone is eligible to stand for election, simply send your nomination to:
>
> Tech-board-discuss@lists.linux-foundation.org
>
> We currently have 3 nominees for five places:
> Thomas Gleixner
> Greg Kroah-Hartman
> Stephen Hemminger
I'd like to nominate myself to stand for a place on the TAB.
I will be present at the Kernel Summit in person.
Thanks,
Rafael
next prev parent reply other threads:[~2015-10-15 21:27 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 10:06 Grant Likely
2015-10-06 14:21 ` [Ksummit-discuss] [Tech-board-discuss] " Josh Triplett
2015-10-13 8:06 ` Grant Likely
2015-10-11 4:20 ` [Ksummit-discuss] " Ric Wheeler
2015-10-13 8:12 ` Grant Likely
2015-10-13 13:09 ` Sage Weil
2015-10-14 17:48 ` Grant Likely
2015-10-13 5:19 ` Kees Cook
2015-10-13 8:10 ` Grant Likely
2015-10-13 16:11 ` Steven Rostedt
2015-10-15 21:56 ` Rafael J. Wysocki [this message]
2015-10-20 0:54 ` Grant Likely
2015-10-20 12:39 ` [Ksummit-discuss] [Tech-board-discuss] " Theodore Ts'o
2015-10-20 23:20 ` Grant Likely
2015-10-25 8:06 ` [Ksummit-discuss] " Grant Likely
2015-10-25 8:43 ` Grant Likely
2015-10-22 21:03 ` Darren Hart
2015-10-23 2:04 ` Neil Brown
2015-10-23 3:00 ` Kristen Accardi
2015-10-23 4:51 ` [Ksummit-discuss] [Tech-board-discuss] " Josh Triplett
2015-10-23 5:54 ` [Ksummit-discuss] " Neil Brown
2015-10-24 10:28 ` Grant Likely
2015-10-24 15:39 ` Rafael J. Wysocki
2015-10-24 15:58 ` [Ksummit-discuss] [Tech-board] " John W. Linville
2015-10-25 3:45 ` Jonathan Corbet
2015-10-25 7:35 ` Grant Likely
2015-10-24 16:51 ` [Ksummit-discuss] " Dan Williams
2015-10-24 17:37 ` Olof Johansson
2015-10-26 1:06 ` Darren Hart
-- strict thread matches above, loose matches on Subject: below --
2016-10-14 20:33 Chris Mason
2016-11-01 23:18 ` H. Peter Anvin
2014-07-15 21:48 James Bottomley
2014-08-18 20:13 ` James Bottomley
2014-08-19 14:43 ` Randy Dunlap
2014-08-19 13:45 ` Grant Likely
2015-09-29 21:55 ` Kees Cook
2015-09-29 22:00 ` Grant Likely
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=4221154.qGPsqztETk@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=Tech-board-discuss@lists.linux-foundation.org \
--cc=glikely@secretlab.ca \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=tech-board@lists.linux-foundation.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