lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ