From: Chris Ball <cjb@laptop.org>
To: Michael Buesch <mb@bu3sch.de>
Cc: Albert Herranz <albert_herranz@yahoo.es>,
bcm43xx-dev@lists.berlios.de, linux-mmc@vger.kernel.org,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH RFC 1/3] sdio: recognize io card without powercycle
Date: Mon, 07 Sep 2009 14:59:45 -0400 [thread overview]
Message-ID: <m3hbvey40u.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <200909072055.24589.mb@bu3sch.de> (Michael Buesch's message of "Mon, 7 Sep 2009 20:55:22 +0200")
Hi Michael,
> Please submit this to the SDIO maintainer.
MULTIMEDIA CARD (MMC), SECURE DIGITAL (SD) AND SDIO SUBSYSTEM
S: Orphan
L: linux-mmc@vger.kernel.org
F: drivers/mmc/
F: include/linux/mmc/
So, these patches are in the right place.
- Chris.
--
Chris Ball <cjb@laptop.org>
One Laptop Per Child
next prev parent reply other threads:[~2009-09-07 19:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-07 18:46 [PATCH RFC 1/3] sdio: recognize io card without powercycle Albert Herranz
2009-09-07 18:55 ` Michael Buesch
2009-09-07 18:59 ` Chris Ball [this message]
2009-09-07 19:05 ` Michael Buesch
2009-09-07 19:10 ` Ehud Gavron
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=m3hbvey40u.fsf@pullcord.laptop.org \
--to=cjb@laptop.org \
--cc=albert_herranz@yahoo.es \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
/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 NNTP newsgroup(s).