On 05/21/2014 11:30 AM, Christian König wrote: > Am 21.05.2014 11:26, schrieb Jiri Slaby: >> On 05/21/2014 11:12 AM, Christian König wrote: >>> Hi Greg, >>> >>> something went wrong here. The patch doesn't apply to your 3.14-stable >>> tree because it's already part of 3.14 since rc4. >> Hi, >> >> not really: >> $ git log v3.14..v3.15-rc1|grep 1c61eae469e0d1d2fb9d7b77f51ca50c1f8f3ce9 >> commit 1c61eae469e0d1d2fb9d7b77f51ca50c1f8f3ce9 >> >> It's only in 3.15-rc1... > > The commit 1c61eae469e0d1d2fb9d7b77f51ca50c1f8f3ce9 is only in 3.15-rc1 > because the hash of the upstream commit in 3.14-rc4 is > 8f53492f86f9ca66bc762be98f0a9fce9bcb319a. > > It's just that the hashes are different, but the patches are identical. Now it makes sense. thanks, -- js suse labs -- 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