destiny: wireshark compliant tcp flags
This enum is also used to set the tcp flags within a tcp header.
With the current values in this enum, wireshark is not able to
recognize the tcp segments as their actual tcp type,
and thus odd messages in wireshark appear.

destiny: reusing tcp flags for combinations
core/cortex-m: add missing NORETURNs to thread_arch
destiny: change byte order of ipv6_header->length
When accessing the length field of an ipv6_header a byte order switch (host -> network) is necessary.
Otherwise, it breaks calculations or the checksum and other tcp related computations.
Furthermore, when writing to ipv6_header->length it is important to switch this
from host byte order to network byte order.
Merge pull request #1275 from cgundogan/fix_tcp_flags_for_wireshark

destiny: wireshark compliant tcp flags
Merge pull request #1300 from cgundogan/fix_wrong_byte_order_ipv6_length

destiny: change byte order of ipv6_header->length
Merge pull request #1292 from Kijewski/issue-1288

core/cortex-m: add missing NORETURNs to thread_arch