All of lore.kernel.org
 help / color / mirror / Atom feed
From: Albert Herranz <albert_herranz@yahoo.es>
To: avorontsov@ru.mvista.com
Cc: linux-mmc@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [RFC PATCH 1/2] sdhci-of: reorganize driver to support additional hardware
Date: Mon, 14 Dec 2009 22:14:02 +0100	[thread overview]
Message-ID: <4B26AA9A.70607@yahoo.es> (raw)
In-Reply-To: <20091214202707.GA5300@oksana.dev.rtsoft.ru>

Anton Vorontsov wrote:
> On Mon, Dec 14, 2009 at 08:33:25PM +0100, Albert Herranz wrote:
>> This patch breaks down sdhci-of into a core portion and a eSDHC portion,
>> clearing the path to easily support additional hardware using the same
>> OF driver.
>>
>> Signed-off-by: Albert Herranz <albert_herranz@yahoo.es>
> 
> Looks really good, thanks a lot for your work!
> 
> Few minor nits down below.
> 
> [...]
>> +++ b/drivers/mmc/host/sdhci-of-core.c
> 
> Not sure if adding -core prefix makes things better (it
> actually makes the patch harder to review).
> 
> Can we leave the core in sdhci-of.c, and just factor out
> esdhc stuff from it?
> 

I wanted to preserve the module name (sdhci-of). I basically renamed sdhci-of.c to sdhci-of-core.c to avoid a recursive rule in the Makefile.
Is there an easy way to make the module build as sdhci-of from sdhci-of.c + sdhci-of-esdhc.c + whatever ?

> [...]
>> +#include <linux/mmc/host.h>
>> +#include <asm/machdep.h>
>> +#include "sdhci-of.h"
>> +
> 
> You still need to include sdhci.h. Files need to include all
> the headers they need. I.e., here you should not rely on the
> fact that sdhci-of.h includes sdhci.h.
> 

Including sdhci.h more than once currently results in duplicate definition errors because that header file is not protected with #ifdef'ery.
I can fix sdhci.h and then explicitly include it again.

> [...]
>> --- /dev/null
>> +++ b/drivers/mmc/host/sdhci-of.h
>> @@ -0,0 +1,42 @@
> [...]
>> +extern struct sdhci_of_data sdhci_esdhc;
>> +
>> +#endif /* __SDHCI_OF_H */
>> +
>> -- 
>> 1.6.3.3
> 
> Unneeded empty line at the end of sdhci-of.h.
> 

Thanks.

> If you'll manage to resend the patches before Linus roll the -rc1
> out, I'd be glad to beg Andrew to send this for v2.6.33. Because
> it will be a pity if it has to wait for 2.6.34.
> 

I'll try, as long as we solve nit #1 quickly enough :)

Cheers,
Albert

  reply	other threads:[~2009-12-14 21:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-14 19:33 [RFC PATCH 0/2] mmc: wii: sdhci controller support Albert Herranz
2009-12-14 19:33 ` [RFC PATCH 1/2] sdhci-of: reorganize driver to support additional hardware Albert Herranz
2009-12-14 20:27   ` Anton Vorontsov
2009-12-14 21:14     ` Albert Herranz [this message]
2009-12-14 19:33 ` [RFC PATCH 2/2] sdhci-of: add support for the wii sdhci controller Albert Herranz

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=4B26AA9A.70607@yahoo.es \
    --to=albert_herranz@yahoo.es \
    --cc=akpm@linux-foundation.org \
    --cc=avorontsov@ru.mvista.com \
    --cc=linux-mmc@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.