All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: torvalds@linux-foundation.org
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Looking for new x86 platform driver maintainer
Date: Wed, 20 Aug 2014 16:22:26 +0100	[thread overview]
Message-ID: <20140820152226.GB3616@srcf.ucam.org> (raw)
In-Reply-To: <20140820152034.GA3616@srcf.ucam.org>

And I think this proves that I don't have time to do a good job of this 
at the moment. It would be helpful if someone else were willing to take 
over responsiblity for this tree - there's not a great deal of churn, 
but it does require some familiarity with firmware and a sense of taste 
(there's about two billion bad ways to implement most of these drivers, 
along with a good way). Anybody willing to take it on?

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2014-08-20 15:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-20 15:20 [GIT PULL] x86 platform driver update Matthew Garrett
2014-08-20 15:22 ` Matthew Garrett [this message]
2014-08-21 13:31   ` Looking for new x86 platform driver maintainer Darren Hart
2014-08-21 21:34     ` Matthew Garrett

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=20140820152226.GB3616@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=torvalds@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.