public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Christophe Leroy" <christophe.leroy@csgroup.eu>,
	"Herve Codina" <herve.codina@bootlin.com>,
	"Qiang Zhao" <qiang.zhao@nxp.com>
Cc: linuxppc-dev@lists.ozlabs.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	"kernel test robot" <lkp@intel.com>
Subject: Re: [PATCH] soc: fsl: qe: ucc: Export ucc_mux_set_grant_tsa_bkpt
Date: Thu, 05 Sep 2024 09:23:10 +0000	[thread overview]
Message-ID: <24dd3479-6fef-43ec-bcec-e70474128e53@app.fastmail.com> (raw)
In-Reply-To: <7091c023-c7e6-4b3a-b306-12d73b8f6698@csgroup.eu>

On Thu, Sep 5, 2024, at 07:31, Christophe Leroy wrote:
> Le 05/09/2024 à 09:22, Herve Codina a écrit :
>> When TSA is compiled as module the following error is reported:
>>    "ucc_mux_set_grant_tsa_bkpt" [drivers/soc/fsl/qe/tsa.ko] undefined!
>> 
>> Indeed, the ucc_mux_set_grant_tsa_bkpt symbol is not exported.
>> 
>> Simply export ucc_mux_set_grant_tsa_bkpt.
>> 
>> Reported-by: kernel test robot <lkp@intel.com>
>> Closes: https://lore.kernel.org/oe-kbuild-all/202409051409.fszn8rEo-lkp@intel.com/
>> Signed-off-by: Herve Codina <herve.codina@bootlin.com>
>
> Acked-by: Christophe Leroy <christophe.leroy@csgroup.eu>
>
> Arnd, it is ok for you to take this patch directly ?

I've applied this one directly, but I'm not always paying attention
to patches flying by, so if you have more fixes like this in the future,
I recommend that you forward those to soc@kernel.org, either as a patch
or a pull request.

That way, I see them in patchwork and will apply them from there.

      Arnd


      reply	other threads:[~2024-09-05  9:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-05  7:22 [PATCH] soc: fsl: qe: ucc: Export ucc_mux_set_grant_tsa_bkpt Herve Codina
2024-09-05  7:31 ` Christophe Leroy
2024-09-05  9:23   ` Arnd Bergmann [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=24dd3479-6fef-43ec-bcec-e70474128e53@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=christophe.leroy@csgroup.eu \
    --cc=herve.codina@bootlin.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=lkp@intel.com \
    --cc=qiang.zhao@nxp.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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