From: Chris Ball <cjb@laptop.org>
To: Per Forlin <per.forlin@linaro.org>
Cc: linaro-dev@lists.linaro.org,
linux-arm-kernel@lists.infradead.org, linux-mmc@vger.kernel.org,
Venkatraman S <svenkatr@ti.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>
Subject: Re: [PATCH 0/2] mmc: clarifications on host.post_req()
Date: Wed, 21 Sep 2011 14:30:31 -0400 [thread overview]
Message-ID: <m2k4913fzs.fsf@bob.laptop.org> (raw)
In-Reply-To: <1314624959-4634-1-git-send-email-per.forlin@linaro.org> (Per Forlin's message of "Mon, 29 Aug 2011 15:35:57 +0200")
Hi Per,
On Mon, Aug 29 2011, Per Forlin wrote:
> Fixes for 3.1.
> This patchset doesn't fix any bugs in 3.1 but it improves the documentation
> in order to prevent new bugs.
I've merged this into mmc-next now, but I'm planning on sending it for
3.2 instead of 3.1 at this point; hope that's okay.
Thanks,
- Chris.
--
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 0/2] mmc: clarifications on host.post_req()
Date: Wed, 21 Sep 2011 14:30:31 -0400 [thread overview]
Message-ID: <m2k4913fzs.fsf@bob.laptop.org> (raw)
In-Reply-To: <1314624959-4634-1-git-send-email-per.forlin@linaro.org> (Per Forlin's message of "Mon, 29 Aug 2011 15:35:57 +0200")
Hi Per,
On Mon, Aug 29 2011, Per Forlin wrote:
> Fixes for 3.1.
> This patchset doesn't fix any bugs in 3.1 but it improves the documentation
> in order to prevent new bugs.
I've merged this into mmc-next now, but I'm planning on sending it for
3.2 instead of 3.1 at this point; hope that's okay.
Thanks,
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2011-09-21 18:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-29 13:35 [PATCH 0/2] mmc: clarifications on host.post_req() Per Forlin
2011-08-29 13:35 ` Per Forlin
2011-08-29 13:35 ` [PATCH 1/2] mmc: core: clarify how to use post_req in case of errors Per Forlin
2011-08-29 13:35 ` Per Forlin
2011-09-12 14:05 ` Linus Walleij
2011-09-12 14:05 ` Linus Walleij
2011-08-29 13:35 ` [PATCH 2/2] mmc: mmci: simplify err check in mmci_post_request Per Forlin
2011-08-29 13:35 ` Per Forlin
2011-09-12 14:06 ` Linus Walleij
2011-09-12 14:06 ` Linus Walleij
2011-09-21 18:30 ` Chris Ball [this message]
2011-09-21 18:30 ` [PATCH 0/2] mmc: clarifications on host.post_req() Chris Ball
2011-09-21 18:43 ` Per Fridén Förlin
2011-09-21 18:43 ` Per Fridén Förlin
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=m2k4913fzs.fsf@bob.laptop.org \
--to=cjb@laptop.org \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=per.forlin@linaro.org \
--cc=svenkatr@ti.com \
/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.