From: Ian Molton <ian@mnementh.co.uk>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Chris Ball <cjb@laptop.org>,
linux-mmc@vger.kernel.org, linux-sh@vger.kernel.org,
Magnus Damm <damm@opensource.se>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Simon Horman <horms@verge.net.au>
Subject: Re: [PATCH 0/2] mmc: tmio: two bug-fixes
Date: Sat, 27 Aug 2011 22:40:31 +0100 [thread overview]
Message-ID: <1314481234.2053.0.camel@drake> (raw)
In-Reply-To: <Pine.LNX.4.64.1107150957570.22613@axis700.grange>
On Fri, 2011-07-15 at 10:46 +0200, Guennadi Liakhovetski wrote:
> Thanks for the offer, I appreciate it! I am not the only active tmio
> mmc contributor, but yes, I could take that role upon me, if noone
> objects.
> Would be good to hear, what Ian thinks? Is he maybe still planning to
> actively working on the driver? Would he like to stay listed as a
> co-maintainer? If I am to maintain the driver alone, it would be good
> to have access to some non-sh-mobile hardware, using it too, at least
> for regression testing. Any idea where to get anything like that?
Seem to remember dealing with this already - but I'm fine with it. I'd
like to keep on testing the TMIO chipsets in e-series (need to build
that again sometime soon).
-Ian
prev parent reply other threads:[~2011-08-27 21:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-14 16:39 [PATCH 0/2] mmc: tmio: two bug-fixes Guennadi Liakhovetski
2011-07-14 16:39 ` [PATCH 1/2] mmc: tmio: fix a recently introduced bug in DMA code Guennadi Liakhovetski
2011-07-14 16:39 ` [PATCH 2/2] mmc: tmio: fix a deadlock Guennadi Liakhovetski
2011-07-14 19:27 ` [PATCH 0/2] mmc: tmio: two bug-fixes Chris Ball
2011-07-15 8:46 ` Guennadi Liakhovetski
2011-08-27 21:40 ` Ian Molton [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=1314481234.2053.0.camel@drake \
--to=ian@mnementh.co.uk \
--cc=cjb@laptop.org \
--cc=damm@opensource.se \
--cc=g.liakhovetski@gmx.de \
--cc=horms@verge.net.au \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=rjw@sisk.pl \
/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