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=-5.9 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED 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 521A1C35647 for ; Fri, 21 Feb 2020 11:18:03 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 271A1207FD for ; Fri, 21 Feb 2020 11:18:03 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="Yapkteku" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727063AbgBULR6 (ORCPT ); Fri, 21 Feb 2020 06:17:58 -0500 Received: from mail-lf1-f65.google.com ([209.85.167.65]:42178 "EHLO mail-lf1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726268AbgBULR6 (ORCPT ); Fri, 21 Feb 2020 06:17:58 -0500 Received: by mail-lf1-f65.google.com with SMTP id 83so1207598lfh.9 for ; Fri, 21 Feb 2020 03:17:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Gim0LahUou+1GhT0i2NTsUJucCc3gqJedRUqf5uOSGY=; b=YapktekuYDYpX1KTSNJAZ2QZReOKHtBO1DePweQSweEsAq1UHVUy1RypFJE81btbve ZJILpa8pMOwj3RPbn7ykJKganH0aQQ2ar63kA5mcgWPSCvb9P6piCgYUIr5o1QBWn+ZX RbZeed8wn7fwIu/Em8IJ21LS/NE2kiarmk7xDyHwdMUtwhDcbPag5gQjxjeBZ/4pUBim MCJmins9PcZqcjkg6H1DP64Hw+I8GKLMWlKwlat7dz0Zr8k7SLT70L/gbOWLw4veNqmm i460+mvR8VJ0/a0iNGzsI9QQ2uGlpu1AIF48iIyex/Tx3kSoTCOfykalbc+T7PAHfiDx DJzQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Gim0LahUou+1GhT0i2NTsUJucCc3gqJedRUqf5uOSGY=; b=aT5n1vkSyWB3TJKNPEJ5Waar/MN5neBz4uhVu0he+DQUuPkD3fHKPwkixB+X+5gVTW eV9E3G4uCp4+9UUG4ocjRWDnu9m3q1TZq3W7SLYBJWoPE80LcymveaoBj1nX1/5ELQe+ X19Qsg+mNHMKd/tel2RsCuw8jpEbYrslgwZ5cWBx1PvL2xP3FUeoRcXgkqxqohu/uy9t Y6nyCf53lj/a4ATB9uYHWovAq07HLcrAQP/2tS1KXt9JTkagqXMufJAkL+hxJik8pp/0 fByQAs4Y07bQrjM/DOCyXAZgNYPbiiLG9ngJnk8KeQc7P1MevyobBdJa13JQ9prA3yCc XEbQ== X-Gm-Message-State: APjAAAUYJt6HROuSxP2RdOcCZ/xARhjiuee6zwNCWRAxtkNBJnqYoJ82 hLwXyrHSxBp/NK6hNWN7BKKT5aCuKUnkdojmThwA/A== X-Google-Smtp-Source: APXvYqwBQiV+KkA20U9up3VHyUSJOdigNHkwyzQDqlAHqaQHklI/NeQBKdnFSBD4r3qgBx1CeYRW6gAVDCwxU/N2S0Q= X-Received: by 2002:ac2:4199:: with SMTP id z25mr19750795lfh.26.1582283876489; Fri, 21 Feb 2020 03:17:56 -0800 (PST) MIME-Version: 1.0 References: <20200221072349.335551332@linuxfoundation.org> <529a5a4a-974e-995a-9556-c2a14d09bb5d@nvidia.com> In-Reply-To: <529a5a4a-974e-995a-9556-c2a14d09bb5d@nvidia.com> From: Naresh Kamboju Date: Fri, 21 Feb 2020 16:47:45 +0530 Message-ID: Subject: Re: [PATCH 5.4 000/344] 5.4.22-stable review To: Greg Kroah-Hartman , t-kristo@ti.com Cc: open list , Linus Torvalds , Andrew Morton , Guenter Roeck , Shuah Khan , patches@kernelci.org, Ben Hutchings , lkft-triage@lists.linaro.org, linux- stable , linux-tegra , Arnd Bergmann , Jon Hunter Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 21 Feb 2020 at 15:34, Jon Hunter wrote: > > > On 21/02/2020 07:36, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 5.4.22 release. > > There are 344 patches in this series, all will be posted as a response > > to this one. If anyone has any issues with these being applied, please > > let me know. > > > > Responses should be made by Sun, 23 Feb 2020 07:19:49 +0000. > > Anything received after that time might be too late. > > > > The whole patch series can be found in one patch at: > > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.4.22-rc1.gz > > or in the git tree and branch at: > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.4.y > > and the diffstat can be found below. > > > > thanks, > > > > greg k-h > > > > ------------- > > Pseudo-Shortlog of commits: > > ... > > > Tero Kristo > > ARM: OMAP2+: pdata-quirks: add PRM data for reset support > > > The above commit is generating the following build error on ARM systems ... > > dvs/git/dirty/git-master_l4t-upstream/kernel/arch/arm/mach-omap2/pdata-quirks.c:27:10: fatal error: linux/platform_data/ti-prm.h: No such file or directory > #include > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ build error: ../arch/arm/mach-omap2/pdata-quirks.c:27:10: fatal error: linux/platform_data/ti-prm.h: No such file or directory 27 | #include | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. make[2]: *** [../scripts/Makefile.build:265: arch/arm/mach-omap2/pdata-quirks.o] Error 1 With these below three patches, it applies cleanly and builds. But I'm not sure these are not expected to get into stable rc 5.4 branch. 3e99cb214f03 ("soc: ti: add initial PRM driver with reset control support") c5117a78dd88 ("soc: ti: omap-prm: poll for reset complete during de-assert") d30cd83f6853 ("soc: ti: omap-prm: add support for denying idle for reset clockdomain") However, it's only patch d30cd83f6853 ("soc: ti: omap-prm: add support for denying idle for reset clockdomain") that introduces file linux/platform_data/ti-prm.h -- Linaro LKFT https://lkft.linaro.org