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.5 required=3.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, USER_AGENT_MUTT autolearn=ham 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 E8A9AC43381 for ; Mon, 25 Feb 2019 14:20:14 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 93156213A2 for ; Mon, 25 Feb 2019 14:20:08 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=baylibre-com.20150623.gappssmtp.com header.i=@baylibre-com.20150623.gappssmtp.com header.b="oW18Z4Cz" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726795AbfBYOUD (ORCPT ); Mon, 25 Feb 2019 09:20:03 -0500 Received: from mail-wr1-f65.google.com ([209.85.221.65]:36001 "EHLO mail-wr1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726099AbfBYOUD (ORCPT ); Mon, 25 Feb 2019 09:20:03 -0500 Received: by mail-wr1-f65.google.com with SMTP id o17so10143524wrw.3 for ; Mon, 25 Feb 2019 06:20:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=3yoaKsQXKinDzNNUZUrWt0YBagLbeTAkKL2S54zvMHk=; b=oW18Z4CzXZ2vSX6AZoi8ce5pse7mztx/CosySagiJ1WXcIqsIX6SmeBzYBiL4hQ+Q2 KyLbNkbVqzE1/9xtn2NSO/bvVCLLIw4izF+PaDKw6q60/LokZNvDKKbmLUsOxH8El9GL w+UItiESLIUpuTc0a2KqKgmEmfJROh8kmVt++CxscTKIOc43uu98Q1jlmr0JvFf0LIB0 zpaqJrcDKkQ6+/06foTO+q61nWhjTH1c6UeoWQAh4NJfkEWqmwzDQNaVJCSY0L/dxRFV eFfphyDybUogXtfQDXCEtlxmxIiF7RpKENu6dKyKk6fr0blRpffhPU6t73c3jIAU09l+ HzqA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=3yoaKsQXKinDzNNUZUrWt0YBagLbeTAkKL2S54zvMHk=; b=CpGg/lHrqiYzHroBAN9j0s64ame6hPTY+kkqohptaYSphW6rIZT0vnNGH0+9Ti9fjT r8sFcBhmaUr4uhEOVZAwU4kOwQdvu9Pqk5sbzPtEb/O7P2FSnS1agl7ElyJMhlSmYWOs 4PnB4EudisTdrx3t4pPmscdB1QCwKZp4aX9S0R2ACJJrQ65wZ99LH3pb55kvoqw7UEfp 4lTzoBmxgftxx8ZUTUtk8dzrTPDhaiwsfhshKwP0vizFGWhLqQuFsf3XyV7ohCXHstQB J+e/1e4CDou7X/wH0fta/0EX0rqc/gdryyyRpmoEKgkWAHTK7le8YcWqN3ttHrthCqaP ar5w== X-Gm-Message-State: AHQUAubZH8nP6DySAbD8NE28M1b88XnWQM2NDTvjj4FyZnM/S2OqqXxE TCj11JSFrDf6UD09VQRlc7K4glVHFhtn1w== X-Google-Smtp-Source: AHgI3IaVpeq0nPSa+HnVpuVnuaIDBBhirtSRhRuCd71QHxLXB99mSZjfuJ07T/1yO4DOgn48xr67ow== X-Received: by 2002:adf:e80c:: with SMTP id o12mr12219061wrm.114.1551104401809; Mon, 25 Feb 2019 06:20:01 -0800 (PST) Received: from Red ([2a01:cb1d:147:7200:2e56:dcff:fed2:c6d6]) by smtp.googlemail.com with ESMTPSA id x17sm12316726wrd.95.2019.02.25.06.20.00 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 25 Feb 2019 06:20:01 -0800 (PST) Date: Mon, 25 Feb 2019 15:19:58 +0100 From: LABBE Corentin To: Greg KH Cc: Eugeniy.Paltsev@synopsys.com, vgupta@synopsys.com, stable@vger.kernel.org, khilman@baylibre.com Subject: Re: WTF: patch "[PATCH] ARC: enable uboot support unconditionally" was seriously submitted to be applied to the 4.20-stable tree? Message-ID: <20190225141958.GB11694@Red> References: <155101646812133@kroah.com> <20190225094347.GA3831@Red> <20190225135400.GA27690@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190225135400.GA27690@kroah.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Mon, Feb 25, 2019 at 02:54:00PM +0100, Greg KH wrote: > On Mon, Feb 25, 2019 at 10:43:47AM +0100, LABBE Corentin wrote: > > On Sun, Feb 24, 2019 at 02:54:28PM +0100, gregkh@linuxfoundation.org wrote: > > > The patch below was submitted to be applied to the 4.20-stable tree. > > > > > > I fail to see how this patch meets the stable kernel rules as found at > > > Documentation/process/stable-kernel-rules.rst. > > > > > > I could be totally wrong, and if so, please respond to > > > and let me know why this patch should be > > > applied. Otherwise, it is now dropped from my patch queues, never to be > > > seen again. > > > > > > thanks, > > > > > > greg k-h > > > > > > > Hello > > > > Without this patch, we cannot boot a defconfig on ARC, and this is > > critical for testing ARC devices in kernelCI. > > But this means you have never been able to boot a defconfig on ARC, > right? So this is a new "feature" you are adding :) No I was able to boot them, but by adding CONFIG_ARC_UBOOT_SUPPORT. This patch remove the assertion that ARC devices will be booted by default for debugging purpose. > > If you wait one more week, all is good, you can do this for 5.0, and > when I drop 4.20 in another few weeks, all is fine. > > > Why this patch is not a real stable patch, it is a strong requirement > > for testing all future stable release on kernelCI. > > Only for 4.20. > > And normally kernelci uses a specific configuration for the board it is > testing, not defconfig. Or am I mistaken? No, kernelci only build defconfig without touching them. > > This is a fine patch to have upstream, it just really doesn't fit the > stable rules. > > > Note that another patch (touching defconfig) for booting defconfig is > > still missing and need to be also added to stable. (I will resend it > > today) > > Again, looks like a new feature. Just wait a week and all will be fine > for you :) >