From: "Chen, Rong A" <rong.a.chen@intel.com>
To: Steven Rostedt <rostedt@goodmis.org>, kernel test robot <lkp@intel.com>
Cc: Daniel Bristot de Oliveira <bristot@redhat.com>,
clang-built-linux@googlegroups.com, kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [kbuild-all] Re: [linux-next:master 12896/14055] kernel/trace/trace_osnoise.c:438:6: warning: no previous prototype for function 'osnoise_trace_irq_entry'
Date: Wed, 30 Jun 2021 16:34:58 +0800 [thread overview]
Message-ID: <c53f2747-e672-672e-df4f-6d0df40431f5@intel.com> (raw)
In-Reply-To: <20210629075300.177d5e47@oasis.local.home>
On 6/29/2021 7:53 PM, Steven Rostedt wrote:
> On Tue, 29 Jun 2021 19:10:01 +0800
> kernel test robot <lkp@intel.com> wrote:
>
>> Hi Daniel,
>>
>> FYI, the error/warning still remains.
>
> Really?
>
> These were reported on Saturday (some people actually take off on weekends).
>
> I don't push any update that doesn't go through my test suite, which
> usually takes around 13 hours to run. I received the fixes from Daniel
> on Monday, and then kicked off my tests. Which *just* finished!
>
> Can we delay the pesky reminders for at least a week?
>
> -- Steve
>
Hi Steve,
Thanks for the advice, we will do it asap.
Best Regards,
Rong Chen
prev parent reply other threads:[~2021-06-30 8:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 11:10 [linux-next:master 12896/14055] kernel/trace/trace_osnoise.c:438:6: warning: no previous prototype for function 'osnoise_trace_irq_entry' kernel test robot
2021-06-29 11:53 ` Steven Rostedt
2021-06-30 8:34 ` Chen, Rong A [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=c53f2747-e672-672e-df4f-6d0df40431f5@intel.com \
--to=rong.a.chen@intel.com \
--cc=bristot@redhat.com \
--cc=clang-built-linux@googlegroups.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).