Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp1194884pxb; Fri, 21 Jan 2022 12:00:10 -0800 (PST) X-Google-Smtp-Source: ABdhPJxtY6CJ7H13rocMq0ownFTP5UhA1paTHSDIRaGmHEyRp4pTwBeQFJ6UVtF59xbWt7iK9BVZ X-Received: by 2002:a17:902:dac3:b0:14b:1edb:b1c9 with SMTP id q3-20020a170902dac300b0014b1edbb1c9mr4196881plx.113.1642795210021; Fri, 21 Jan 2022 12:00:10 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1642795210; cv=none; d=google.com; s=arc-20160816; b=tz6hueehZ2br40iB7pJJZ9MITRplttI1mm+7vrrOEWhcGZRQOape1SfdELACFMF60t 5ssA7FCynt9/OZ6UJW06XEnrEIYLRPF+ZfKmt9OgK0q8oST21wjwTytdsMitymzr/mDS Ohp6PVz/TmCUSBD8PmKZVvqKnmGWFAIlIacjKPdjm406zw7d4cRKU8ZVAtYmD3domKtA yT6IHKGZZuXxMO/XRdLjHRLXfjuEmKAek7IoW/5bkE6ImEWkNNfUb97gu7mFsaG9i9O9 sYRDEi70CxcZNP2daEydElmZuJnqICz0Mf2mChBPDXWNt2/o8a4Pw/I26AOhp43UOGUz gtEg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=2JxLZ3v4Bv8bpwHY46hEuPtIdRIXaUCCMTr9cL9Lo5Y=; b=UCwcv3NAmnoljG6Ejo0zWp9jZQYfjGz6DGdH4YxlYF6mFwQnlqIVpWQX5ETU0CkS6U BleEm3KoRlPX4dp+7V6P3GMfDvHD+bN8fVmJX13R0CbJWygVtf89s/AOlMgjW6dQNy+f sXCqHRmYcqcuLLHf0mS43B/f5Qt0HURW+2gp4rOp6mAY5TT9iszXZdKIobpNCVMrAoT3 G7K4dx2XSRTDmQyw2QXgg0OQO0cnqG/1XILqRzFM2h6Qu5cHPY67xD50VMhxLWp4NbqH vFqKu5QC32Y0XA7CJNILgzVGGZPPg4o2wLOXgGyIy7fHfBC4MS61jzPapQo7Q3q4Xn2T sSIg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@lixom-net.20210112.gappssmtp.com header.s=20210112 header.b="nr/v7Bo9"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id nv8si13669564pjb.136.2022.01.21.11.59.57; Fri, 21 Jan 2022 12:00:09 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@lixom-net.20210112.gappssmtp.com header.s=20210112 header.b="nr/v7Bo9"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1357143AbiASTnm (ORCPT + 99 others); Wed, 19 Jan 2022 14:43:42 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33088 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241622AbiASTnl (ORCPT ); Wed, 19 Jan 2022 14:43:41 -0500 Received: from mail-pj1-x1032.google.com (mail-pj1-x1032.google.com [IPv6:2607:f8b0:4864:20::1032]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 34B13C06161C for ; Wed, 19 Jan 2022 11:43:41 -0800 (PST) Received: by mail-pj1-x1032.google.com with SMTP id a1-20020a17090a688100b001b3fd52338eso3620697pjd.1 for ; Wed, 19 Jan 2022 11:43:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lixom-net.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2JxLZ3v4Bv8bpwHY46hEuPtIdRIXaUCCMTr9cL9Lo5Y=; b=nr/v7Bo98eaUcUQlYthkka1KhZlp1Ut7bIDqOHADDCwAs/NYO/PVuJCoawnGAiknTO 5Jv2cD0EOg4fYZmS2HjiPFvpq+uyAPHyBvIXV/mhsHb7FRwH/siAKDtGVjYEl8f86oGQ HvKQo2qtWrxEmlPjwgrrn3iDMbmTUqwKifIHUPxcYsMl/BTDZTY2Ev0t5n5NM5G9aPp6 gRVFwE5XuUxm/vTIw1yQpHfaYimX+8kYiarmziRxG3O6dnniK+gdLhfQtMdHUkDP+HGx AL6YkvxFK4wf3lNdSgMBH6GnCt2MsAjCJA+Bsi/zeO5tBtKPJi+AFjcEiVjBL+a1GSh3 seEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2JxLZ3v4Bv8bpwHY46hEuPtIdRIXaUCCMTr9cL9Lo5Y=; b=fufAEfpfQZQ07BqLJuNCEKVgKJ0qma89HPUSMCDeJPIMECSuQz2JEsmqH1BE8EqmRU YJSusK2lCxxwg791QqNbe7Cq+66UWvsCq7SSIlm14X8G0e5sBu1ZpwhXTJBHjH76gV/g uaFqagTbXoYs/IcbVn9HOcH76oV2Ie6wPcISktdkYzf0l2nxBfTHebxd64obXUuh7ZZZ emde7lApvbirEseYxTiKB0LwmZaojjlIJT2B1NcU1Zoeqe4ndw3rOZhxQ7QXkM7v/POW 8fHXJ0OvsFxiEQaxPVHWokKivMiLG9WESYu1UO7APSpTHZjHVxS31XR8r5FzdWhijdSA HEPg== X-Gm-Message-State: AOAM531614SQv7satGlr1qCWvGqkp3cS9cIYjc9TdaAebFlf+NdXop+m fyJgdcknxBudBzKzI6aRgJkrwRTqTODoFqne/49FLQ== X-Received: by 2002:a17:902:b947:b0:14a:a6aa:4fa6 with SMTP id h7-20020a170902b94700b0014aa6aa4fa6mr21067587pls.149.1642621420467; Wed, 19 Jan 2022 11:43:40 -0800 (PST) MIME-Version: 1.0 References: <20211227112959.7325-1-krzysztof.kozlowski@canonical.com> In-Reply-To: From: Olof Johansson Date: Wed, 19 Jan 2022 11:43:29 -0800 Message-ID: Subject: Re: [GIT PULL] arm64: dts: samsung: Second pull for v5.17 To: Krzysztof Kozlowski Cc: Arnd Bergmann , Sam Protsenko , arm-soc , SoC Team , Linux ARM , "moderated list:ARM/SAMSUNG EXYNOS ARM ARCHITECTURES" , Linux Kernel Mailing List , Krzysztof Kozlowski Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 19, 2022 at 9:01 AM Krzysztof Kozlowski wrote: > > On Wed, 19 Jan 2022 at 17:53, Olof Johansson wrote: > > > > On Wed, Jan 19, 2022 at 8:07 AM Arnd Bergmann wrote: > > > > > > On Wed, Jan 19, 2022 at 4:11 PM Sam Protsenko > > > wrote: > > > > On Mon, 27 Dec 2021 at 13:30, Krzysztof Kozlowski wrote: > > > > > > > > Hi Olof, Arnd, > > > > > > > > Just want to check if it's possible for those patches to be applied in > > > > v5.17? Sorry for the noise, but that's important to me. > > > > > > I can see that Olof merged merged this into the "arm/late" branch in > > > the soc tree, > > > so I assume he still plans to send it in the next few days. > > > > Yep, will be sent up today most likely. > > > > > With the timing over Christmas, I sent out the large bulk of the > > > contents (anything > > > I merged before Dec 23) last year, and Linus already merged it, the rest ended > > > up in the "late" branch. > > > > > > As usual, there is no guarantee that late changes make it in, but I have seen > > > no indication of any problems so far. > > > > Correct. Been sitting on it for a while in case there were fixes > > coming in for the first pieces that got merged, but in traditional > > fashion I'm guessing those will start to show up a few days after the > > late branch gets merged. :) > > Actually I have such, but to prepare a pull with them, I would need to > base it on some random Linus' commit, not on v5.17-rc1. Therefore I > wait for v5.17-rc1. Would you prefer different approach? If needed you can base it on Linus' last merge commit of arm-soc contents for the first set of fixes (or your topic branch that you sent the code up on), but it's also OK to wait if they're minor bugs/fixes. -Olof