Upstream had a 2.0 tag for a while, then removed it and added a 1.1 tag :-/
Let's make it match to avoid confusion. There's only one new commit
added, which adds a missing manpage.

Also, update the outdated version comment in rt-tests.inc

Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>

This recipe uses some convoluted methods to ensure the build is using the right
flags but they don't appear to be needed anymore.

No need to prepend HOST_CC_ARCH/TOOLCHAIN_OPTIONS via CFLAGS as the Makefile
picks up CC from the environment and that includes these options.

No need to append the default CFLAGS as their special options are actually in
CPPFLAGS.

Signed-off-by: Ross Burton <ross.burton@intel.com>

0001-Makefile-Set-CC-AR-variable-only-if-it-doesn-t-have-.patch has been merged upstream

Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

bump version to 0.96

Signed-off-by: Maxin B. John <maxin.john@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>

All of the rt-tests patches that OE has been carrying have been
upstreamed or superceded by changes in the v0.94 release.

Adjust SRC_URI to point to canonical upstream git repo, instead of a
development tree.

There was a notable change upstream that required slight reworking of
the recipe.  rt-tests now joins other kbuild-inspired projects by making
use of a CROSS_COMPILE flag to indicate the compiler prefix.

Previously TOOLCHAIN_OPTIONS were conveyed via $CC directly, however,
this does not work with CROSS_COMPILE.  Workaround this by both
specifying CROSS_COMPILE, and feeding the rt-tests build system the
proper $(HOST_CC_ARCH)$(TOOLCHAIN_OPTIONS) via $CFLAGS.

Signed-off-by: Josh Cartwright <joshc@ni.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>

Neither the hackbench target, or the rt-migrate-test target actually
depend on librttest.a; drop this unnecessary patch.

Signed-off-by: Josh Cartwright <joshc@ni.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

Currently gzip on host is used. If host gzip is provided by pigz, it
fails to redo install that pigz can't handle the option after file name.
When run command for target install in Makefile:

gzip src/backfire/backfire.4 -c > OUTPUT_FILE

File src/backfire/backfire.4 is zipped into backfire.4.gz but the
OUTPUT_FILE is empty. When rerun do_install, it shows warning:

| gzip: src/backfire/backfire.4 does not exist -- skipping

and empty manual gzip files are created:

$ file image/usr/share/man/man4/backfire.4.gz
image/usr/share/man/man4/backfire.4.gz: empty

Fix it by putting option '-c' before the file name.

Signed-off-by: Kai Kang <kai.kang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

Version upgrade to v0.92
Rebased below listed patch to newer source code:
	added-missing-dependencies.patch

Signed-off-by: Maxin B. John <maxin.john@enea.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>

1. Upgrade version to 0.91
2. Add ptest support

[YOCTO #1569]

Signed-off-by: Thomas Lundström <thomas.lundstrom@enea.com>
Signed-off-by: Maxin B. John <maxin.john@enea.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

The "-c" doesn't work in command "gzip file -c", need use "gzip -c file"

Signed-off-by: Robert Yang <liezhi.yang@windriver.com>