All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Pierre Ossman <pierre@ossman.eu>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-embedded@vger.kernel.org,
	nico@cam.org, nicolas.ferre@rfo.atmel.com, hskinnemoen@atmel.com,
	tony@atomide.com, david-b@pacbell.net, manuel.lauss@gmail.com,
	mirq-linux@rere.qmqm.pl, ppisa@pikron.com,
	jarkko.lavinen@nokia.com, ben@fluff.org, saschasommer@freenet.de,
	avorontsov@ru.mvista.com, oakad@yahoo.com, ian@mnementh.co.uk,
	HaraldWelte@viatech.com, JosephChan@via.com.tw,
	adrian.hunter@nokia.com
Subject: Re: New MMC maintainer needed
Date: Tue, 18 Aug 2009 11:33:45 +0200	[thread overview]
Message-ID: <4A8A7579.9080604@atmel.com> (raw)
In-Reply-To: <20090731122623.254fd0f1@mjolnir.ossman.eu>

Pierre Ossman :
> This things are currently lingering in my inbox:

[..]

> [PATCH 1/2] atmel-mci: Unified Atmel MCI drivers (AVR32 & AT91)
> http://marc.info/?l=linux-arm-kernel&m=124577578729455
> 
> This is nice work and it's really up to Nicolas when he wants it merged.

Ok guys, it should be fine if we can plan a merge for those bits: I have
additional patches that are waiting on top of this one...

Thanks a lot. Bye,
-- 
Nicolas Ferre

  parent reply	other threads:[~2009-08-18  9:33 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-14 13:36 New MMC maintainer needed Pierre Ossman
2009-07-14 13:36 ` Pierre Ossman
2009-07-14 21:04 ` Ian Molton
2009-07-22 22:17 ` Andrew Morton
2009-07-23  0:08   ` Ian Molton
2009-07-23  5:54     ` Matt Fleming
2009-07-23  6:22       ` Andrew Morton
2009-07-23  6:42         ` Paul Mundt
2009-07-23  6:50         ` Ohad Ben-Cohen
2009-07-23 13:52           ` Matt Fleming
2009-07-24 22:29             ` Andrew Morton
2009-07-27  6:06               ` Philip Langdale
2009-07-27 12:09                 ` David Vrabel
2009-07-27 21:40                   ` Matt Fleming
2009-07-28  0:52                     ` Philip Langdale
2009-07-28 12:51                     ` David Vrabel
2009-07-23  7:01         ` Adrian Hunter
2009-07-23  7:01           ` Adrian Hunter
2009-07-23  7:25         ` Stephen Rothwell
2009-07-23  7:32           ` Andrew Morton
2009-07-23  7:38             ` Stephen Rothwell
2009-07-23 16:29               ` Andi Kleen
2009-07-23 10:57       ` Roberto A. Foglietta
2009-07-28 20:22     ` Pierre Ossman
2009-07-30  2:36       ` Segher Boessenkool
2009-07-28 20:20   ` Pierre Ossman
2009-07-28 21:14     ` Ian Molton
2009-07-28 22:41       ` Andrew Morton
2009-07-29  6:35         ` Sam Ravnborg
2009-07-29 10:35         ` Ian Molton
2009-07-28 20:23   ` Pierre Ossman
2009-07-31 10:26     ` Pierre Ossman
2009-07-31 10:54       ` Matt Fleming
2009-08-03 10:34         ` Pierre Ossman
2009-08-03 11:10           ` Matt Fleming
2009-08-03 11:13           ` Adrian Hunter
2009-08-03 11:13             ` Adrian Hunter
2009-08-03 21:41             ` Andrew Morton
2009-08-11 14:02             ` Matt Fleming
2009-08-11 14:02               ` Matt Fleming
2009-08-12 22:27               ` Andrew Morton
2009-08-13  8:21                 ` Matt Fleming
2009-08-13  8:21                   ` Matt Fleming
2009-08-13  7:01               ` Adrian Hunter
2009-08-13  7:01                 ` Adrian Hunter
2009-08-13 17:03                 ` Nicolas Pitre
2009-08-13 17:03                   ` Nicolas Pitre
2009-08-04  1:51       ` David Brownell
2009-08-05  1:42         ` David VomLehn
2009-08-06  8:54         ` Pierre Ossman
2009-08-18  9:33       ` Nicolas Ferre [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-07-15  4:59 Alex Dubov
2009-07-15  4:59 ` Alex Dubov
2009-07-31 13:36 ` Maxim Levitsky
2009-08-01  6:53   ` Alex Dubov
2009-08-01  7:21     ` Maxim Levitsky
2009-08-12 22:52 ellis

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=4A8A7579.9080604@atmel.com \
    --to=nicolas.ferre@atmel.com \
    --cc=HaraldWelte@viatech.com \
    --cc=JosephChan@via.com.tw \
    --cc=adrian.hunter@nokia.com \
    --cc=akpm@linux-foundation.org \
    --cc=avorontsov@ru.mvista.com \
    --cc=ben@fluff.org \
    --cc=david-b@pacbell.net \
    --cc=hskinnemoen@atmel.com \
    --cc=ian@mnementh.co.uk \
    --cc=jarkko.lavinen@nokia.com \
    --cc=linux-embedded@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manuel.lauss@gmail.com \
    --cc=mirq-linux@rere.qmqm.pl \
    --cc=nico@cam.org \
    --cc=nicolas.ferre@rfo.atmel.com \
    --cc=oakad@yahoo.com \
    --cc=pierre@ossman.eu \
    --cc=ppisa@pikron.com \
    --cc=saschasommer@freenet.de \
    --cc=tony@atomide.com \
    /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.