public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: kernel test robot <lkp@intel.com>, LKML <linux-kernel@vger.kernel.org>
Cc: kbuild-all@lists.01.org, Christoph Hellwig <hch@infradead.org>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: [patch V4 1/2] smp: Rename flush_smp_call_function_from_idle()
Date: Wed, 13 Apr 2022 15:00:00 +0200	[thread overview]
Message-ID: <878rs9f8a7.ffs@tglx> (raw)
In-Reply-To: <202204131011.m9M80Uip-lkp@intel.com>

On Wed, Apr 13 2022 at 10:52, kernel test robot wrote:
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All warnings (new ones prefixed by >>):
>
>>> kernel/smp.c:697:6: warning: no previous prototype for 'flush_smp_call_function_queue' [-Wmissing-prototypes]
>      697 | void flush_smp_call_function_queue(void)
>          |      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~

This is not really new. It's "new" because the function was renamed.

I'll fix the whole pile of preexisting warnings which are related to
kernel/sched/*.

Thanks,

        tglx

  reply	other threads:[~2022-04-13 13:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12 20:51 [patch V4 0/2] smp: Make softirq handling RT friendly Thomas Gleixner
2022-04-12 20:51 ` [patch V4 1/2] smp: Rename flush_smp_call_function_from_idle() Thomas Gleixner
2022-04-13  2:52   ` kernel test robot
2022-04-13 13:00     ` Thomas Gleixner [this message]
2022-04-13  2:53   ` kernel test robot
2022-04-12 20:51 ` [patch V4 2/2] smp: Make softirq handling RT safe in flush_smp_call_function_queue() Thomas Gleixner

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=878rs9f8a7.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=bigeasy@linutronix.de \
    --cc=hch@infradead.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.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