linux-kernel - Re: how about 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: <4C57EE69.4080209@gmail.com>
Date:	Tue, 03 Aug 2010 13:24:41 +0300
From:	Boaz Harrosh <openosd@...il.com>
To:	Américo Wang <xiyou.wangcong@...il.com>
CC:	hacklu <embedway.linux@...il.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: how about KBUILD_MODNAME

On 08/03/2010 01:15 PM, Américo Wang wrote:
> 
> And it doesn't make sense to hold two drivers in one .c file.
> 

I meant when two drivers share the same .c file. But instead of
using a third common module they just share it by duplicating
the code. example:

<Kbuild>
drv1-y := drv-one.o common.o
obj-$(CONFIG_DRV1) += drv1.o

drv2-y := drv-two.o common.o
obj-$(CONFIG_DRV2) += drv2.o
</Kbuild>

When compiling common.o the KBUILD_MODNAME fails to be set

Cheers
Boaz
--
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/