From: Ulf Hansson <ulf.hansson@stericsson.com>
To: Per FORLIN <per.forlin@stericsson.com>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Chris Ball <cjb@laptop.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Russell King <rmk+kernel@arm.linux.org.uk>
Subject: Re: [PATCH] ARM: mmci: add capabilities2 for MMC_CAP2
Date: Tue, 29 Nov 2011 14:43:38 +0100 [thread overview]
Message-ID: <4ED4E18A.3070907@stericsson.com> (raw)
In-Reply-To: <1321268548-21933-1-git-send-email-per.forlin@stericsson.com>
Per FORLIN wrote:
> Signed-off-by: Per Forlin <per.forlin@stericsson.com>
> ---
> This patch depends on patches adding CAP2 available on mmc-next.
> Chris, would you mind merging this through your tree when it
> has been accepted.
>
Acked-by: Ulf Hansson <ulf.hansson@stericsson.com>
WARNING: multiple messages have this Message-ID (diff)
From: ulf.hansson@stericsson.com (Ulf Hansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mmci: add capabilities2 for MMC_CAP2
Date: Tue, 29 Nov 2011 14:43:38 +0100 [thread overview]
Message-ID: <4ED4E18A.3070907@stericsson.com> (raw)
In-Reply-To: <1321268548-21933-1-git-send-email-per.forlin@stericsson.com>
Per FORLIN wrote:
> Signed-off-by: Per Forlin <per.forlin@stericsson.com>
> ---
> This patch depends on patches adding CAP2 available on mmc-next.
> Chris, would you mind merging this through your tree when it
> has been accepted.
>
Acked-by: Ulf Hansson <ulf.hansson@stericsson.com>
next prev parent reply other threads:[~2011-11-29 13:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 11:02 [PATCH] ARM: mmci: add capabilities2 for MMC_CAP2 Per Forlin
2011-11-14 11:02 ` Per Forlin
2011-11-17 7:42 ` Linus Walleij
2011-11-17 7:42 ` Linus Walleij
2011-11-29 13:43 ` Ulf Hansson [this message]
2011-11-29 13:43 ` Ulf Hansson
2011-11-30 11:39 ` Linus Walleij
2011-11-30 11:39 ` Linus Walleij
2011-12-01 17:41 ` Chris Ball
2011-12-01 17:41 ` 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=4ED4E18A.3070907@stericsson.com \
--to=ulf.hansson@stericsson.com \
--cc=cjb@laptop.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=per.forlin@stericsson.com \
--cc=rmk+kernel@arm.linux.org.uk \
/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.