[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a2cvd+od4+UwwrBQ=7F3+cpEAMFz9tBfsZ=nR1Ak1ppwQ@mail.gmail.com>
Date: Tue, 12 Oct 2021 14:39:13 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Alexander Sverdlin <alexander.sverdlin@...il.com>,
Mark Brown <broonie@...nel.org>, Arnd Bergmann <arnd@...db.de>,
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
On Tue, Oct 12, 2021 at 1:30 PM Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
> On Tue, Oct 12, 2021 at 1:26 PM Alexander Sverdlin <alexander.sverdlin@...il.com> wrote:
> > On Tue, 2021-10-12 at 12:21 +0100, Mark Brown wrote:
> > > Looks like Arnd is ready to pick it, and the only dependency which is
> > > > not yet merged into Linus's tree is "ASoC: cirrus: i2s: Prepare clock before using it".
> > >
> > > OK, so I'm still unclear as to what's going on here. Arnd's mail where
> > > I got copied into this subthread suggested that things were getting
> > > merged by individual trees which is generally easiest?
> >
> > I only wanted to ask you to pick ASoC patch, I can resend it if you'd like.
> > It has no dependencies and all the previous patches were already picked
> > and are visible in the Linus's master.
>
> So it might be better for Arnd to pick up the ASoC patch, too.
> Else he has to postpone the final CCF conversion patch one more cycle,
> to avoid regressions.
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.
Arnd
Powered by blists - more mailing lists