public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>,
	John Crispin <john@phrozen.org>,
	linux-mips@vger.kernel.org
Subject: Re: [PATCH] MIPS: lantiq: export clk_get_io() for lantiq_wdt.ko
Date: Mon, 19 Sep 2022 16:50:11 +0200	[thread overview]
Message-ID: <20220919145010.GF7674@alpha.franken.de> (raw)
In-Reply-To: <20220917232540.25436-1-rdunlap@infradead.org>

On Sat, Sep 17, 2022 at 04:25:40PM -0700, Randy Dunlap wrote:
> The lantiq WDT driver uses clk_get_io(), which is not exported,
> so export it to fix a build error:
> 
> ERROR: modpost: "clk_get_io" [drivers/watchdog/lantiq_wdt.ko] undefined!
> 
> Fixes: 287e3f3f4e68 ("MIPS: lantiq: implement support for clkdev api")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Reported-by: kernel test robot <lkp@intel.com>
> Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
> Cc: John Crispin <john@phrozen.org>
> Cc: linux-mips@vger.kernel.org
> ---
>  arch/mips/lantiq/clk.c |    1 +
>  1 file changed, 1 insertion(+)
> 
> --- a/arch/mips/lantiq/clk.c
> +++ b/arch/mips/lantiq/clk.c
> @@ -50,6 +50,7 @@ struct clk *clk_get_io(void)
>  {
>  	return &cpu_clk_generic[2];
>  }
> +EXPORT_SYMBOL_GPL(clk_get_io);
>  
>  struct clk *clk_get_ppe(void)
>  {

applied to mips-fixes.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

      reply	other threads:[~2022-09-19 14:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-17 23:25 [PATCH] MIPS: lantiq: export clk_get_io() for lantiq_wdt.ko Randy Dunlap
2022-09-19 14:50 ` Thomas Bogendoerfer [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=20220919145010.GF7674@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=john@phrozen.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=rdunlap@infradead.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