ccnl: fix two typos

ccnl: fix ageing timeout

Use `filter` instead of `findstring`

Do not zero out sched_threads needlessly

core: msg: don't wake up sender after receive if it's REPLY_BLOCKED

Add wireshark dissector for native packets

fix ignore_add unused parameter warning

use filter instead of findstring in BOARD_BLACKLIST checking

Add quadword math library

replace all endless for loops by while

Introduce board blacklists and board whitelists

shell: remove useless copying of input string

https://github.com/Kijewski/RIOT/commit/102dc453828012985f82915ad826be069f444e61#commitcomment-5378590

Add USEPKG variable for Makefiles

Do not mandate input language

See #672

An application might want to use C11 features. The user would assume
that setting `CFLAGS=-std=gnu11` in the Makefile would work. It does not
since the board's Makefile.include shadows the `-std` flag.

This patch removes the `-std=gnu99` from the various Makefile.includes,
and sets the flag in the common Makefile.include of RIOT instead.
If an `-std` flag was provided by an earlier Makefile (the application,
the board, or the CPU [whilst only the former one should]), then no
additional flag is set. It is first tested if the supplied compiler
understands `-std=gnu99`, then `-std=c99`.

fix test_irq Makefile

closes #696

added two test cases for issue #100

test_thread_msg_block_w_queue:
	demonstrates the behaviour described in issue #100
	and that it is solved by PR #569

test_thread_msg_block_wo_queue:
	demonstrates behaviour similar to the above but without
	a messge queue. This works with the current master, but
	breaks with PR #569

When setting the running task reply_blocked, it is implicitly removed
from the runqueue. But if queueing of a msg is actually successful, the
thread exits msg_send without yielding, continuing to run even if it's
not supposed to.

Nice example of why multiple function exit points lead to weird
errors...

Makefiles: Always use absolute paths with configurable paths variables

fix wiki links

solves issue #100

If the sender is reply-blocked, waking it up after its message has been
delivered is wrong. It needs to stay reply-blocked until the reply has
been delivered.

Portable definition of function attributes