You can add a filter that will match this IP with an empty action that will classify the packet as "pass", without going through further filters. Since without specifying a priority the order can't be guessed, both filters should have a priority (aka prio or pref) set. So if you want to spare the IP 192.0.2.10 from rate limitation, you can replace your filter with those two:
tc filter add dev eth1 parent ffff: protocol ip priority 1 \
u32 match ip src 192.0.2.10 action pass
tc filter add dev eth1 parent ffff: protocol ip priority 2 \
u32 match ip sport 22 0xffff action police rate 800kbit burst 24000 drop flowid :1
Note that police is also an action, but the action keyword is optional (while it has to be stated for an empty action with only a pass option).
Also, if it can still suit this case, you should consider using shaping (delaying before having to drop) on egress traffic, rather than policing (dropping only) on ingress traffic: this would probably improve performances (avoiding duplicate packets on the wire because of drops).