From: Chen, Rong A <rong.a.chen@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [peterz-queue:sched/core 8/11] include/linux/sched.h:1722:57: warning: unused parameter 'dst'
Date: Mon, 23 Aug 2021 17:16:05 +0800 [thread overview]
Message-ID: <428f3e9a-a8d3-51ca-5e2e-caa50b8da3eb@intel.com> (raw)
In-Reply-To: <YSNkCAyMU0tJoedT@hirez.programming.kicks-ass.net>
[-- Attachment #1: Type: text/plain, Size: 834 bytes --]
On 8/23/2021 5:02 PM, Peter Zijlstra wrote:
> On Sat, Aug 21, 2021 at 09:20:50AM +0800, kernel test robot wrote:
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git sched/core
>> head: 234b8ab6476c5edd5262e2ff563de9498d60044a
>> commit: b90ca8badbd11488e5f762346b028666808164e7 [8/11] sched: Introduce task_struct::user_cpus_ptr to track requested affinity
>> config: i386-randconfig-a016-20210820 (attached as .config)
>> compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project d9c5613e856cf2addfbf892fc4c1ce9ef9feceaa)
>> reproduce (this is a W=1 build):
>
> Dear 0day folks; could you please blacklist me for all W=1 build output?
> I'm 100% not interested in random compiler generated garbage.
Hi Peterz,
Got it, we'll do that for you asap.
Best Regards,
Rong Chen
WARNING: multiple messages have this Message-ID (diff)
From: "Chen, Rong A" <rong.a.chen@intel.com>
To: Peter Zijlstra <peterz@infradead.org>, kernel test robot <lkp@intel.com>
Cc: Will Deacon <will@kernel.org>,
clang-built-linux@googlegroups.com, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org,
Valentin Schneider <Valentin.Schneider@arm.com>
Subject: Re: [kbuild-all] Re: [peterz-queue:sched/core 8/11] include/linux/sched.h:1722:57: warning: unused parameter 'dst'
Date: Mon, 23 Aug 2021 17:16:05 +0800 [thread overview]
Message-ID: <428f3e9a-a8d3-51ca-5e2e-caa50b8da3eb@intel.com> (raw)
In-Reply-To: <YSNkCAyMU0tJoedT@hirez.programming.kicks-ass.net>
On 8/23/2021 5:02 PM, Peter Zijlstra wrote:
> On Sat, Aug 21, 2021 at 09:20:50AM +0800, kernel test robot wrote:
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git sched/core
>> head: 234b8ab6476c5edd5262e2ff563de9498d60044a
>> commit: b90ca8badbd11488e5f762346b028666808164e7 [8/11] sched: Introduce task_struct::user_cpus_ptr to track requested affinity
>> config: i386-randconfig-a016-20210820 (attached as .config)
>> compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project d9c5613e856cf2addfbf892fc4c1ce9ef9feceaa)
>> reproduce (this is a W=1 build):
>
> Dear 0day folks; could you please blacklist me for all W=1 build output?
> I'm 100% not interested in random compiler generated garbage.
Hi Peterz,
Got it, we'll do that for you asap.
Best Regards,
Rong Chen
next prev parent reply other threads:[~2021-08-23 9:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-21 1:20 [peterz-queue:sched/core 8/11] include/linux/sched.h:1722:57: warning: unused parameter 'dst' kernel test robot
2021-08-21 1:20 ` kernel test robot
2021-08-23 9:02 ` Peter Zijlstra
2021-08-23 9:02 ` Peter Zijlstra
2021-08-23 9:16 ` Chen, Rong A [this message]
2021-08-23 9:16 ` [kbuild-all] " Chen, Rong A
2021-08-23 9:26 ` Peter Zijlstra
2021-08-23 9:26 ` [kbuild-all] " Peter Zijlstra
2021-09-11 12:24 ` Peter Zijlstra
2021-09-11 12:24 ` [kbuild-all] " Peter Zijlstra
2021-09-13 1:05 ` Rong Chen
2021-09-13 1:05 ` [kbuild-all] " Rong Chen
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=428f3e9a-a8d3-51ca-5e2e-caa50b8da3eb@intel.com \
--to=rong.a.chen@intel.com \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.