ts27010mux_uart: Fix GCC 4.7 compilation error

Change-Id: I0c6e885298a514837969703bf165df17efab1f20
compat-wireless: Remove generated files and add them to the gitignore

Conflicts:
	drivers/net/wireless/compat-wireless_R5.SP2.03/Module.symvers
	drivers/net/wireless/compat-wireless_R5.SP2.03/include/linux/compat_autoconf.h

Conflicts:
	drivers/net/wireless/compat-wireless_R5.SP2.03/include/linux/compat_autoconf.h
Add permission checking for binder IPC.

Change-Id: I3a7b3ce9fba888a031d1e73823d10c5326cc4020
Signed-off-by: Ed Tam <etam@google.com>
Fix security_binder_transfer_binder hook.

Drop the owning task argument to security_binder_transfer_binder
since ref->node->proc can be NULL (dead owner?).
Revise the SELinux checking to apply a single transfer check between
the source and destination tasks.  Owning task is no longer relevant.
Drop the receive permission definition as it is no longer used.

This makes the transfer permission similar to the call permission; it is only
useful if you want to allow a binder IPC between two tasks (call permission)
but deny passing of binder references between them (transfer permission).

Change-Id: Ic8710c82f5b275c3f006176f4e5aec3d6e38d559
Signed-off-by: Ed Tam <etam@google.com>
Enable setting security contexts on rootfs inodes.

rootfs (ramfs) can support setting of security contexts
by userspace due to the vfs fallback behavior of calling
the security module to set the in-core inode state
for security.* attributes when the filesystem does not
provide an xattr handler.  No xattr handler required
as the inodes are pinned in memory and have no backing
store.

This is useful in allowing early userspace to label individual
files within a rootfs while still providing a policy-defined
default via genfs.

Change-Id: I95d287398508aacb706544bdbfa58c104a8fe5df
Signed-off-by: Stephen Smalley <sds@tycho.nsa.gov>