netdev - Re: [PATCH 1/5] wil6210: Convert to Kbuild

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: <1397059601.14321.19.camel@joe-AO722>
Date:	Wed, 09 Apr 2014 09:06:41 -0700
From:	Joe Perches <joe@...ches.com>
To:	Vladimir Kondratiev <qca_vkondrat@....qualcomm.com>,
	Michal Marek <mmarek@...e.cz>
Cc:	"John W . Linville" <linville@...driver.com>,
	linux-wireless@...r.kernel.org, wil6210@....qualcomm.com,
	netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH 1/5] wil6210: Convert to Kbuild

(adding Michal Marek)

On Wed, 2014-04-09 at 17:08 +0300, Vladimir Kondratiev wrote:
> On Tuesday, April 08, 2014 09:14:51 AM Joe Perches wrote:
> > On Tue, 2014-04-08 at 11:36 +0300, Vladimir Kondratiev wrote:
> > > Convert Makefile -> Kbuild,
> > > to make off-kernel development easier and less intrusive.
> > No drivers/net directory uses Kbuild.
> > Why should this?
> 
> because it makes it easier to do off-kernel development, and then
> move things to the proper location within the kernel without
> conflicting changes in the Makefile.
> As I understand, Kbuild is better choice because it is really not
> standalone "Makefile", it is intended to be included by the real
> Makefile. Thus, distinct name is better.
> Are there any reasons why not using Kbuild? I did not found
> guidelines when use Kbuild and when not.

Michal?  Any opinion?


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html