mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Claudio Scordino <claudio@evidence.eu.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	peterz@infradead.org, mingo@redhat.com,
	Claudio Scordino <claudio@evidence.eu.com>,
	Juri Lelli <juri.lelli@arm.com>,
	Luca Abeni <luca.abeni@santannapisa.it>
Subject: Re: [PATCH] sched/deadline: add GRUB bw change tracepoints
Date: Thu, 6 Jul 2017 11:40:13 +0800	[thread overview]
Message-ID: <201707061124.XYrPZEND%fengguang.wu@intel.com> (raw)
In-Reply-To: <1499171396-9662-1-git-send-email-claudio@evidence.eu.com>

[-- Attachment #1: Type: text/plain, Size: 2013 bytes --]

Hi Claudio,

[auto build test ERROR on tip/auto-latest]
[cannot apply to v4.12]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Claudio-Scordino/sched-deadline-add-GRUB-bw-change-tracepoints/20170706-091701
config: xtensa-allyesconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 4.9.0
reproduce:
        wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=xtensa 

All errors (new ones prefixed by >>):

   kernel/sched/deadline.c: In function 'add_running_bw':
>> kernel/sched/deadline.c:90:22: error: 'struct rq' has no member named 'cpu'
       rq_of_dl_rq(dl_rq)->cpu);
                         ^
   kernel/sched/deadline.c: In function 'sub_running_bw':
   kernel/sched/deadline.c:104:22: error: 'struct rq' has no member named 'cpu'
       rq_of_dl_rq(dl_rq)->cpu);
                         ^
   kernel/sched/deadline.c: In function 'add_rq_bw':
   kernel/sched/deadline.c:116:22: error: 'struct rq' has no member named 'cpu'
       rq_of_dl_rq(dl_rq)->cpu);
                         ^
   kernel/sched/deadline.c: In function 'sub_rq_bw':
   kernel/sched/deadline.c:132:22: error: 'struct rq' has no member named 'cpu'
       rq_of_dl_rq(dl_rq)->cpu);
                         ^

vim +90 kernel/sched/deadline.c

    84	
    85		lockdep_assert_held(&(rq_of_dl_rq(dl_rq))->lock);
    86		dl_rq->running_bw += dl_bw;
    87		SCHED_WARN_ON(dl_rq->running_bw < old); /* overflow */
    88		SCHED_WARN_ON(dl_rq->running_bw > dl_rq->this_bw);
    89		trace_sched_dl_grub(dl_rq->this_bw, dl_rq->running_bw,
  > 90				rq_of_dl_rq(dl_rq)->cpu);
    91	}
    92	
    93	static inline

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 50189 bytes --]

      parent reply	other threads:[~2017-07-06  3:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-04 12:29 Claudio Scordino
2017-07-04 12:49 ` Juri Lelli
     [not found]   ` <CAGWmfYogdmOFLOsHYnu-YO0+0L6ypuM_DmJkUQeU4rTsye_4GA@mail.gmail.com>
     [not found]     ` <CAGWmfYrayXX3Aw2Mk-wQFtw9LSYB-scFc5mdCVy=iXdN0fTfjQ@mail.gmail.com>
     [not found]       ` <CAGWmfYq2aDJekMhE6R+ALNMQwhbkAw8-BWnkbAbszpXQryTgyQ@mail.gmail.com>
2017-07-04 13:16         ` Claudio Scordino
2017-07-06  3:40 ` kbuild test robot [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=201707061124.XYrPZEND%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=claudio@evidence.eu.com \
    --cc=juri.lelli@arm.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca.abeni@santannapisa.it \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.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

all inboxes | Powered by JetHome®