From: Colin King <hidden> Date: 2018-03-11 17:03:45
From: Colin Ian King <redacted>
Functions rds_info_from_znotifier and rds_message_zcopy_from_user are
local to the source and do not need to be in global scope, so make them
static.
Cleans up sparse warnins:
net/rds/message.c:70:27: warning: symbol 'rds_info_from_znotifier' was
not declared. Should it be static?
net/rds/message.c:358:5: warning: symbol 'rds_message_zcopy_from_user'
was not declared. Should it be static?
Signed-off-by: Colin Ian King <redacted>
---
net/rds/message.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
From: Colin Ian King <redacted>
Functions rds_info_from_znotifier and rds_message_zcopy_from_user are
local to the source and do not need to be in global scope, so make them
static.
From: Colin Ian King <redacted>
Functions rds_info_from_znotifier and rds_message_zcopy_from_user are
local to the source and do not need to be in global scope, so make them
static.
Cleans up sparse warnins:
net/rds/message.c:70:27: warning: symbol 'rds_info_from_znotifier' was
not declared. Should it be static?
net/rds/message.c:358:5: warning: symbol 'rds_message_zcopy_from_user'
was not declared. Should it be static?
Signed-off-by: Colin Ian King <redacted>
---
net/rds/message.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
On 3/11/18 11:54 PM, santosh.shilimkar@oracle.com wrote:
On 3/11/18 10:03 AM, Colin King wrote:
quoted
From: Colin Ian King <redacted>
Functions rds_info_from_znotifier and rds_message_zcopy_from_user are
local to the source and do not need to be in global scope, so make them
static.
Cleans up sparse warnins:
net/rds/message.c:70:27: warning: symbol 'rds_info_from_znotifier' was
not declared. Should it be static?
net/rds/message.c:358:5: warning: symbol 'rds_message_zcopy_from_user'
was not declared. Should it be static?
Signed-off-by: Colin Ian King <redacted>
---
net/rds/message.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
Acked-by: Santosh Shilimkar <redacted>
This was fixed by kbuild robot and the fix is already in net-next.
Regards,
Santosh