kunit: skb: use "gfp" variable instead of hardcoding GFP_KERNEL
[ Upstream commitfd0a5afb54] The intent here was clearly to use the gfp variable flags instead of hardcoding GFP_KERNEL. All the callers pass GFP_KERNEL as the gfp flags so this doesn't affect runtime. Fixes:b3231d353a("kunit: add a convenience allocation wrapper for SKBs") Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org> Reviewed-by: David Gow <davidgow@google.com> Reviewed-by: Kuan-Wei Chiu <visitorckw@gmail.com> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org> Signed-off-by: Sasha Levin <sashal@kernel.org>
This commit is contained in:
committed by
Greg Kroah-Hartman
parent
e691826a3d
commit
673f503cfe
@@ -29,7 +29,7 @@ static void kunit_action_kfree_skb(void *p)
|
||||
static inline struct sk_buff *kunit_zalloc_skb(struct kunit *test, int len,
|
||||
gfp_t gfp)
|
||||
{
|
||||
struct sk_buff *res = alloc_skb(len, GFP_KERNEL);
|
||||
struct sk_buff *res = alloc_skb(len, gfp);
|
||||
|
||||
if (!res || skb_pad(res, len))
|
||||
return NULL;
|
||||
|
||||
Reference in New Issue
Block a user