From: Simon Horman <simon@horms.net>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [patch 1/3] mmc, sh: Move MMCIF_PROGRESS_* into sh_mmcif.h
Date: Mon, 06 Dec 2010 01:28:02 +0000 [thread overview]
Message-ID: <20101206012801.GA3735@verge.net.au> (raw)
In-Reply-To: <AANLkTikdKiNg3Mvz3ycqyqh=thNSWijPURK6HG+fbY-o@mail.gmail.com>
On Mon, Dec 06, 2010 at 09:57:17AM +0900, Magnus Damm wrote:
> On Mon, Dec 6, 2010 at 9:12 AM, Simon Horman <horms@verge.net.au> wrote:
> > Allow MMCIF_PROGRESS_* to be shared.
> >
> > Cc: Magnus Damm <magnus.damm@gmail.com>
> > Signed-off-by: Simon Horman <horms@verge.net.au>
>
> I'm a bit hesitant to this change. This because the progress really
> hasn't anything to do with the MMCIF hardware block. The enum does use
> the MMCIF prefix though, so I guess i should be silent. =)
>
> In the future I can imagine that there will be more boards making use
> of this feature, and other MMC/SD-capable hardware blocks that want to
> support early loading. Perhaps moving the enum into the header like
> you suggest is the easiest way forward. Unless there is any easy way
> to share the same progress code between MMCIF and say SDHI.
The way that I see things is that with the last patch in this series
there are two files using these enums, one under arch/sh and one under
arch/arm. They both relate to using MMCIF. And they both assume that
there are states we are interested in that can be usefully displayed.
If SHDI can make use of this it may make sense to move it somewhere
else at that time.
OTOH, its just 4 integers and this is really just debugging code.
I wouldn't be opposed to removing it altogether.
next prev parent reply other threads:[~2010-12-06 1:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 0:12 [patch 0/3] mmc, ARM: Add zboot from MMC support for SuperH Mobile ARM Simon Horman
2010-12-06 0:12 ` [patch 1/3] mmc, sh: Move MMCIF_PROGRESS_* into sh_mmcif.h Simon Horman
2010-12-06 0:57 ` Magnus Damm
2010-12-06 1:28 ` Simon Horman [this message]
2010-12-06 1:38 ` Magnus Damm
2010-12-06 0:12 ` [patch 2/3] mmc, sh: Remove sh_mmcif_boot_slurp() Simon Horman
2010-12-06 0:12 ` [patch 3/3] mmc, ARM: Add zboot from MMC support for SuperH Mobile ARM Simon Horman
2010-12-06 0:44 ` [patch 3/3] mmc, ARM: Add zboot from MMC support for SuperH Simon Horman
2010-12-06 0:51 ` Magnus Damm
2010-12-06 1:11 ` Simon Horman
2010-12-06 1:33 ` Magnus Damm
2010-12-06 1:42 ` Simon Horman
2010-12-06 7:56 ` [patch 3/3 v2] " Simon Horman
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=20101206012801.GA3735@verge.net.au \
--to=simon@horms.net \
--cc=linux-arm-kernel@lists.infradead.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).