Hi Greg,
We've started to analize the list of upstream commits that have been
backported to 3.2 but missing from 3.4.
For the 16 commits that I've analized,
- 2 commits have been backported to 3.4. The script failed to detect them.
- 1 commits have no stable tag, it's prepare for another bug fix patch.(*)
- 3 commits were marked for stable but can't be applied cleanly to 3.4.
- other 10 commits were marked for stable, and were a fix pacthset:
- 8 commit were marked for stable and can be applied cleanly and the fix
is obviously correct.
- 1 commits were marked for stable but can't be applied cleanly to 3.4,
and 3.2 misses it. I'll send out the backport later.
- 1 commits of the patchset only affect 3.7+, so just drop it like 3.2.
Please cherry-pick those commits from 3.2.x:
a27e05b0cf32 sunrpc: clarify comments on rpc_make_runnable
f7b72b71fe00 SUNRPC: Prevent an rpc_task wakeup race
0f260fd5c5b7 ASoC: imx-ssi: Fix occasional AC97 reset failure
95d909e86710 ASoC: sglt5000: Fix the default value of CHIP_SSS_CTRL
53fcffc423f4 ALSA: atiixp: Fix unlocked snd_pcm_stop() call
28518ed66242 ALSA: 6fire: Fix unlocked snd_pcm_stop() call
a4d0e7c132a9 ALSA: ua101: Fix unlocked snd_pcm_stop() call
e93a7f00a3db ALSA: usx2y: Fix unlocked snd_pcm_stop() call
272f254b2719 ALSA: pxa2xx: Fix unlocked snd_pcm_stop() call
8ac7e3f3ac40 ASoC: s6000: Fix unlocked snd_pcm_stop() call
4bcfe68e7e4d staging: line6: Fix unlocked snd_pcm_stop() call
cherry-pick those commits from mainline:
60478295d687 ALSA: asihpi: Fix unlocked snd_pcm_stop() call
(*) The commit is a27e05b0cf32 (sunrpc: clarify comments on rpc_make_runnable),
prepare for f7b72b71fe00 (SUNRPC: Prevent an rpc_task wakeup race).
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html