linux-kernel - Re: [PATCH] ipack: move header files to include/linux

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1353089655.4563.56.camel@fourier.local.igalia.com>
Date:	Fri, 16 Nov 2012 19:14:15 +0100
From:	Samuel Iglesias Gonsálvez 
	<siglesias@...lia.com>
To:	Joe Perches <joe@...ches.com>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
	industrypack-devel@...ts.sourceforge.net,
	jens.taprogge@...rogge.org
Subject: Re: [PATCH] ipack: move header files to include/linux

On Fri, 2012-11-16 at 10:08 -0800, Joe Perches wrote:
> On Fri, 2012-11-16 at 18:34 +0100, Samuel Iglesias Gonsalvez wrote:
> > Move ipack header files to include/linux/ directory where they belong to.
> 
> Why do these belong in include/linux?

They are used for other drivers that could be in other directories.

> What's wrong with path relative includes?

There is nothing wrong with relative includes. It's just to do the
things as other subsystems do: keeping the bus' header file in
include/linux directory.

Is this approach wrong for this case?

Sam


Download attachment "signature.asc" of type "application/pgp-signature" (199 bytes)