On Tue, Apr 29, 2014 at 03:00:13PM +0800, Qiang Huang wrote:
> Hi Greg,
>
> These are the part 6 commits that I've analyzed from the list of
> upstream commits that have been backported to 3.2 but missing
> from 3.4.
>
> v1 -> v2:
> - Add one commit(23005ee8bad9) which is missed in a former analyze bunch.
> - Add some comments about why [1] and [3] are not needed.
>
> For the 16 commits that I've analyzed,
> - 1 commit is already in 3.4.x, must be the tool's mistake.
> - 1 commit has no stable tag, it's a dependency of several commits adding
> device IDs which we haven't deal with, let's leave it till then. [1]
> - 2 commits have no stable tags, they are bugfixes, and one is dependency
> of the other. [2]
> - 1 commit was marked for stable and can be applied cleanly to 3.4, it is
> only needed for commit 017cecee99d8 ('m68k: Add infrastructure for
> machine-specific random_get_entropy()') which was not cc'd to stable and
> is not on any stable branch, so we'll ignore it. [3]
> - 11 commits were marked for stable but can't be applied cleanly to 3.4.
>
> Please cherry-pick those commits from 3.2.x:
> 71eac9d144be cfg80211: check wdev->netdev in connection work
> 4e9169bee6bc i2c-piix4: Add AMD CZ SMBus device ID
> 51f2a0a803cd b43: ensue that BCMA is "y" when B43 is "y"
That patch didn't apply, I had to do it by hand, please check your
scripts.
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
