Function lnet_selftest_structure_assertion is never used and can
be removed.
Signed-off-by: Anton Saraev antonysar...@gmail.com
---
drivers/staging/lustre/lnet/selftest/module.c | 11 ---
1 file changed, 11 deletions(-)
diff --git a/drivers/staging/lustre/lnet/selftest/module.c
b
declaration and deletion of function should be in two
different patches. So the second patch depends on the first...
Anton Saraev (2):
staging:lustre:lnet:selftest: fix sparse warnings
staging:lustre:lnet:selftest: remove unused function
drivers/staging/lustre/lnet/selftest/conctl.c| 34
Fix sparse warnings: symbol X was not declared. Should it be static?
Some functions used only in files where they are declared. They can
be static.
Signed-off-by: Anton Saraev antonysar...@gmail.com
---
drivers/staging/lustre/lnet/selftest/conctl.c| 34
drivers/staging
Patch fix simple sparse warnings: make functions static and remove
unused code. I'm doing only little testing: module was loaded properly,
output of lst without real server is the same as before.
Anton Saraev (2):
staging:lustre:lnet:selftest: fix sparse warnings
staging:lustre:lnet:selftest
Fix sparse warnings: symbol X was not declared. Should it be static?
Some functions used only in files where they are declared. They can
be static.
Signed-off-by: Anton Saraev antonysar...@gmail.com
---
drivers/staging/lustre/lnet/selftest/conctl.c| 34
drivers/staging
Function lnet_selftest_structure_assertion is never used and can
be removed.
Signed-off-by: Anton Saraev antonysar...@gmail.com
---
drivers/staging/lustre/lnet/selftest/module.c | 11 ---
1 file changed, 11 deletions(-)
diff --git a/drivers/staging/lustre/lnet/selftest/module.c
b
On Thu, May 22, 2014 at 01:04:41PM -0400, Jason Cooper wrote:
I do not, I'm unsure if Anton has anything pending capable of
upstreaming.
I have two simple patches. But I don't know is it necessary to send
this patches. First is export of functions in *api.c files.
But it is trivial part of api
On Tue, May 20, 2014 at 10:24:11AM -0600, Jake Edge wrote:
On Tue, 20 May 2014 10:47:57 -0400 Jason Cooper wrote:
but some kind of tests are needed to ensure nothing breaks before
digging into that ...
I have some test: slightly modified version of tests from
camelCase is not accepted in the Linux Kernel. To prepare skein
driver for mainline inclusion, we rename all functions to
non-camelCase equivalents.
Signed-off-by: Anton Saraev antonysar...@gmail.com
---
drivers/staging/skein/TODO | 1 -
drivers/staging/skein/include/skein.h
camelCase is not accepted in the Linux Kernel. To prepare skein
driver for mainline inclusion, we rename all files to
non-camelCase equivalents.
Signed-off-by: Anton Saraev antonysar...@gmail.com
---
drivers/staging/skein/Makefile | 10 +-
drivers/staging
Code have skein_512_ctx and skein_256_ctx but skein1024_ctx.
It would be logical to convert these names to a single form.
Signed-off-by: Anton Saraev antonysar...@gmail.com
---
drivers/staging/skein/include/skein.h | 14 +++---
drivers/staging/skein/include/skeinApi.h| 2
11 matches
Mail list logo