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 38BE4C43381 for ; Mon, 25 Feb 2019 09:43:53 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id E29B020989 for ; Mon, 25 Feb 2019 09:43:52 +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="xZem3zZ8" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726475AbfBYJnw (ORCPT ); Mon, 25 Feb 2019 04:43:52 -0500 Received: from mail-wr1-f66.google.com ([209.85.221.66]:36666 "EHLO mail-wr1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726374AbfBYJnw (ORCPT ); Mon, 25 Feb 2019 04:43:52 -0500 Received: by mail-wr1-f66.google.com with SMTP id o17so9116505wrw.3 for ; Mon, 25 Feb 2019 01:43:51 -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=biDph1O5SuxUGQ3uqleYLXOG7APfmGgC7cLQGKcv42k=; b=xZem3zZ8RVtKsWm0VlE1yIROrUb1FmCiQMscIsPytachXEJYaAl6lFJwdded8GbzoC QzAqD6iWlq+QCq6lw3EdKzUkzHIZ+aBh3dFz7wkdPZDGjbIkvdmq0nmNua0J0qhWvC/2 cvYGLQl8Zvyhrj0mc0tA/IvUuw1ZcdhM+HVqP59i5U9rRBmZ+XqfY9CehgsLJYqq1rL+ aUWlwIA6GKqlXw1i45/jQNZrcgkJnbJLPPbO5hYzkxgxlrbzPUSRQCHDsNFi/TWfP6R5 d3ODdPeABdYOV8pm0G1vIHkX9gaWEuOngRtzgGqpTBj5nLHaQNTiNOsQbXHZaJa02m2Y vsMQ== 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=biDph1O5SuxUGQ3uqleYLXOG7APfmGgC7cLQGKcv42k=; b=h1p1ttTuVKKaHpa+v2/EgTrXHwMafXt8fC1q7PB4hcjFbl2xbPej+7nygXLT90HJLU HR7Z4AtCZNoeR+VccBcFt7sKUVInUIiKRmQ6qJ2dAtcTh4PMxkO9cIEwGCCFxvY1/wmm d4Nhujb+nvXWIjjgxIQ3zlifSZQJojAT4/zWrzJtrmhKLWq3P4uxFJTKTPE+Vzu63n6K Wa+QZxNVPUQ2r14sNwcJJsv4ZU0vMJQBsZ4mC/kcEP5WmquRbAWRqWohphjl5m3h6rmW yKg1Aeo22SrAYez2U/YHdSPNbn+Zl6xsezahFym83G0RtQZUU2wWkK9jTzgWwfP9fVO9 00oA== X-Gm-Message-State: AHQUAub8w3etwB40RIJIdYitfGdmPn5gRbYUeF71ecP7/SSRmEu6RXr+ np5ph8ykcRiijOIeVMnnSSYLYw== X-Google-Smtp-Source: AHgI3Ia9lGyXkInWXo2N4h80WXaBXpS3EIsXqrA6/Yx9jDBvILl3B9YLt1lDJz+gnMmSVLfQrh8IQw== X-Received: by 2002:a5d:4804:: with SMTP id l4mr12233478wrq.177.1551087830519; Mon, 25 Feb 2019 01:43:50 -0800 (PST) Received: from Red ([2a01:cb1d:147:7200:2e56:dcff:fed2:c6d6]) by smtp.googlemail.com with ESMTPSA id d206sm14738723wmc.11.2019.02.25.01.43.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 25 Feb 2019 01:43:49 -0800 (PST) Date: Mon, 25 Feb 2019 10:43:47 +0100 From: LABBE Corentin To: gregkh@linuxfoundation.org Cc: Eugeniy.Paltsev@synopsys.com, vgupta@synopsys.com, stable@vger.kernel.org Subject: Re: WTF: patch "[PATCH] ARC: enable uboot support unconditionally" was seriously submitted to be applied to the 4.20-stable tree? Message-ID: <20190225094347.GA3831@Red> References: <155101646812133@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <155101646812133@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 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. Why this patch is not a real stable patch, it is a strong requirement for testing all future stable release on kernelCI. 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) Regards