public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Srinivasarao Pathipati <quic_c_spathi@quicinc.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH V1] rcu-tasks: Fix build error
Date: Mon, 20 Feb 2023 19:54:00 +0100	[thread overview]
Message-ID: <Y/PByBdfz/WPBs2W@kroah.com> (raw)
In-Reply-To: <1676916839-32235-1-git-send-email-quic_c_spathi@quicinc.com>

On Mon, Feb 20, 2023 at 11:43:59PM +0530, Srinivasarao Pathipati wrote:
> Making show_rcu_tasks_rude_gp_kthread() function as 'inline' to
> fix below compilation error.
> This is applicable to only 5.10 kernels as code got modified
> in latest kernels.
> 
>  In file included from kernel/rcu/update.c:579:0:
>  kernel/rcu/tasks.h:710:13: error: ‘show_rcu_tasks_rude_gp_kthread’ defined but not used [-Werror=unused-function]
>   static void show_rcu_tasks_rude_gp_kthread(void) {}
> 
> Signed-off-by: Srinivasarao Pathipati <quic_c_spathi@quicinc.com>
> ---
>  kernel/rcu/tasks.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/kernel/rcu/tasks.h b/kernel/rcu/tasks.h
> index 8b51e6a..53ddb4e 100644
> --- a/kernel/rcu/tasks.h
> +++ b/kernel/rcu/tasks.h
> @@ -707,7 +707,7 @@ static void show_rcu_tasks_rude_gp_kthread(void)
>  #endif /* #ifndef CONFIG_TINY_RCU */
>  
>  #else /* #ifdef CONFIG_TASKS_RUDE_RCU */
> -static void show_rcu_tasks_rude_gp_kthread(void) {}
> +static inline void show_rcu_tasks_rude_gp_kthread(void) {}
>  #endif /* #else #ifdef CONFIG_TASKS_RUDE_RCU */
>  
>  ////////////////////////////////////////////////////////////////////////
> -- 
> 2.7.4
> 

What commit id caused this problem?

And why isn't it an issue in newer kernels, what commit id fixed it and
why can't we just take that instead?

thanks,

greg k-h

  reply	other threads:[~2023-02-20 18:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-20 18:13 [PATCH V1] rcu-tasks: Fix build error Srinivasarao Pathipati
2023-02-20 18:54 ` Greg KH [this message]
2023-02-21  9:27   ` Srinivasarao Pathipati
2023-02-21 10:37     ` Greg KH
2023-02-21 11:19       ` Srinivasarao Pathipati
2023-02-21 13:45         ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2023-02-21 12:03 Srinivasarao Pathipati
2023-02-21 13:44 ` Greg KH

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=Y/PByBdfz/WPBs2W@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=quic_c_spathi@quicinc.com \
    --cc=stable@vger.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