summaryrefslogtreecommitdiffstats
path: root/kernel
diff options
context:
space:
mode:
authorGreg Ungerer <gerg@uclinux.org>2012-05-09 16:03:06 +1000
committerGreg Ungerer <gerg@uclinux.org>2012-07-16 09:59:20 +1000
commit5bd9dd450173bc1464e8218e717d218075b9f1a4 (patch)
tree83e06d904ae9897dc419e88394e6b1ac75f2213a /kernel
parent84a1caf1453c3d44050bd22db958af4a7f99315c (diff)
downloadtalos-op-linux-5bd9dd450173bc1464e8218e717d218075b9f1a4.tar.gz
talos-op-linux-5bd9dd450173bc1464e8218e717d218075b9f1a4.zip
m68k: use some direct calls to ret_from_exception in entry code
The ret_from_excption code is referenced by its function name, or by a label set at the start of its code. The non-MMU code can share some of this code if we make direct calls to ret_from_exception instead of the associated label. The effected function paths are: buserr, trap and ret_from_fork. So change these to branch directly to ret_from_exception. Signed-off-by: Greg Ungerer <gerg@uclinux.org> Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud