From: Chris Ball <cjb@laptop.org>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: "Eric Bénard" <eric@eukrea.com>,
r65037@freescale.com, linux-mmc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, shawn.gsc@gmail.com
Subject: Re: [PATCH] sdhci-esdhc-imx: fix timeout on i.MX's sdhci
Date: Tue, 19 Oct 2010 20:45:16 +0100 [thread overview]
Message-ID: <20101019194516.GA28424@void.printf.net> (raw)
In-Reply-To: <20101019193638.GB31336@pengutronix.de>
On Tue, Oct 19, 2010 at 09:36:38PM +0200, Wolfram Sang wrote:
> > I do have, but I can't do the tests until next week because of other priorities.
>
> I'd suggest to add a proper patch next week then (maybe together with correct
> usage of the MULTIBLOCK-quirk, too?). It's a new driver, so adding update
> patches late in the cycle should not cause problems? Of course, Chris makes the
> final decision about that.
Fine with me, tested patches are good. There's no need to rush to get
it in before -rc1.
Thanks,
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
WARNING: multiple messages have this Message-ID (diff)
From: cjb@laptop.org (Chris Ball)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] sdhci-esdhc-imx: fix timeout on i.MX's sdhci
Date: Tue, 19 Oct 2010 20:45:16 +0100 [thread overview]
Message-ID: <20101019194516.GA28424@void.printf.net> (raw)
In-Reply-To: <20101019193638.GB31336@pengutronix.de>
On Tue, Oct 19, 2010 at 09:36:38PM +0200, Wolfram Sang wrote:
> > I do have, but I can't do the tests until next week because of other priorities.
>
> I'd suggest to add a proper patch next week then (maybe together with correct
> usage of the MULTIBLOCK-quirk, too?). It's a new driver, so adding update
> patches late in the cycle should not cause problems? Of course, Chris makes the
> final decision about that.
Fine with me, tested patches are good. There's no need to rush to get
it in before -rc1.
Thanks,
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2010-10-19 19:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 12:49 [PATCH] sdhci-esdhc-imx: fix timeout on i.MX's sdhci Eric Bénard
2010-10-19 12:49 ` Eric Bénard
2010-10-19 15:07 ` Wolfram Sang
2010-10-19 15:07 ` Wolfram Sang
2010-10-19 15:17 ` Eric Bénard
2010-10-19 15:17 ` Eric Bénard
2010-10-19 19:36 ` Wolfram Sang
2010-10-19 19:36 ` Wolfram Sang
2010-10-19 19:45 ` Chris Ball [this message]
2010-10-19 19:45 ` 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=20101019194516.GA28424@void.printf.net \
--to=cjb@laptop.org \
--cc=eric@eukrea.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=r65037@freescale.com \
--cc=shawn.gsc@gmail.com \
--cc=w.sang@pengutronix.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 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.