From: Tony Lindgren <tony@atomide.com>
To: Carlos Aguiar <carlos.aguiar@indt.org.br>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [01/17 PATCH] MMC: OMAP: Introduces new structures for MMC multislot support.
Date: Mon, 3 Sep 2007 08:45:11 -0700 [thread overview]
Message-ID: <20070903154510.GC21056@atomide.com> (raw)
In-Reply-To: <46DC1262.1000002@indt.org.br>
* Carlos Aguiar <carlos.aguiar@indt.org.br> [070903 07:00]:
> ext David Brownell wrote:
> > On Friday 17 August 2007, David Brownell wrote:
> >
> >> On Friday 17 August 2007, Carlos Aguiar wrote:
> >>
> >>> Introduces new structures for MMC multislot support.
> >>>
> >> Seems like #1 and #2 should be a single patch, since
> >> after #1 it won't compile ...
> >>
> >
> >
> Hi Dave,
> > ... and maybe #3, and ... ?
> >
> You're right! But this 'level of granularity' of the patches was
> requested by Tony.
Huh? Naturally the patch series should compile and work after each
step no matter what "level of granularity".
> > Also, this doesn't look to me primarily like "multislot"
> > support. It's also "stop relying on GPIOs" for various
> > things that newer boards handle with external chips
> > (like CD and WP switches), and "move board-specific code
> > out of the MMC driver"...
> >
> The concept of multislot applied here is to provide a code (and needed
> modifications) that runs OMAP platforms with a single and/or two MMC slots.
Carlos, what Dave is saying above is that the patches don't do what you have
in the patch description. You should try to do a series of independent
easy to read patches that match the patch description.
Regards,
Tony
next prev parent reply other threads:[~2007-09-03 15:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-17 19:01 [01/17 PATCH] MMC: OMAP: Introduces new structures for MMC multislot support Carlos Aguiar
2007-08-17 21:45 ` David Brownell
2007-08-17 21:55 ` David Brownell
2007-09-03 13:55 ` Carlos Aguiar
2007-09-03 15:45 ` Tony Lindgren [this message]
2007-09-03 17:38 ` Carlos Aguiar
2007-09-04 8:32 ` Madhusudhan Chikkature Rajashekar
2007-09-04 14:48 ` Carlos Aguiar
2007-09-04 14:59 ` Madhusudhan Chikkature Rajashekar
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=20070903154510.GC21056@atomide.com \
--to=tony@atomide.com \
--cc=carlos.aguiar@indt.org.br \
--cc=linux-omap-open-source@linux.omap.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox