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;
Message-ID: <3ea0db23ab3284fdee2fec6cfc08026a0acccb6f.camel@gmail.com>
Subject: Re: [PATCH v2 8/8] ep93xx: clock: convert in-place to COMMON_CLK
From:   Alexander Sverdlin <alexander.sverdlin@gmail.com>
To:     Arnd Bergmann <arnd@arndb.de>,
        Geert Uytterhoeven <geert@linux-m68k.org>
Cc:     Mark Brown <broonie@kernel.org>,
        Russell King <linux@armlinux.org.uk>,
        Hartley Sweeten <hsweeten@visionengravers.com>,
        Linus Walleij <linus.walleij@linaro.org>,
        Ard Biesheuvel <ardb@kernel.org>,
        Andrew Morton <akpm@linux-foundation.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
        Anshuman Khandual <anshuman.khandual@arm.com>,
        Geert Uytterhoeven <geert+renesas@glider.be>,
        YiFei Zhu <yifeifz2@illinois.edu>,
        Mike Rapoport <rppt@kernel.org>,
        Uwe =?ISO-8859-1?Q?Kleine-K=F6nig?= 
        <u.kleine-koenig@pengutronix.de>,
        "moderated list:ARM PORT" <linux-arm-kernel@lists.infradead.org>,
        open list <linux-kernel@vger.kernel.org>,
        Nikita Shubin <nikita.shubin@maquefel.me>
Date:   Tue, 12 Oct 2021 14:57:45 +0200
In-Reply-To: <CAK8P3a2cvd+od4+UwwrBQ=7F3+cpEAMFz9tBfsZ=nR1Ak1ppwQ@mail.gmail.com>
References: <20210726140001.24820-1-nikita.shubin@maquefel.me>
         <20210726140001.24820-9-nikita.shubin@maquefel.me>
         <ed557882a9530f2fd6245e34657be62399df76bc.camel@gmail.com>
         <CAK8P3a0Y4uwX4B10d5CR3WjZ1qXAqhKJGJ0EhUEF60uB1q3H9A@mail.gmail.com>
         <e50f2da7af1fa6f02fd413081fa5762837b86895.camel@gmail.com>
         <CAK8P3a3jAdYQerE03O5s2_PBUqt5QPCPSQxxs54E7-V=0HVBXA@mail.gmail.com>
         <YWVixgDQtJ8EGbwo@sirena.org.uk>
         <7f7acc8986aca1c895de732297b2995d05ec23e7.camel@gmail.com>
         <YWVmvHsEkPFkrD/R@sirena.org.uk>
         <7ec1690ea0ca9f6538b8228f78e62b2f38405fd4.camel@gmail.com>
         <YWVvyKq4W4VShiRU@sirena.org.uk>
         <00781d5212bb4015064d07e762ae0695d16e834e.camel@gmail.com>
         <CAMuHMdUCpfpORD9r28r1hdtdKMPyvXtkYZQsiBCfM8WDcLYKFw@mail.gmail.com>
         <CAK8P3a2cvd+od4+UwwrBQ=7F3+cpEAMFz9tBfsZ=nR1Ak1ppwQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.40.4 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: bulk

Hi Arnd,

On Tue, 2021-10-12 at 14:39 +0200, Arnd Bergmann wrote:
> Right, if everything else is in mainline, then having the last two patches
> in the soc tree gets the job done the quickest.
> 
> If any of the other patches are only in linux-next but not in mainline yet,
> then it seems best for Mark to take the ASoC/i2s patch for v5.16, and I'll
> take the last one for v5.17, or maybe queue it separately from the rest
> and send that in the second half of the 5.16 merge window after everything
> else has landed.

correct, everything else is in mainline, only these two left floating.
Should I resend them for soc patchwork?

-- 
Alexander Sverdlin.