From: Biju Das <biju.das.jz@bp.renesas.com>
To: Stephen Boyd <sboyd@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Mark Brown <broonie@kernel.org>,
kernel test robot <lkp@intel.com>
Cc: "oe-kbuild-all@" <lists.linux.dev oe-kbuild-all@lists.linux.dev>,
Linux Memory Management List <linux-mm@kvack.org>,
"linux-clk@" <vger.kernel.org linux-clk@vger.kernel.org>,
"linux-kernel@" <vger.kernel.org linux-kernel@vger.kernel.org>
Subject: RE: [linux-next:master 11663/12731] ERROR: modpost: "clk_unregister_fixed_rate" [drivers/regulator/raa215300.ko] undefined!
Date: Fri, 30 Jun 2023 06:55:14 +0000 [thread overview]
Message-ID: <OS0PR01MB59224F4C50258B34C966603B862AA@OS0PR01MB5922.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <d0a14215febf33fcfc36c40420ff352f.sboyd@kernel.org>
Hi Stephen,
Thanks for the feedback.
> -----Original Message-----
> From: Stephen Boyd <sboyd@kernel.org>
> Sent: Friday, June 30, 2023 5:41 AM
> To: Biju Das <biju.das.jz@bp.renesas.com>; Geert Uytterhoeven
> <geert@linux-m68k.org>; Mark Brown <broonie@kernel.org>; kernel test
> robot <lkp@intel.com>
> Cc: oe-kbuild-all@ <lists.linux.dev oe-kbuild-all@lists.linux.dev>;
> Linux Memory Management List <linux-mm@kvack.org>; linux-clk@
> <vger.kernel.org linux-clk@vger.kernel.org>; linux-kernel@
> <vger.kernel.org linux-kernel@vger.kernel.org>
> Subject: RE: [linux-next:master 11663/12731] ERROR: modpost:
> "clk_unregister_fixed_rate" [drivers/regulator/raa215300.ko] undefined!
>
> Quoting Biju Das (2023-06-28 08:47:19)
> > Hi All,
> >
> > I have come up with two solutions for fixing this issue.
> >
> > Please suggest which solution, I should submit.
> >
> > First solution allows to build the driver for m68k architecture,
> > whereas the second solution skips it.
>
> I'd opt to depend on COMMON_CLK config.
Yes, it is mainlined like above [1]
[1] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20230630&id=e9bd04e52d649c3cfd713b594c5db35cab03c42b
Cheers,
Biju
prev parent reply other threads:[~2023-06-30 6:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 12:52 kernel test robot
2023-06-28 15:47 ` Biju Das
2023-06-28 16:56 ` Mark Brown
2023-06-30 4:40 ` Stephen Boyd
2023-06-30 6:55 ` Biju Das [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=OS0PR01MB59224F4C50258B34C966603B862AA@OS0PR01MB5922.jpnprd01.prod.outlook.com \
--to=biju.das.jz@bp.renesas.com \
--cc=broonie@kernel.org \
--cc=geert@linux-m68k.org \
--cc=lkp@intel.com \
--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