I don't know what to do with this. IMHO the warning is useless in this
particular case. It happens only on a few targets and depends on the
kernel config, etc.
If the condition is always false in some cases then so be it. The
compiler can optimize the unneeded code away I'm sure.
On Mon, 15
Hi Nicolas,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: f82e7b57b5fc48199e2f26ffafe2f96f7338ad3d
commit: 2717769e204e83e65b8819c5e2ef3e5b6639b270 vt: don't hardcode the mem
allocation upper bound
date: 7
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 642b151f45dd54809ea00ecd3976a56c1ec9b53d
commit: 2717769e204e83e65b8819c5e2ef3e5b6639b270 vt: don't hardcode the mem
allocation upper bound
date: 4 weeks ago
config: ia64-defconfig (attached as .config)
3 matches
Mail list logo