On 06/18/2013 06:21 PM, [email protected] wrote: > >>> What about creating module_exists() module_load() and module_unload() >>> library functions? >> Yeah, it is possible. Could I use tst_resource files for that? Or perhaps, >> would it be better to create tst_modules files? > Start a separate source file for that, tst_module(s) is OK. > I would like to implement tst_module_load() function with variable argument list (use for command line parameters of the insmod command). There is a macro EXPAND_VAR_ARGS defined in tst_res.c, which might be used by that function. Is it possible to move it outside of the tst_res.c file, where it can be easily accessed by other c files? >>> The path to the module should be determined from LTPROOT env variable, >>> see lib/tst_resource.c and lib/tst_resource.h that handles similar >>> situation for files needed by the tests. >>> >>> >>>> + >>>> +static void cleanup(void) >>>> +{ >>>> + if (skip_cleanup) >>>> + return; >>>> + int i; >>>> + for (i = fw_num - 1; i>= 0; --i) { >>> Is there any reason for the loop going backward? >>> >> It is the only way to successfully remove created directories. >> I need to start from the last created file or/and directory and move >> upward. > I see, some of the dirs are subdirs of previously created dirs. What > about adding a short comment explaining that? > OK
Thanks, Alexey ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
