From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] mmc, sh: Move MMCIF_PROGRESS_* into sh_mmcif.h
Date: Tue, 11 Jan 2011 02:07:51 +0000 [thread overview]
Message-ID: <20110111020751.GE3760@linux-sh.org> (raw)
In-Reply-To: <20110110230549.GA20886@verge.net.au>
On Tue, Jan 11, 2011 at 08:05:49AM +0900, Simon Horman wrote:
> Allow MMCIF_PROGRESS_* to be shared.
>
> Cc: Magnus Damm <magnus.damm@gmail.com>
> Signed-off-by: Simon Horman <horms@verge.net.au>
> Signed-off-by: Paul Mundt <lethal@linux-sh.org>
> ---
> arch/sh/boot/romimage/mmcif-sh7724.c | 3 ---
> include/linux/mmc/sh_mmcif.h | 3 +++
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> Hi Paul,
>
> this change didn't seem to make it into your
> rc1 pull request, although it is present in
> remotes/sh-2.6/common/mmcif.
>
Blast. I thought I had all of the common/mmcif stuff rolled in via
rmobile/mmcif, but it seems this one slipped by. I'll make sure it gets
merged this time around.
> It is needed by "[patch v5] mmc, ARM: Add zboot from MMC support for SuperH
> Mobile ARM", which I was hoping to get Russell to merge post 2.6.38-rc1.
> Perhaps I should just add the enums directly to
> arch/arm/boot/compressed/mmcif-sh7372.c in that patch for now?
>
Optionally you can just push it out without the enums resolved also, the
build target will just fail until the other patch catches up.
next prev parent reply other threads:[~2011-01-11 2:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 23:05 [PATCH] mmc, sh: Move MMCIF_PROGRESS_* into sh_mmcif.h Simon Horman
2011-01-11 2:07 ` Paul Mundt [this message]
2011-01-11 2:51 ` Simon Horman
2011-01-11 3:51 ` Simon Horman
2011-01-13 21:12 ` Paul Mundt
2011-01-14 1:29 ` Simon Horman
2011-01-14 6:49 ` Paul Mundt
2011-01-14 7:06 ` Magnus Damm
2011-01-14 7:08 ` Paul Mundt
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=20110111020751.GE3760@linux-sh.org \
--to=lethal@linux-sh.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).