msm_bam_rmnet: Fix potential memory corruption

Usage of legacy string manipulation function sprintf could lead to
memory corruption as the number of bytes to be written to the
destination is not bounded. Replace sprintf with snprintf where the
number of bytes to be written is explicitly specified.

CRs-fixed: 672202
Change-Id: Iab7516ad0e2540eb619fe96e26a3516c7adf86cc
Signed-off-by: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>
Merge "msm_bam_rmnet: Fix potential memory corruption"
power: qpnp-charger: update battery status when boost enabled

Battery status is not updated correctly when boost enabled with charger
connected and battery charged to full. Add some logic in the boost
enable/disable hook function to update the battery status.

CRs-Fixed 688311
Change-Id: I07f7f6c11e206533d30470e78eef246dc15cf871
Signed-off-by: Chunmei Cai <ccai@codeaurora.org>
Merge "power: qpnp-charger: update battery status when boost enabled"
msm: vidc: handle dynamic buffers in pendingq during flush

In dynamic buffer mode, if flush was received before
stream-on, driver would have incremented the ref count
for output buffers, but not yet sent to firmware. So,
after flush done, there would be no fbd from firmware
and the reference to these buffers would not be removed.
So when the buffers are dequeued, driver fails to
unmap and free the output buffers.
Subsequently, after flush done, when client queues
the same output buffers again to driver, the ref
count is increased and becomes 2. This results in
the driver holding the buffers with itself, thereby
entering in to a deadlock situation and starving the
firmware of output buffers. This results in a video
freeze.

Change-Id: I0c3d13124bd48b900e56e14666eaed2f0e7ee9d6
Signed-off-by: Arun Menon <avmenon@codeaurora.org>
Merge "msm: vidc: handle dynamic buffers in pendingq during flush"
Merge d573930c11d41223ee70f1d3766e402472e2c7bc on remote branch

Change-Id: I2277e72fdd459210a9315efacf2bea21868c79d6