From: Subrata <sub...@us...> - 2009-02-26 13:18:46
|
Update of /cvsroot/ltp/ltp/testcases/kernel/device-drivers/pci/user_tpci In directory ddv4jf1.ch3.sourceforge.com:/tmp/cvs-serv4515/ltp/testcases/kernel/device-drivers/pci/user_tpci Modified Files: tpci_ki.c user_tpci.c Log Message: Clear Trailing Whitespace. Signed-off-by: Michal Simek <mo...@mo...>. Index: user_tpci.c =================================================================== RCS file: /cvsroot/ltp/ltp/testcases/kernel/device-drivers/pci/user_tpci/user_tpci.c,v retrieving revision 1.3 retrieving revision 1.4 diff -C2 -d -r1.3 -r1.4 *** user_tpci.c 9 Jan 2006 19:17:17 -0000 1.3 --- user_tpci.c 26 Feb 2009 12:02:10 -0000 1.4 *************** *** 105,109 **** } ! int tpciclose() { --- 105,109 ---- } ! int tpciclose() { Index: tpci_ki.c =================================================================== RCS file: /cvsroot/ltp/ltp/testcases/kernel/device-drivers/pci/user_tpci/tpci_ki.c,v retrieving revision 1.2 retrieving revision 1.3 diff -C2 -d -r1.2 -r1.3 *** tpci_ki.c 9 Jan 2006 19:17:17 -0000 1.2 --- tpci_ki.c 26 Feb 2009 12:02:10 -0000 1.3 *************** *** 19,31 **** * This file will include user space functions that will drive ! * the kernel module tpci to test various pci functions * and kernel calls. Each function will need to setup the tif ! * structure so that the in parameters and out parameters * are correctly initialized * ! * use tif structure for passing params between user ! * space and kernel space, in some tests it is really ! * not needed but makes easy to maintain all tests if ! * have the same process to read in params in the * kernel module no matter what the test is * --- 19,31 ---- * This file will include user space functions that will drive ! * the kernel module tpci to test various pci functions * and kernel calls. Each function will need to setup the tif ! * structure so that the in parameters and out parameters * are correctly initialized * ! * use tif structure for passing params between user ! * space and kernel space, in some tests it is really ! * not needed but makes easy to maintain all tests if ! * have the same process to read in params in the * kernel module no matter what the test is * *************** *** 82,87 **** tif.in_len = 0; tif.in_data = 0; ! tif.out_len = 0; ! tif.out_data = 0; tif.out_rc = 0; --- 82,87 ---- tif.in_len = 0; tif.in_data = 0; ! tif.out_len = 0; ! tif.out_data = 0; tif.out_rc = 0; |