compat-drivers: make patches apply again

Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
compat-drivers: fix handing of include/uapi

The kernel make file uses an include path of kernel/include,
kernel/include/uapi (I removed all the other unrelated paths). Now
compat-drivers should also use this path otherwise we have to patch
many files. With this patch for compat-drivers it creates a include
path like this: w-d/include, w-d/include/uapi, kernel/include,
kernel/include/uapi that way this is similar to the way the kernel does
it.
When copying all the upai headers like it was done before in compat-
drivers, some headers in c-d/include/uapi will overwrite some important
headers in the kernel, we should just copy the files we actually need.
With this patch compat-drivers compiles for me against my Ubuntu 3.2
kernel, it still fails on some other kernel versions, with as I see it,
uapi unrelated errors.

Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
compat-drivers: add uapi/dri to WSTABLE

This will let us ensure we can query these files for
stable patch generation purposes.

Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
compat-drivers: remove full drivers from crap

Moving forward no full drivers will be accepted
into crap/. As the alx drivers has proven this only
slows down access to getting users a proper driver.
Restricting the driver to be made available only
through compat-drivers has provided less visibility
and access to the drivers.

The purpose of adding drivers into crap/ over upstream
drivers/staging/ was that some developers may prefer to
not go through the staging development process if they
were sure they could meet the proper upstream quailty
criteria in a timely manner. Practice shows that even
if this is claimed in the end the driver just ends up
bit rotting away in crap/ over a few kernel releases.

Lets stop that. If you want your driver accessible or
automatically backported you have two options:

  * Linux upstream drivers/staging/
  * Linux upstream proper

Choose wisely.

The additional patch directories then remain useful
only for patches content that is already present on
Linux upstream, nothing more.

Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
compat-drivers: remove alx driver from scripts / Makefile

This can be reverted once the driver gets onto Linux upstream.

Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
compat-drivers: remove wil6210 driver from scripts/driver-select

This can be reverted once wil6210 get into Linux upstream.

Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
compat-drivers: add rfkill.h from UAPI path

The rfkill.h header was moved to the UAPI path,
copy it over. But there is one more issue we would
need to address.

The UAPI changes split up the kernel and userspace API
headers into separate directories. We provide backport
support for the new rfkill module to kernels older than
2.6.31. To allow us to dynamically provide only backport
support for those kernels we have a trick within compat
to provide its own include/linux/rfkill.h header which
then will include either your own kernel's rkfill.h or
include the one we are taking from linux-next. The one
we take from linux-next is renamed to rfkill_backport.h.
In order to allow the call to include your own kernel's
rfkill.h the compat rfkill.h uses include_next. The UAPI
changes would mean though that instead of getting your
own kernel's rfkill.h you'd end up getting the UAPI
header file. Fix this by ensuring that for new kernels
we linux_next into the user's kernels rfkill.h and if
the kernel is old we still to the rfkill_backport.h
naming scheme.

Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>