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=-7.3 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=unavailable 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 E9328C3A5A4 for ; Fri, 23 Aug 2019 17:36:30 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id BEC7E2173E for ; Fri, 23 Aug 2019 17:36:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1566581790; bh=I+q0DDKZZ2CbEjDpmYe9VqaMEDkMv33qzg1hGIO7uoQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=JMhF2tQosOwZjsQ8QLpg1OynNmHGv7bESIJVHQ5kM2Dl1F2H27oudHc4e3qZZoBDX ahTa5JElomKNovnj2hJ3xmRkUuRs/5q/U0eNraKYbVgDnUR7PXC8y+Mu9JPUXprUH/ R7DI/45wQ93YPNQKdKC8z8/x0FAqAVYiWhZr+Ayo= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2404105AbfHWRg3 (ORCPT ); Fri, 23 Aug 2019 13:36:29 -0400 Received: from mail.kernel.org ([198.145.29.99]:39496 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2390003AbfHWRg3 (ORCPT ); Fri, 23 Aug 2019 13:36:29 -0400 Received: from localhost (unknown [104.129.198.240]) (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 F14E82133F; Fri, 23 Aug 2019 17:36:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1566581788; bh=I+q0DDKZZ2CbEjDpmYe9VqaMEDkMv33qzg1hGIO7uoQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=fhOXlTCjlQ7esRMzA0VNFm6JOFIuomOFvQQqBrg2XAWSN1GHC1WXj4IgMXYFqMswp WqjM3iTXmeGgvwrF5pNlZqFA319qckAkAvF5QkpVJauQ/HtKXbR5/FbBkYJZ6zI/Qk ZfkOE0wX5O5ry4x62TQsqt4cZBZu8PnXtDfTOQkk= Date: Fri, 23 Aug 2019 10:36:27 -0700 From: Greg KH To: Sasha Levin Cc: Stefan Lippers-Hollmann , linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: [PATCH 5.2 000/135] 5.2.10-stable review Message-ID: <20190823173627.GA1040@kroah.com> References: <20190822170811.13303-1-sashal@kernel.org> <20190822172619.GA22458@kroah.com> <20190823000527.0ea91c6b@mir> <20190822233847.GB24034@kroah.com> <20190823024248.11e2dac3@mir> <20190823062853.GC1581@sasha-vm> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190823062853.GC1581@sasha-vm> 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 02:28:53AM -0400, Sasha Levin wrote: > On Fri, Aug 23, 2019 at 02:42:48AM +0200, Stefan Lippers-Hollmann wrote: > > Hi > > > > On 2019-08-22, Greg KH wrote: > > > On Fri, Aug 23, 2019 at 12:05:27AM +0200, Stefan Lippers-Hollmann wrote: > > > > On 2019-08-22, Greg KH wrote: > > > > > On Thu, Aug 22, 2019 at 01:05:56PM -0400, Sasha Levin wrote: > > [...] > > > > 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 > > [...] > > > 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. > > > > "Rely" is a strong word, I can adapt if they're going away, but > > I've been using them so far, as in (slightly simplified): > > > > $ cd patches/upstream/ > > $ wget https://cdn.kernel.org/pub/linux/kernel/v5.x/patch-5.2.9.xz > > $ xz -d patch-5.2.9.xz > > $ wget https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.2.10-rc1.gz > > $ gunzip patch-5.2.10-rc1.gz > > $ vim ../series > > $ quilt ... > > > > I can switch to importing the quilt queue with some sed magic (and I > > already do that, if interesting or just a larger amounts of patches are > > queuing up for more than a day or two), but using the -rc patches has > > been convenient in that semi-manual workflow, also to make sure to really > > get and test the formal -rc patch, rather than something inbetween. > > An easy way to generate a patch is to just use the git.kernel.org web > interface. A patch for 5.2.10-rc1 would be: > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/patch/?id=linux-5.2.y&id2=v5.2.9 > > Personally this patch upload story sounded to me like a pre-git era > artifact... Given that we no longer do patches for Linus's -rc releases for the past few years, maybe it is time to move to do the same for the stable releases to be consistent. thanks, greg k-h