[<prev] [next>] [day] [month] [year] [list]
Message-ID: <b0c88b10811192220s7a61f1eax2dfc84e935a7a05a@mail.gmail.com>
Date: Thu, 20 Nov 2008 07:20:46 +0100
From: "Antonio R. Costa" <costa.antonior@...il.com>
To: "Linux Kernel list" <linux-kernel@...r.kernel.org>
Subject: Fwd: [PATCH] mmc: atmel-mci: move atmel-mci.h file to include/linux
Hi all,
I agree with Pierre.
I find pretty confusing to mix protocol .h file with drver specific includes.
Why can't we have something like:
include/linux/mmc
include/drivers/mmc
Ciao,
Antnoio
2008/11/19 Pierre Ossman <drzeus@...eus.cx>
>
> On Thu, 13 Nov 2008 15:43:34 +0100
> Nicolas Ferre <nicolas.ferre@...el.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...
>
> --
> -- Pierre Ossman
>
> WARNING: This correspondence is being monitored by the
> Swedish government. Make sure your server uses encryption
> for SMTP traffic and consider using PGP for end-to-end
> encryption.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists