From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Pierre Ossman <drzeus@drzeus.cx>,
Haavard Skinnemoen <hskinnemoen@atmel.com>
Cc: Ben Dooks <ben-linux@fluff.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
kernel@avr32linux.org
Subject: Re: [PATCH] mmc: atmel-mci: move atmel-mci.h file to include/linux
Date: Thu, 20 Nov 2008 15:25:18 +0100 [thread overview]
Message-ID: <4925734E.1060606@atmel.com> (raw)
In-Reply-To: <20081119193631.448ae25e@mjolnir.drzeus.cx>
Pierre Ossman :
> On Thu, 13 Nov 2008 15:43:34 +0100
> Nicolas Ferre <nicolas.ferre@atmel.com> wrote:
>
>> Ben Dooks :
>>> Would people object to putting this in include/linux/mmc/atmel.h
>>> to avoid making include/linux abound with device/subsystem/machine
>>> specific header files?
>> I tend to agree *but* it seems that header files in include/linux/mmc
>> are mostly sd/mmc subsystem core files (I mean, not driver ones).
>> Although, a bunch of atmel-a_driver.h files are already in include/linux...
>>
>> Pierre, a comment ?
>>
>
> I'd prefer if include/linux/mmc could stay clean and just have core
> stuff since the header files are basically the reference documentation
> for the subsystem. But if you can't find any other way...
I agree with both of you Pierre and Antonio.
Haavard, I submit a patch which also fix the mimc200 board very soon now.
Bye,
--
Nicolas Ferre
next prev parent reply other threads:[~2008-11-20 14:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 11:14 [PATCH] mmc: atmel-mci: move atmel-mci.h file to include/linux Nicolas Ferre
2008-11-13 11:26 ` Haavard Skinnemoen
2008-11-13 13:48 ` Ben Dooks
2008-11-13 14:43 ` Nicolas Ferre
2008-11-19 18:36 ` Pierre Ossman
[not found] ` <b0c88b10811192207oe65e02fg91ec6476b49564ba@mail.gmail.com>
2008-11-20 6:20 ` Fwd: " Antonio R. Costa
2008-11-20 14:25 ` Nicolas Ferre [this message]
2008-11-20 14:34 ` Haavard Skinnemoen
2008-11-20 14:59 ` Nicolas Ferre
2008-11-22 18:41 ` Pierre Ossman
2009-01-05 16:23 ` Haavard Skinnemoen
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=4925734E.1060606@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=ben-linux@fluff.org \
--cc=drzeus@drzeus.cx \
--cc=hskinnemoen@atmel.com \
--cc=kernel@avr32linux.org \
--cc=linux-kernel@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