tech-board-discuss.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Tech Board Discuss
	<Tech-board-discuss@lists.linux-foundation.org>,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: [Tech-board-discuss] Linux Foundation Technical Advisory Board Elections and Nomination process
Date: Sat, 17 Oct 2009 04:34:13 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0910170433370.2664@localhost.localdomain> (raw)
In-Reply-To: <fa686aa40910160922r78db1bb5md4f3f225d4a33c67@mail.gmail.com>



On Fri, 16 Oct 2009, Grant Likely wrote:

> On Mon, Oct 12, 2009 at 4:04 PM, James Bottomley
> <James.Bottomley@hansenpartnership.com> wrote:
> > On Thu, 2009-10-01 at 18:20 +0000, James Bottomley wrote:
> >> We currently have Five nominees (the incumbents):
> >>
> >> Greg KH <greg@kroah.com>
> >> Christoph Lameter <christoph@lameter.com>
> >> Jonathan Corbet <corbet@lwn.net>
> >> Arjan van de Ven <arjan@infradead.org>
> >> Christoph Hellwig <hch@lst.de>
> >
> > At this time we have no new nominees.
> 
> Personally, I'd really like to see someone with an embedded focus
> sitting on the board.  Thomas?  David?  Would either of you consider
> putting your name forward?

Add my name to the list.

    Thomas

  parent reply	other threads:[~2009-10-17  2:34 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-01 18:20 [Tech-board-discuss] Linux Foundation Technical Advisory Board Elections and Nomination process James Bottomley
2009-10-12 22:04 ` James Bottomley
2009-10-16 16:22   ` Grant Likely
2009-10-16 16:46     ` Roland Dreier
2009-10-16 17:06     ` David Woodhouse
2009-10-17  2:34     ` Thomas Gleixner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-10-15 14:00 James Bottomley
2010-10-15 17:18 ` Chris Wright
2010-10-20 20:46   ` Daniel Walker
2010-11-02 21:36   ` Chris Wright
2010-10-20 18:02 ` Randy Dunlap
2010-10-20 20:42   ` Daniel Walker
2010-10-20 18:42 ` John W. Linville
2011-09-02 14:31 James Bottomley
2012-07-06 13:49 James Bottomley
2012-08-24  9:48 James Bottomley
2013-10-14 18:01 James Bottomley
2013-10-23  7:40 James Bottomley
2014-07-15 21:48 James Bottomley
2014-08-18 20:13 ` James Bottomley
2014-08-19 14:43   ` Randy Dunlap
2014-08-19 19:03   ` James Bottomley
2014-08-19  3:03 ` Theodore Ts'o
2015-10-06 10:06 Grant Likely
2015-10-06 14:21 ` Josh Triplett
2015-10-13  8:06   ` Grant Likely
2015-10-08 21:02 ` Shuah Khan
2015-10-13  8:08   ` Grant Likely
2015-10-11  4:20 ` 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-20  0:54 ` Grant Likely
2015-10-20 12:39   ` Theodore Ts'o
2015-10-20 23:20     ` Grant Likely
2015-10-25  8:06   ` Grant Likely
2015-10-25  8:43     ` Grant Likely
2015-10-24 17:37 ` Olof Johansson
2016-10-14 20:28 [Tech-board-discuss] [Potential Spoof] [Tech-board] [draft v2] " Chris Mason
2016-10-14 20:34 ` [Tech-board-discuss] " Chris Mason

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=alpine.LFD.2.00.0910170433370.2664@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=Tech-board-discuss@lists.linux-foundation.org \
    --cc=dwmw2@infradead.org \
    --cc=grant.likely@secretlab.ca \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).