net: rmnet_usb: don't access unet after freeing

When mux is enabled, unet is accessed after freeing it in
rmnet_usb_disconnect(). Fix it by caching the variables that
are required to retrieve unet from unet_list array before
freeing the unet.

CRs-Fixed: 562671
Change-Id: Id21a99db6b3f5da05e89e17f04c01202ea996d06
Signed-off-by: Pavankumar Kondeti <pkondeti@codeaurora.org>
USB: gadget: u_ctrl_hsic: fix a bug in control bits propagation

A work is scheduled to open the hsic transport channel upon
USB cable connect.  If the host sends SET_CONTROL_LINE_STATE
control transfer before the port is opened, the control bits
are not propagated to the mdm.

CRs-Fixed: 556039
Change-Id: Ic60830d2b04327c9ea9ded84e66b8eb7b92aee82
Signed-off-by: Pavankumar Kondeti <pkondeti@codeaurora.org>
Merge "net: rmnet_usb: don't access unet after freeing"
Merge "USB: gadget: u_ctrl_hsic: fix a bug in control bits propagation"
msm: cpufreq: Unable to handle kernel NULL pointer

In the function cpufreq_governor_dbs,( case CPUFREQ_GOV_START )
sysfs creation is under the critical section where as
(case CPUFREQ_GOV_STOP) sysfs removal is not under critical section.
If a START/STOP done frequently from user space then there is chance
of hitting the race condition with sysfs interface creation and removal.
Hence the removal of sysfs entry should happen in the criticalpath.

Change-Id: I3b0dd475e8e306b633b282ff23bd1c8195b5f45f
CRs-fixed: 564850
Signed-off-by: Swetha Chikkaboraiah <schikk@codeaurora.org>
Merge "msm: cpufreq: Unable to handle kernel NULL pointer"