From: "Madhusudhan" <madhu.cr@ti.com>
To: akpm@linux-foundation.org, torvalds@linux-foundation.org
Cc: HaraldWelte@viatech.com, JosephChan@via.com.tw,
ben-linux@fluff.org, drzeus@drzeus.cx, ian@mnementh.co.uk,
jarkko.lavinen@nokia.com, linux-mmc@vger.kernel.org,
manuel.lauss@gmail.com, nico@cam.org, ppisa@pikron.com,
saschasommer@freenet.de
Subject: RE: [patch 4/9] mmc: add the new linux-mmc mailing list to MAINTAINERS
Date: Tue, 18 Aug 2009 17:08:40 -0500 [thread overview]
Message-ID: <003c01ca2050$71d72c80$544ff780@am.dhcp.ti.com> (raw)
In-Reply-To: <200908182111.n7ILBCSc017248@imap1.linux-foundation.org>
> -----Original Message-----
> From: linux-mmc-owner@vger.kernel.org [mailto:linux-mmc-
> owner@vger.kernel.org] On Behalf Of akpm@linux-foundation.org
> Sent: Tuesday, August 18, 2009 4:11 PM
> To: torvalds@linux-foundation.org
> Cc: akpm@linux-foundation.org; HaraldWelte@viatech.com;
> JosephChan@via.com.tw; ben-linux@fluff.org; drzeus@drzeus.cx;
> ian@mnementh.co.uk; jarkko.lavinen@nokia.com; linux-mmc@vger.kernel.org;
> manuel.lauss@gmail.com; nico@cam.org; ppisa@pikron.com;
> saschasommer@freenet.de
> Subject: [patch 4/9] mmc: add the new linux-mmc mailing list to
> MAINTAINERS
>
> From: Andrew Morton <akpm@linux-foundation.org>
>
> There are a number of individual MMC drivers listed in MAINTAINERS. I
> didn't modify those records. Perhaps I should have.
>
Does this mean that the individual MMC drivers list needs to be changed to
linux-mmc@vger.kernel.org?
For e.g. the OMAP MMC support currently listed as
L: linux-omap@vger.kernel.org
Should now be changed as below?
L: linux-mmc@vger.kernel.org
Regards,
Madhu
> Cc: <linux-mmc@vger.kernel.org>
> Cc: Manuel Lauss <manuel.lauss@gmail.com>
> Cc: Nicolas Pitre <nico@cam.org>
> Cc: Pierre Ossman <drzeus@drzeus.cx>
> Cc: Pavel Pisa <ppisa@pikron.com>
> Cc: Jarkko Lavinen <jarkko.lavinen@nokia.com>
> Cc: Ben Dooks <ben-linux@fluff.org>
> Cc: Sascha Sommer <saschasommer@freenet.de>
> Cc: Ian Molton <ian@mnementh.co.uk>
> Cc: Joseph Chan <JosephChan@via.com.tw>
> Cc: Harald Welte <HaraldWelte@viatech.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff -puN MAINTAINERS~mmc-add-the-new-linux-mmc-mailing-list-to-
> maintainers MAINTAINERS
> --- a/MAINTAINERS~mmc-add-the-new-linux-mmc-mailing-list-to-maintainers
> +++ a/MAINTAINERS
> @@ -3429,6 +3429,7 @@ F: drivers/mfd/
>
> MULTIMEDIA CARD (MMC), SECURE DIGITAL (SD) AND SDIO SUBSYSTEM
> S: Orphan
> +L: linux-mmc@vger.kernel.org
> F: drivers/mmc/
> F: include/linux/mmc/
>
> _
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-08-18 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 21:11 [patch 4/9] mmc: add the new linux-mmc mailing list to MAINTAINERS akpm
2009-08-18 22:08 ` Madhusudhan [this message]
2009-08-18 22:17 ` Andrew Morton
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='003c01ca2050$71d72c80$544ff780@am.dhcp.ti.com' \
--to=madhu.cr@ti.com \
--cc=HaraldWelte@viatech.com \
--cc=JosephChan@via.com.tw \
--cc=akpm@linux-foundation.org \
--cc=ben-linux@fluff.org \
--cc=drzeus@drzeus.cx \
--cc=ian@mnementh.co.uk \
--cc=jarkko.lavinen@nokia.com \
--cc=linux-mmc@vger.kernel.org \
--cc=manuel.lauss@gmail.com \
--cc=nico@cam.org \
--cc=ppisa@pikron.com \
--cc=saschasommer@freenet.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox