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=-10.3 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED, 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 EE39BC32750 for ; Fri, 2 Aug 2019 07:40:59 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id C3F7B2086A for ; Fri, 2 Aug 2019 07:40:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1564731659; bh=WdW+h+XGuGqjKwJ5w5plqYCPLFR0EQgahxkRPqpuyZY=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=qv2GhvHovRMioVv1aQmUFVrRNNL+4hWITNpADf546wo6aJp9I82a0W6c7LOd2Tq8M deNOsv+wTZcr3JYXaiQhOQAxmXK94cqzR4ky9YeEyCorUH2Q/8KsVbYJhemsoLzJ2H EQnPO2OTJX/neayhwQ0JOfGqvtSlkTtoPH+VOX/o= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389943AbfHBHk6 (ORCPT ); Fri, 2 Aug 2019 03:40:58 -0400 Received: from mail.kernel.org ([198.145.29.99]:43706 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732277AbfHBHk4 (ORCPT ); Fri, 2 Aug 2019 03:40:56 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (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 6C0212086A; Fri, 2 Aug 2019 07:40:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1564731655; bh=WdW+h+XGuGqjKwJ5w5plqYCPLFR0EQgahxkRPqpuyZY=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=H3r9ZsyblPP9d/UZ24Yu885Myc5WLnctX0R5hAz3sA4P2qsYWNaLqtNNDvL7rE/cX SlD0BLzdzuDTPKncegj4CagRPWVSdfRKwIT95NaaqCu4gk5ahbYghF9vzCrh47n3aD EIVAeCNF4jloZPOWQMsi9AJpG8pR/gbNRYUudNWs= Date: Fri, 2 Aug 2019 09:40:53 +0200 From: Greg Kroah-Hartman To: Alexey Brodkin Cc: linux-stable , "linux-kernel@vger.kernel.org" , Corentin Labbe , "khilman@baylibre.com" , "linux-snps-arc@lists.infradead.org" , Eugeniy Paltsev , Vineet Gupta Subject: Re: [PATCH v2 2/2] ARC: enable uboot support unconditionally Message-ID: <20190802074053.GE26174@kroah.com> References: <20190214150745.18773-1-Eugeniy.Paltsev@synopsys.com> <20190214150745.18773-3-Eugeniy.Paltsev@synopsys.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 Thu, Jul 18, 2019 at 08:51:23PM +0000, Alexey Brodkin wrote: > Hi Greg, > > > -----Original Message----- > > From: Eugeniy Paltsev > > Sent: Thursday, February 14, 2019 6:08 PM > > To: linux-snps-arc@lists.infradead.org; Vineet Gupta > > Cc: linux-kernel@vger.kernel.org; Alexey Brodkin ; Corentin Labbe > > ; khilman@baylibre.com; Eugeniy Paltsev > > Subject: [PATCH v2 2/2] ARC: enable uboot support unconditionally > > > > After reworking U-boot args handling code and adding paranoid > > arguments check we can eliminate CONFIG_ARC_UBOOT_SUPPORT and > > enable uboot support unconditionally. > > > > For JTAG case we can assume that core registers will come up > > reset value of 0 or in worst case we rely on user passing > > '-on=clear_regs' to Metaware debugger. > > > > Signed-off-by: Eugeniy Paltsev > > May we have this one back-ported to linux-4.19.y? > > It was initially applied to Linus' tree during 5.0 development > cycle [1] but was never back-ported. > > Now w/o that patch in KernelCI we see boot failure on ARC HSDK > board [2] as opposed to normally working later kernel versions. > > [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=493a2f812446e92bcb1e69a77381b4d39808d730 > [2] https://storage.kernelci.org/stable/linux-4.19.y/v4.19.59/arc/hsdk_defconfig/gcc-8/lab-baylibre/boot-hsdk.txt > > Below is that same patch but rebased on linux-4.19 as in its pristine > form it won't apply due to offset of one of hunks. Why is this patch ok for stable kernel trees? Are you not removing existing support in 4.19 for a feature that people might be using there? What bug is this fixing that requires this removal? thanks, greg k-h