mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: trix@redhat.com, tglx@linutronix.de, shawnguo@kernel.org,
	s.hauer@pengutronix.de, kernel@pengutronix.de,
	festevam@gmail.com, linux-imx@nxp.com
Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] clocksource/timer-imx-tpm: define tpm_read_sched_clock() conditionally for arm
Date: Sat, 5 Mar 2022 23:30:59 +0100	[thread overview]
Message-ID: <708ef23d-0c4a-47b5-dfe1-c55df9ccbf4b@linaro.org> (raw)
In-Reply-To: <20220305205605.707937-1-trix@redhat.com>


Hi,

thanks for your patch.

It was already fixed by:

https://lore.kernel.org/r/20220303184212.2356245-1-nathan@kernel.org


On 05/03/2022 21:56, trix@redhat.com wrote:
> From: Tom Rix <trix@redhat.com>
> 
> On aarch64 allyesconfig there is this error
> timer-imx-tpm.c:78:20: error: 'tpm_read_sched_clock'
>    defined but not used [-Werror=unused-function]
>     78 | static u64 notrace tpm_read_sched_clock(void)
>        |                    ^~~~~~~~~~~~~~~~~~~~
> 
> tpm_read_sched_clock() is only used conditionally
> for arm.  So also define conditionally for arm.
> 
> Signed-off-by: Tom Rix <trix@redhat.com>
> ---
>   drivers/clocksource/timer-imx-tpm.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/clocksource/timer-imx-tpm.c b/drivers/clocksource/timer-imx-tpm.c
> index 60cefc247b715..bd64a8a8427f3 100644
> --- a/drivers/clocksource/timer-imx-tpm.c
> +++ b/drivers/clocksource/timer-imx-tpm.c
> @@ -73,12 +73,12 @@ static unsigned long tpm_read_current_timer(void)
>   {
>   	return tpm_read_counter();
>   }
> -#endif
>   
>   static u64 notrace tpm_read_sched_clock(void)
>   {
>   	return tpm_read_counter();
>   }
> +#endif
>   
>   static int tpm_set_next_event(unsigned long delta,
>   				struct clock_event_device *evt)


-- 
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

      reply	other threads:[~2022-03-05 22:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-05 20:56 trix
2022-03-05 22:30 ` Daniel Lezcano [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=708ef23d-0c4a-47b5-dfe1-c55df9ccbf4b@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=trix@redhat.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

all inboxes | Powered by JetHome®