From: Stephen Boyd <sboyd@kernel.org>
To: Keguang Zhang <keguang.zhang@gmail.com>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mips@vger.kernel.org,
Serge Semin <Sergey.Semin@baikalelectronics.ru>
Subject: Re: [PATCH] MIPS: loongson32: Update the clock initialization
Date: Wed, 15 Mar 2023 12:04:46 -0700 [thread overview]
Message-ID: <48d30bc1f094bee18a2180a5b8e65e40.sboyd@kernel.org> (raw)
In-Reply-To: <CAJhJPsWDO_nyPLH7uMTB+ODS74SAKDPGOXxk_Nperk1dKBKStQ@mail.gmail.com>
Quoting Keguang Zhang (2023-03-15 02:43:02)
> On Wed, Mar 15, 2023 at 5:29 PM Thomas Bogendoerfer
> <tsbogend@alpha.franken.de> wrote:
> >
> > 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 ?
> >
> Sure. Will do.
>
Please resend this patch along with the loongson patches that it goes
with.
prev parent reply other threads:[~2023-03-15 19:05 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
2023-03-15 9:43 ` Keguang Zhang
2023-03-15 19:04 ` Stephen Boyd [this message]
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=48d30bc1f094bee18a2180a5b8e65e40.sboyd@kernel.org \
--to=sboyd@kernel.org \
--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=tsbogend@alpha.franken.de \
/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