Re: [PATCH][crypto-next] crypto: inside-secure - make function safexcel_try_push_requests static

Hi Colin, On Tue, Jan 02, 2018 at 02:34:10PM +, Colin King wrote: > > /* Called with ring's lock taken */ > -int safexcel_try_push_requests(struct safexcel_crypto_priv *priv, int ring, > -int reqs) > +static int safexcel_try_push_requests(struct

Re: [PATCH][crypto-next] crypto: inside-secure - make function safexcel_try_push_requests static

Hi Colin, On Tue, Jan 02, 2018 at 02:34:10PM +, Colin King wrote: > > /* Called with ring's lock taken */ > -int safexcel_try_push_requests(struct safexcel_crypto_priv *priv, int ring, > -int reqs) > +static int safexcel_try_push_requests(struct

[PATCH][crypto-next] crypto: inside-secure - make function safexcel_try_push_requests static

From: Colin Ian King The function safexcel_try_push_requests is local to the source and does not need to be in global scope, so make it static. Cleans up sparse warning: symbol 'safexcel_try_push_requests' was not declared. Should it be static? Signed-off-by: Colin

[PATCH][crypto-next] crypto: inside-secure - make function safexcel_try_push_requests static

From: Colin Ian King The function safexcel_try_push_requests is local to the source and does not need to be in global scope, so make it static. Cleans up sparse warning: symbol 'safexcel_try_push_requests' was not declared. Should it be static? Signed-off-by: Colin Ian King ---