Hi On 2015-05-02, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.0.2 release. > There are 220 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Mon May 4 18:58:12 UTC 2015. > Anything received after that time might be too late. > > The whole patch series can be found in one patch at: > kernel.org/pub/linux/kernel/v4.0/stable-review/patch-4.0.2-rc1.gz [...] This file doesn't exist(404). While I'm aware that the mirroring probably hasn't caught up yet, the URL seems to have multiple issues besides just that. http://kernel.org/pub/linux/kernel/v4.0/ doesn't exist, there doesn't appear to be a symlink from v4.x to v4.0 (imho for good reasons), while such a smylink did exist for v3.x --> v3.0. So fixing the obvious problem and adapting the URL to http://kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.0.2-rc1.gz doesn't work either, as there is no "stable-review" directory under http://kernel.org/pub/linux/kernel/v4.x/ yet (which probably should be created). Your previous, "[PATCH 4.0 0/7] 4.0.1-stable review"[1], mail referenced kernel.org/pub/linux/kernel/v3.0/stable-review/patch-4.0.1-rc1.gz which does exist. However patch-4.0.2-rc1.gz is still missing there or at the more sensible location at http://kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.0.2-rc1.gz Given that the patch files of the other stable-review patches posted today are already available[2], I assume that it's not just a problem with the mirroring. Regards Stefan Lippers-Hollmann [1] http://lkml.kernel.org/r/<20150426120018.032351371@xxxxxxxxxxxxxxxxxxx> [2] https://www.kernel.org/pub/linux/kernel/v3.0/stable-review/patch-3.10.77-rc1.gz https://www.kernel.org/pub/linux/kernel/v3.0/stable-review/patch-3.14.41-rc1.gz https://www.kernel.org/pub/linux/kernel/v3.0/stable-review/patch-3.19.7-rc1.gz -- 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