[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3ea0db23ab3284fdee2fec6cfc08026a0acccb6f.camel@gmail.com>
Date: Tue, 12 Oct 2021 14:57:45 +0200
From: Alexander Sverdlin <alexander.sverdlin@...il.com>
To: Arnd Bergmann <arnd@...db.de>,
Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Mark Brown <broonie@...nel.org>,
Russell King <linux@...linux.org.uk>,
Hartley Sweeten <hsweeten@...ionengravers.com>,
Linus Walleij <linus.walleij@...aro.org>,
Ard Biesheuvel <ardb@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>,
Anshuman Khandual <anshuman.khandual@....com>,
Geert Uytterhoeven <geert+renesas@...der.be>,
YiFei Zhu <yifeifz2@...inois.edu>,
Mike Rapoport <rppt@...nel.org>,
Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>,
"moderated list:ARM PORT" <linux-arm-kernel@...ts.infradead.org>,
open list <linux-kernel@...r.kernel.org>,
Nikita Shubin <nikita.shubin@...uefel.me>
Subject: Re: [PATCH v2 8/8] ep93xx: clock: convert in-place to COMMON_CLK
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.
Powered by blists - more mailing lists