linux-kernel - Re: Staging: RAR support - bring ready to move from staging

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: <20100504155112.GA26143@kroah.com>
Date:	Tue, 4 May 2010 08:51:12 -0700
From:	Greg KH <greg@...ah.com>
To:	Alan Cox <alan@...ux.intel.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Staging: RAR support - bring ready to move from staging

On Tue, May 04, 2010 at 10:50:32AM +0100, Alan Cox wrote:
> 
> rar: perform a clean up pass
> 
> - Move to a registration model where each RAR is claimed/unclaimed
> - Use that to fix the client stuff (one client per RAR so no need to queue stuff)
> - Support unregister so drivers can rmmod themselves safely
> - Fix locking hang on calling rar lock from rar callback
> - Clean up
> - Kerneldoc

I get the following build errors with this patch:
	  CC [M]  drivers/staging/memrar/memrar_handler.o
	drivers/staging/memrar/memrar_handler.c: In function ‘memrar_init’:
	drivers/staging/memrar/memrar_handler.c:910: warning: passing argument 1 of ‘register_rar’ makes integer from pointer without a cast
	drivers/staging/memrar/../rar_register/rar_register.h:37: note: expected ‘int’ but argument is of type ‘int (*)(void *)’
	drivers/staging/memrar/memrar_handler.c:910: error: too few arguments to function ‘register_rar’
	make[2]: *** [drivers/staging/memrar/memrar_handler.o] Error 1
	make[1]: *** [drivers/staging/memrar] Error 2
	make: *** [_module_drivers/staging] Error 2

Should I have applied your other patch first?

thanks,

greg k-h
--
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/