From: Peter Zijlstra <peterz@infradead.org>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org, lkp@intel.com, yujie.liu@intel.com,
oliver.sang@intel.com
Subject: Re: [peterz-queue:sched/cleanup 38/40] kernel/irq_work.c:44:6: warning: no previous prototype for function 'irq_work_single'
Date: Thu, 7 Oct 2021 09:48:43 +0200 [thread overview]
Message-ID: <20211007074843.GO174703@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <202110071515.2ivww4qz-lkp@intel.com>
This mail has dodgy headers:
To: unlisted-recipients: no To-header on input <;
Is the robot sick?
next prev parent reply other threads:[~2021-10-07 7:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 7:39 [peterz-queue:sched/cleanup 38/40] kernel/irq_work.c:44:6: warning: no previous prototype for function 'irq_work_single' kernel test robot
2021-10-07 7:48 ` Peter Zijlstra [this message]
2021-10-08 1:27 ` [kbuild-all] " Chen, Rong A
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=20211007074843.GO174703@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=yujie.liu@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;
as well as URLs for NNTP newsgroup(s).