From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 75A64C3A5A3 for ; Thu, 22 Aug 2019 23:38:50 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 416AB21848 for ; Thu, 22 Aug 2019 23:38:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1566517130; bh=ITNFY1BlYLCzTwOHLm2S2nQdiT2eZatinPQGLa5g+Sw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=mgHwWlnRVrV3jACOwoWqs6r5jwC2XNPSWPjEMQKgGnuHSOgBSc2mMbpkH70gN5thN 2q+YYXZrdsIFh9rIgkE4IH9cdUKMQhI2oER+wOviyC/Rc6axz2N7jAY8wxl4WtHoAC Xv1TkTlWNES4YSyWoRbsK90m86Q3rYvOFocqVNII= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727070AbfHVXit (ORCPT ); Thu, 22 Aug 2019 19:38:49 -0400 Received: from mail.kernel.org ([198.145.29.99]:44034 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725283AbfHVXis (ORCPT ); Thu, 22 Aug 2019 19:38:48 -0400 Received: from localhost (wsip-184-188-36-2.sd.sd.cox.net [184.188.36.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id A188621848; Thu, 22 Aug 2019 23:38:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1566517127; bh=ITNFY1BlYLCzTwOHLm2S2nQdiT2eZatinPQGLa5g+Sw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=O0o7UwKYKklXR/jKKK0FAlAwfnUpzLvehLMMLFfLLhKiv9tlkog2vCr8BVDG9AY3K ibp/4boiS0DOZCvXnMHaXiem5fmlp9v9kxBxJPAE0RSVXH7MJD0aLkhiNAjJezCrk7 ptGqxAKN++IjZoLFkDAHUTiJyPW+8tN/ECHUYqjQ= Date: Thu, 22 Aug 2019 16:38:47 -0700 From: Greg KH To: Stefan Lippers-Hollmann Cc: Sasha Levin , linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: [PATCH 5.2 000/135] 5.2.10-stable review Message-ID: <20190822233847.GB24034@kroah.com> References: <20190822170811.13303-1-sashal@kernel.org> <20190822172619.GA22458@kroah.com> <20190823000527.0ea91c6b@mir> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190823000527.0ea91c6b@mir> User-Agent: Mutt/1.12.1 (2019-06-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Aug 23, 2019 at 12:05:27AM +0200, Stefan Lippers-Hollmann wrote: > Hi > > On 2019-08-22, Greg KH wrote: > > On Thu, Aug 22, 2019 at 01:05:56PM -0400, Sasha Levin wrote: > > > > > > This is the start of the stable review cycle for the 5.2.10 release. > [...] > > > The whole patch series can be found in one patch at: > > > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-5.2.10-rc1.gz > ^v5.x > [...] > > If anyone notices anything that we messed up, please let us know. > > It might be down to kernel.org mirroring, but the patch file doesn't > seem to be available yet (404), both in the wrong location listed > above - and the expected one under > > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.2.10-rc1.gz > or > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.2.10-rc1.xz > > The v4.x based patches can be found just fine: > > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.4.190-rc1.gz > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.9.190-rc1.gz > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.140-rc1.gz > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.68-rc1.gz Ah, no, it's not a mirroring problem, Sasha and I didn't know if anyone was actually using the patch files anymore, so it was simpler to do a release without them to see what happens. :) Do you rely on these, or can you use the -rc git tree or the quilt series? If you do rely on them, we will work to fix this, it just involves some scripting that we didn't get done this morning. thanks, greg k-h