Squashed backup commit (no shallow-clone history issues) of xiaomi-mt6833-dev/kernel_xiaomi_mt6833 (lineage-23.2 branch, upstream commit 9eece662e) plus all fixes applied to get everpal_defconfig building clean against a modern (GCC 15.2.0) toolchain -- see the previous commit message on the lineage-23.2 branch (also in this repo history is not available here since this is a squashed snapshot; full incremental history lives in the local DL380 checkout and the upstream GitHub remote). Upstream: https://github.com/xiaomi-mt6833-dev/kernel_xiaomi_mt6833 (lineage-23.2)
73 lines
971 B
C
73 lines
971 B
C
// SPDX-License-Identifier: GPL-2.0
|
|
#define _GNU_SOURCE
|
|
#include "main.h"
|
|
#include <assert.h>
|
|
|
|
/* stub implementation: useful for measuring overhead */
|
|
void alloc_ring(void)
|
|
{
|
|
}
|
|
|
|
/* guest side */
|
|
int add_inbuf(unsigned len, void *buf, void *datap)
|
|
{
|
|
return 0;
|
|
}
|
|
|
|
/*
|
|
* skb_array API provides no way for producer to find out whether a given
|
|
* buffer was consumed. Our tests merely require that a successful get_buf
|
|
* implies that add_inbuf succeed in the past, and that add_inbuf will succeed,
|
|
* fake it accordingly.
|
|
*/
|
|
void *get_buf(unsigned *lenp, void **bufp)
|
|
{
|
|
return "Buffer";
|
|
}
|
|
|
|
bool used_empty()
|
|
{
|
|
return false;
|
|
}
|
|
|
|
void disable_call()
|
|
{
|
|
assert(0);
|
|
}
|
|
|
|
bool enable_call()
|
|
{
|
|
assert(0);
|
|
}
|
|
|
|
void kick_available(void)
|
|
{
|
|
assert(0);
|
|
}
|
|
|
|
/* host side */
|
|
void disable_kick()
|
|
{
|
|
assert(0);
|
|
}
|
|
|
|
bool enable_kick()
|
|
{
|
|
assert(0);
|
|
}
|
|
|
|
bool avail_empty()
|
|
{
|
|
return false;
|
|
}
|
|
|
|
bool use_buf(unsigned *lenp, void **bufp)
|
|
{
|
|
return true;
|
|
}
|
|
|
|
void call_used(void)
|
|
{
|
|
assert(0);
|
|
}
|