All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sched/core: include asm/paravirt.h
Date: Fri, 24 Feb 2017 09:31:52 +0100	[thread overview]
Message-ID: <20170224083152.GA24307@gmail.com> (raw)
In-Reply-To: <CAK8P3a21JXApn=zGF-bWJYiZ+1RUZZZ83qM_PFz7BtHtQnH0pA@mail.gmail.com>


* Arnd Bergmann <arnd@arndb.de> wrote:

> On Fri, Feb 17, 2017 at 3:43 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> > One of the headers that got removed was needed after all, depending
> > on the configuration:
> >
> > kernel/sched/core.c: In function 'update_rq_clock_task':
> > kernel/sched/core.c:198:50: error: 'paravirt_steal_rq_enabled' undeclared (first use in this function); did you mean 'arch_local_irq_enable'?
> >
> > This restores the include.
> >
> > Fixes: 004172bdad64 ("sched/core: Remove unnecessary #include headers")
> > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> > ---
> 
> The broken patch has now made it into mainline, according to the output of the
> build bots.

Oops, I totally mis-read the bug reports and assumed it was related to the sched.h 
splitup, which is in a separate branch. But this was a sched/core commit ...

I'll push the fix to Linus later today and sorry about that!

Thanks,

	Ingo

  reply	other threads:[~2017-02-24  8:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-17 14:43 [PATCH] sched/core: include asm/paravirt.h Arnd Bergmann
2017-02-21  9:29 ` Arnd Bergmann
2017-02-24  8:31   ` Ingo Molnar [this message]
2017-02-24  9:23     ` Arnd Bergmann
2017-02-24 11:13       ` Ingo Molnar

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=20170224083152.GA24307@gmail.com \
    --to=mingo@kernel.org \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --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 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.