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
---
drivers/staging/lustre/lnet/selftest/conctl.c| 34
drivers/staging/lustre/lnet/selftest
ition of static 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/c
Function lnet_selftest_structure_assertion is never used and can
be removed.
Signed-off-by: Anton Saraev
---
drivers/staging/lustre/lnet/selftest/module.c | 11 ---
1 file changed, 11 deletions(-)
diff --git a/drivers/staging/lustre/lnet/selftest/module.c
b/drivers/staging/lustre/lnet
Function lnet_selftest_structure_assertion is never used and can
be removed.
Signed-off-by: Anton Saraev
---
drivers/staging/lustre/lnet/selftest/module.c | 11 ---
1 file changed, 11 deletions(-)
diff --git a/drivers/staging/lustre/lnet/selftest/module.c
b/drivers/staging/lustre/lnet
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
---
drivers/staging/lustre/lnet/selftest/conctl.c| 34
drivers/staging/lustre/lnet/selftest
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:sel
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
https://github.com/wernerd/Ske
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
---
drivers/staging/skein/include/skein.h | 14 +++---
drivers/staging/skein/include/skeinApi.h| 2 +-
drivers/staging/skein
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
---
drivers/staging/skein/Makefile | 10 +-
drivers/staging/skein/TODO
Linux Kernel use capitalized names for enum. To prepare skein
driver to mainline inclusion, we rename all enums to capitalized
names.
Signed-off-by: Anton Saraev
---
drivers/staging/skein/include/skein.h| 6 +++---
drivers/staging/skein/include/skeinApi.h | 8
drivers
Hi! To prepare skein driver for mainline inclusion we fixing most of
style issues (wrong names of functions, vars, macros, files) and
checkpatch problems in this patch set. For example, existing code
is widely use camelCase names. This patch fix it.
Anton Saraev (6):
staging: crypto: skein
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
---
drivers/staging/skein/TODO | 1 -
drivers/staging/skein/include/skein.h| 66
13 matches
Mail list logo
