From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Keguang Zhang <keguang.zhang@gmail.com>
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mips@vger.kernel.org,
Serge Semin <Sergey.Semin@baikalelectronics.ru>,
Stephen Boyd <sboyd@kernel.org>
Subject: Re: [PATCH] MIPS: loongson32: Update the clock initialization
Date: Wed, 15 Mar 2023 10:29:10 +0100 [thread overview]
Message-ID: <20230315092910.GA8008@alpha.franken.de> (raw)
In-Reply-To: <CAJhJPsUQN5Lo_rVUbbmGY68gorwkcQT=9AXfcEh371cP97Wj_A@mail.gmail.com>
On Wed, Mar 15, 2023 at 11:07:23AM +0800, Keguang Zhang wrote:
> On Sat, Feb 11, 2023 at 7:31 AM Stephen Boyd <sboyd@kernel.org> wrote:
> >
> > Quoting Keguang Zhang (2023-02-10 03:11:41)
> > > The Loongson-1 clock driver is under re-implementation
> > > to add DT support. As a result, ls1x_clk_init() will be dropped soon.
> > > Therefore, call of_clk_init() for clock initialization instead.
> > >
> > > Link: https://lore.kernel.org/all/20230209132614.1079198-3-keguang.zhang@gmail.com
> > > Link: https://lore.kernel.org/all/20230209132614.1079198-4-keguang.zhang@gmail.com
>
> Hi Thomas,
> Sorry to bother you.
> For fear of raising build error, is it possible to merge this patch
> before the above two patches getting applied?
> Or is there anything to improve?
> Thanks very much!
the IMHO best way would be to let this patch go the same way as
the other patch set. So Stephen could you take this into your
tree, too ?
Acked-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2023-03-15 9:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 11:11 [PATCH] MIPS: loongson32: Update the clock initialization Keguang Zhang
2023-02-10 23:31 ` Stephen Boyd
2023-03-15 3:07 ` Keguang Zhang
2023-03-15 9:29 ` Thomas Bogendoerfer [this message]
2023-03-15 9:43 ` Keguang Zhang
2023-03-15 19:04 ` Stephen Boyd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230315092910.GA8008@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=Sergey.Semin@baikalelectronics.ru \
--cc=keguang.zhang@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=sboyd@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox