Hi Ben,
Thanks for the review.
On 2014/4/27 7:12, Ben Hutchings wrote:
> On Wed, 2014-04-23 at 11:44 +0800, Qiang Huang wrote:
>> Hi Greg,
>>
>> We've started to analyze the list of upstream commits that have been
>> backported to 3.2 but missing from 3.4.
>>
>> For the 15 commits that I've analyzed,
>> - 1 commit is already in 3.4.x, must be the tool's mistake.
>> - 2 commits have no stable tags, they are not bugfixes, and I didn't
>> find any patches which relied on them. [1]
>> - 1 commit was marked for stable and can be applied cleanly to 3.4, but
>> I see it fix no bug and didn't find any patches relied on it, so I
>> think we should ignore it. [2]
> [...]
>> [1] the patches from 3.2.x
>> 3eddd6c470e2 net: Add net_ratelimited_function and net_<level>_ratelimited macros
>
> This is a dependency of commit 9ecd1a75d977 ('xen-netfront: reduce
> gso_max_size to account for max TCP header').
You are right, we analyzed this patch in this bunch:
http://thread.gmane.org/gmane.linux.kernel.stable/81797
But it is chosen not to backport, after some review, I think we
should both backport these two patches. I'll resend this out soon.
>
>> 56f1f4bb5770 PCI: Define macro for Marvell vendor ID
>
> This is a dependency of several commits adding device IDs to ahci.
Yes, I checked these commits,
9ed46e8a9a81cb ahci: add Marvell 9230 to the AHCI PCI device list
this is already in 3.4.x, without the macro to identify the ID.
Others are all merged in 3.2.x after 3.2.54, which is beyond out
list, we'll deal with them in out next analyze round.
I'll add some comments in my next post, thanks.
>
>> [2] the patch form 3.2.x
>> ee698d67a4af random: allow architectures to optionally define random_get_entropy()
>
> True, this 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.
>
> Ben.
>
--
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