wifi: remove local nl80211 header

* Sync with omapzoom d-jb-mr2.1-release

Change-Id: I89cb2c3bdf667f38ff4c94c164cdfb3d750478e2
Revert "libhardware_legacy: Add support for oneshot WiFi setup"

This reverts commit 2736b9e876fbb552a297c6497591ac0eec2c898b.

Change-Id: I95c35b3c47b127be996f4503747f3a5f90c787ae
Fix merge error

Change-Id: I5d59321e84c165128092174076f90b937d3621d1
uevent: Allow multiple uevent listeners from the same process

The netlink socket created by uevent_init sets the nl_pid to the
current PID. nl_pid must be unique per-process, however it does not
have to do with the PID. From the documentation:

"
For a user-space process, nl_pid
is usually the PID of the process owning the destination socket.
However, nl_pid identifies a netlink socket, not a process.  If a
process owns several netlink sockets, then nl_pid can be equal to the
process ID only for at most one socket.
"

In use cases where a single process calls uevent_init more than one
time, the second one will always fail. This patch sets the nl_pid
to 0, which lets the kernel pick its own unique identifier as per the
documentation:

"
If the application sets it to 0, the kernel takes
care of assigning it.  The kernel assigns the process ID to the first
netlink socket the process opens and assigns a unique nl_pid to every
netlink socket that the process subsequently creates.
"

The behavior stays the same for the first socket but will also succeed
in subsequent calls.

Change-Id: I6fa74adc9d5835ff39b86187799998111fc12001

Conflicts:
	uevent/uevent.c
policy: Offload enhancements

 * Port changes from audio-caf to the generic HAL to bring
   support for these features to more devices.

Change-Id: I74ff10dd7574498654d4771a74285e0875dd8580