From: Greg KH <greg@kroah.com>
To: Mark Lord <lkml@rtr.ca>, drzeus-sdhci@drzeus.cx
Cc: "David J. Wallace" <katana@onetel.com>,
sdhci-devel@list.drzeus.cx, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@osdl.org>
Subject: Re: [Sdhci-devel] Submission to the kernel?
Date: Fri, 17 Mar 2006 08:57:23 -0800 [thread overview]
Message-ID: <20060317165723.GA32281@kroah.com> (raw)
In-Reply-To: <441AD537.5080403@rtr.ca>
On Fri, Mar 17, 2006 at 10:26:47AM -0500, Mark Lord wrote:
> David J. Wallace wrote:
> >On Thursday 16 March 2006 23:53, David Liontooth wrote:
> >
> >>I would urge people to test Andrew's latest -mm kernel and report to
> >>lkml (cc him) on whether the sdhci driver works or causes any kind of
> >>problem.
>
> SDHCI seems to be working well on my Dell Inspiron 9300.
>
> But I have concerns over maintenance of the code -- there does not
> seem to be a functioning (for me) email address for a maintainer.
Did you try the one listed in the MAINTAINERS portion of the patch:
+SECURE DIGITAL HOST CONTROLLER INTERFACE DRIVER
+P: Pierre Ossman
+M: drzeus-sdhci@drzeus.cx
+L: sdhci-devel@list.drzeus.cx
+W: http://mmc.drzeus.cx/wiki/Linux/Drivers/sdhci
+S: Maintained
thanks,
greg k-h
prev parent reply other threads:[~2006-03-17 16:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4419FA7A.4050104@cogweb.net>
2006-03-17 10:42 ` [Sdhci-devel] Submission to the kernel? David J. Wallace
2006-03-17 15:26 ` Mark Lord
2006-03-17 15:46 ` Pierre Ossman
2006-03-17 17:01 ` Greg KH
2006-03-17 17:15 ` Pierre Ossman
2006-03-25 2:39 ` Greg KH
2006-03-25 5:48 ` Pierre Ossman
2006-03-25 6:39 ` Greg KH
2006-03-25 14:08 ` Pierre Ossman
2006-03-28 2:23 ` Alistair John Strachan
2006-03-29 8:24 ` Pierre Ossman
2006-03-29 16:11 ` Alistair John Strachan
2006-03-29 16:18 ` Pierre Ossman
2006-03-17 19:37 ` Mark Lord
2006-03-17 19:48 ` Pierre Ossman
2006-03-17 16:57 ` Greg KH [this message]
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=20060317165723.GA32281@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=drzeus-sdhci@drzeus.cx \
--cc=katana@onetel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=sdhci-devel@list.drzeus.cx \
/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.