summaryrefslogtreecommitdiffstats
path: root/drivers/s390
diff options
context:
space:
mode:
authorHeiko Carstens <heiko.carstens@de.ibm.com>2017-11-17 09:50:40 +0100
committerMartin Schwidefsky <schwidefsky@de.ibm.com>2017-11-20 08:51:02 +0100
commitde35089cc82c33f8be1dec5a0c3d7a05cf91720d (patch)
treee47b55158cd1458151ad59f4171856810fd561bb /drivers/s390
parent3241d3eb7d9bb7a134bedf49db196cf98b58834d (diff)
downloadtalos-obmc-linux-de35089cc82c33f8be1dec5a0c3d7a05cf91720d.tar.gz
talos-obmc-linux-de35089cc82c33f8be1dec5a0c3d7a05cf91720d.zip
s390/disassembler: remove confusing code
When searching the opcode offset table within find_insn() the check "entry->opcode == 0" was intended to clarify that 1-byte opcodes, the first one being 0, are special. However there is no mnemonic for an illegal opcode starting with 0. Therefore there is also no opcode offset table entry that matches, which again means that the check never is true. Therefore just remove the confusing check, and add a comment which hopefully explains how this works. Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com> Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'drivers/s390')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud