From: Chris Ball <cjb@laptop.org>
To: Arnd Hannemann <arnd@arndnet.de>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
linux-mmc@vger.kernel.org, Paul Mundt <lethal@linux-sh.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ian Molton <ian@mnementh.co.uk>, Magnus Damm <damm@opensource.se>,
linux-sh@vger.kernel.org
Subject: Re: outstanding TMIO MMC patches
Date: Wed, 5 Jan 2011 22:49:10 +0000 [thread overview]
Message-ID: <20110105224910.GC13209@void.printf.net> (raw)
In-Reply-To: <20110105222408.GM9198@void.printf.net>
On Wed, Jan 05, 2011 at 10:24:08PM +0000, Chris Ball wrote:
> > There are also these two:
> >
> > [1/2] tmio_mmc: handle missing HW interrupts
> > https://patchwork.kernel.org/patch/201962/
> > [2/2] tmio_mmc: fix CMD irq handling
> > https://patchwork.kernel.org/patch/201982/
>
> I haven't merged these because 1/2 breaks the build without TMIO_MMC_DMA=y.
These two are merged now, was my fault.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
WARNING: multiple messages have this Message-ID (diff)
From: Chris Ball <cjb@laptop.org>
To: Arnd Hannemann <arnd@arndnet.de>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
linux-mmc@vger.kernel.org, Paul Mundt <lethal@linux-sh.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ian Molton <ian@mnementh.co.uk>, Magnus Damm <damm@opensource.se>,
linux-sh@vger.kernel.org
Subject: Re: outstanding TMIO MMC patches
Date: Wed, 05 Jan 2011 22:49:10 +0000 [thread overview]
Message-ID: <20110105224910.GC13209@void.printf.net> (raw)
In-Reply-To: <20110105222408.GM9198@void.printf.net>
On Wed, Jan 05, 2011 at 10:24:08PM +0000, Chris Ball wrote:
> > There are also these two:
> >
> > [1/2] tmio_mmc: handle missing HW interrupts
> > https://patchwork.kernel.org/patch/201962/
> > [2/2] tmio_mmc: fix CMD irq handling
> > https://patchwork.kernel.org/patch/201982/
>
> I haven't merged these because 1/2 breaks the build without TMIO_MMC_DMA=y.
These two are merged now, was my fault.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2011-01-05 22:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-28 23:32 outstanding TMIO MMC patches Guennadi Liakhovetski
2010-12-28 23:32 ` Guennadi Liakhovetski
2010-12-29 13:35 ` Arnd Hannemann
2010-12-29 13:35 ` Arnd Hannemann
2011-01-05 22:24 ` Chris Ball
2011-01-05 22:24 ` Chris Ball
2011-01-05 22:49 ` Chris Ball [this message]
2011-01-05 22:49 ` Chris Ball
2011-01-05 2:10 ` Magnus Damm
2011-01-05 2:10 ` Magnus Damm
2011-01-05 4:53 ` Paul Mundt
2011-01-05 4:53 ` Paul Mundt
2011-01-05 16:57 ` Chris Ball
2011-01-05 16:57 ` Chris Ball
2011-01-05 17:30 ` Paul Mundt
2011-01-05 17:30 ` Paul Mundt
2011-01-05 18:57 ` Chris Ball
2011-01-05 18:57 ` Chris Ball
2011-01-05 21:16 ` Arnd Hannemann
2011-01-05 21:16 ` Arnd Hannemann
2011-01-05 23:08 ` Paul Mundt
2011-01-05 23:08 ` Paul Mundt
2011-01-05 23:31 ` Paul Mundt
2011-01-05 23:31 ` Paul Mundt
2011-01-06 1:57 ` Magnus Damm
2011-01-06 1:57 ` Magnus Damm
2011-01-05 22:57 ` Chris Ball
2011-01-05 22:57 ` Chris Ball
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=20110105224910.GC13209@void.printf.net \
--to=cjb@laptop.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndnet.de \
--cc=damm@opensource.se \
--cc=g.liakhovetski@gmx.de \
--cc=ian@mnementh.co.uk \
--cc=lethal@linux-sh.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sh@vger.kernel.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 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.