netdev - Re: [PATCH 3/5] net: add NL802154 interface for configuration of 802.15.4 devices

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]

Date:	Fri, 05 Jun 2009 00:54:18 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	dbaryshkov@...il.com
Cc:	johannes@...solutions.net, linux-kernel@...r.kernel.org,
	netdev@...r.kernel.org, linux-wireless@...r.kernel.org,
	slapin@...fans.org, sfr@...b.auug.org.au
Subject: Re: [PATCH 3/5] net: add NL802154 interface for configuration of
 802.15.4 devices

From: Dmitry Eremin-Solenikov <dbaryshkov@...il.com>
Date: Fri, 5 Jun 2009 11:15:29 +0400

> On Fri, Jun 05, 2009 at 08:52:17AM +0200, Johannes Berg wrote:
>> On Fri, 2009-06-05 at 06:29 +0400, Dmitry Eremin-Solenikov wrote:
>> 
>> > +/* This source file is shared between kernel and userspace sources, thus
>> > + * a bit of __KERNEL__ checks
>> > + */
>> > +#ifdef __KERNEL__
>> 
>> It's a C file. It can't be shared expect by copying, hence IMO these
>> things are pointless.
> 
> It is shared by copying. And I'd strongly prefer to have it shared
> directly by 'cp', not by 'cp' and 'patch'. E.g. currently I can ensure
> that policy definitions and commands are current just by comparing
> files. I'd like to still have that ability. Thus, I'd ask to permit this
> stuff in.

You can maintain your own code in your own directories in your
own source tree however you like.

But if you want you code in the upstream kernel, you have to clean it
of things like this.

I agree with Johannes, you have to get rid of this.
--
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