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: Thu, 13 Jan 2011 21:12:28 +0000 [thread overview]
Message-ID: <20110113211228.GB20418@linux-sh.org> (raw)
In-Reply-To: <20110110230549.GA20886@verge.net.au>
On Tue, Jan 11, 2011 at 12:51:05PM +0900, Simon Horman wrote:
> On Tue, Jan 11, 2011 at 11:51:50AM +0900, Simon Horman wrote:
> > On Tue, Jan 11, 2011 at 11:07:51AM +0900, Paul Mundt wrote:
> > > 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.
> > >
> > > Optionally you can just push it out without the enums resolved also, the
> > > build target will just fail until the other patch catches up.
> >
> > Ok, I guess that sounds reasonable. Its not like many people/anyone will have
> > the config option enabled while the merge is shaking itself out.
>
> Submitted to Russell's patch tracker
> http://www.arm.linux.org.uk/developer/patches/viewpatch.php?idf17/1
Everything has been pulled by Linus now, so it's just this patch in
the patch tracker that should be outstanding. You may wish to double
check to make sure I got it all this time around :-)
next prev parent reply other threads:[~2011-01-13 21:12 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
2011-01-11 2:51 ` Simon Horman
2011-01-11 3:51 ` Simon Horman
2011-01-13 21:12 ` Paul Mundt [this message]
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=20110113211228.GB20418@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 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.