netlabel: use GFP flags from caller instead of GFP_ATOMIC
authorDan Carpenter <dan.carpenter@oracle.com>
Wed, 21 Mar 2012 20:41:01 +0000 (20:41 +0000)
committerBen Hutchings <ben@decadent.org.uk>
Sat, 13 Sep 2014 22:41:42 +0000 (23:41 +0100)
commit908964e5d5b6dd6cfaee838e1bdad0b8f62c7583
treed748d6796f1f281d4c786485665c21047c6255d0
parent8977e721d5fe7c6d4ce734cd5039b80c2d6f71a3
netlabel: use GFP flags from caller instead of GFP_ATOMIC

commit 64b5fad526f63e9b56752a7e8e153b99ec0ddecd upstream.

This function takes a GFP flags as a parameter, but they are never used.
We don't take a lock in this function so there is no reason to prefer
GFP_ATOMIC over the caller's GFP flags.

There is only one caller, cipso_v4_map_cat_rng_ntoh(), and it passes
GFP_ATOMIC as the GFP flags so this doesn't change how the code works.
It's just a cleanup.

Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
net/netlabel/netlabel_kapi.c