mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: kbuild test robot <lkp@intel.com>, Fengguang Wu <fengguang.wu@intel.com>
Cc: Nate Dailey <nate.dailey@stratus.com>,
	kbuild-all@01.org, linux-kernel@vger.kernel.org,
	bigeasy@linutronix.de, tglx@linutronix.de
Subject: Re: [PATCH RT] usb: Use _nort in usb_hcd_pci_remove
Date: Tue, 25 Apr 2017 08:01:54 -0400	[thread overview]
Message-ID: <20170425080154.5aba8b18@gandalf.local.home> (raw)
In-Reply-To: <201704251347.xzis6U3b%fengguang.wu@intel.com>

On Tue, 25 Apr 2017 13:26:41 +0800
kbuild test robot <lkp@intel.com> wrote:

> Hi Nate,
> 
> [auto build test ERROR on usb/usb-testing]
> [also build test ERROR on v4.11-rc8 next-20170424]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

Hi Fengguang,

You may want to have your bot look at the subject. If there's an "RT"
in the [PATCH ...] portion, then you need to apply the PREEMPT_RT
patch, or use one of the RT git trees for it.

This patch is applied to the RT trees.

Thanks!

-- Steve

> 
> url:    https://github.com/0day-ci/linux/commits/Nate-Dailey/usb-Use-_nort-in-usb_hcd_pci_remove/20170424-214548
> base:   https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
> config: x86_64-rhel (attached as .config)
> compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
> reproduce:
>         # save the attached .config to linux build tree
>         make ARCH=x86_64 
> 
> All errors (new ones prefixed by >>):
> 
>    drivers/usb//core/hcd-pci.c: In function 'usb_hcd_pci_remove':
> >> drivers/usb//core/hcd-pci.c:344:2: error: implicit declaration of function 'local_irq_disable_nort' [-Werror=implicit-function-declaration]  
>      local_irq_disable_nort();
>      ^~~~~~~~~~~~~~~~~~~~~~
> >> drivers/usb//core/hcd-pci.c:346:2: error: implicit declaration of function 'local_irq_enable_nort' [-Werror=implicit-function-declaration]  
>      local_irq_enable_nort();
>      ^~~~~~~~~~~~~~~~~~~~~
>    cc1: some warnings being treated as errors
> 
> vim +/local_irq_disable_nort +344 drivers/usb//core/hcd-pci.c
> 
>    338			pm_runtime_get_noresume(&dev->dev);
>    339	
>    340		/* Fake an interrupt request in order to give the driver a chance
>    341		 * to test whether the controller hardware has been removed (e.g.,
>    342		 * cardbus physical eject).
>    343		 */
>  > 344		local_irq_disable_nort();  
>    345		usb_hcd_irq(0, hcd);
>  > 346		local_irq_enable_nort();  
>    347	
>    348		/* Note: dev_set_drvdata must be called while holding the rwsem */
>    349		if (dev->class == CL_EHCI) {
> 
> ---
> 0-DAY kernel test infrastructure                Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

  reply	other threads:[~2017-04-25 12:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-24 12:29 Nate Dailey
2017-04-25  5:26 ` kbuild test robot
2017-04-25 12:01   ` Steven Rostedt [this message]
2017-04-25 13:06     ` [kbuild-all] " Philip Li

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=20170425080154.5aba8b18@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=bigeasy@linutronix.de \
    --cc=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=nate.dailey@stratus.com \
    --cc=tglx@linutronix.de \
    /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®