All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rik van Riel <riel@surriel.com>
To: kbuild test robot <lkp@intel.com>
Cc: linux-kernel@vger.kernel.org, x86@vger.kernel.org,
	luto@kernel.org, mingo@kernel.org, tglx@linutronix.de,
	dave.hansen@linux.intel.com, efault@gmx.de,
	songliubraving@fb.com, kernel-team@fb.com
Subject: Re: [PATCH 7/7] x86,idle: do not leave mm in idle state
Date: Wed, 20 Jun 2018 20:25:22 -0400	[thread overview]
Message-ID: <1529540722.7898.180.camel@surriel.com> (raw)
In-Reply-To: <201806210615.8NIETZnu%fengguang.wu@intel.com>

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

On Thu, 2018-06-21 at 06:20 +0800, kbuild test robot wrote:

> All error/warnings (new ones prefixed by >>):
> 
>    arch/x86/xen/mmu_pv.c: In function 'drop_mm_ref_this_cpu':
> > > arch/x86/xen/mmu_pv.c:987:3: error: implicit declaration of
> > > function 'leave_mm' [-Werror=implicit-function-declaration]
> 
>       leave_mm(smp_processor_id());
>       ^~~~~~~~
>    cc1: some warnings being treated as errors

This was the result of a last minute cleanup,
erroneously thinking I had removed the last
user of leave_mm.  Of course there's Xen :)

Fixed in my tree for v2.

-- 
All Rights Reversed.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2018-06-21  0:25 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-20 19:56 [PATCH 0/7] x86,tlb,mm: make lazy TLB mode even lazier Rik van Riel
2018-06-20 19:56 ` [PATCH 1/7] mm: allocate mm_cpumask dynamically based on nr_cpu_ids Rik van Riel
2018-06-20 21:32   ` kbuild test robot
2018-06-21 20:18     ` Rik van Riel
2018-06-21  0:24   ` kbuild test robot
2018-06-22 15:10   ` Dave Hansen
2018-06-22 17:45     ` Rik van Riel
2018-06-20 19:56 ` [PATCH 2/7] x86,tlb: leave lazy TLB mode at page table free time Rik van Riel
2018-06-21  0:23   ` Rik van Riel
2018-06-22 14:58   ` Andy Lutomirski
2018-06-22 15:17     ` Rik van Riel
2018-06-20 19:56 ` [PATCH 3/7] x86,tlb: change tlbstate.is_lazy to tlbstate.state Rik van Riel
2018-06-22 17:01   ` Dave Hansen
2018-06-22 17:08     ` Rik van Riel
2018-06-20 19:56 ` [PATCH 4/7] x86,tlb: make lazy TLB mode lazier Rik van Riel
2018-06-22 15:04   ` Andy Lutomirski
2018-06-22 15:15     ` Rik van Riel
2018-06-22 15:34       ` Andy Lutomirski
2018-06-22 17:05   ` Dave Hansen
2018-06-22 17:16     ` Rik van Riel
2018-06-20 19:56 ` [PATCH 5/7] x86,tlb: only send page table free TLB flush to lazy TLB CPUs Rik van Riel
2018-06-22 17:23   ` Dave Hansen
2018-06-20 19:56 ` [PATCH 6/7] x86,mm: always use lazy TLB mode Rik van Riel
2018-06-20 19:56 ` [PATCH 7/7] x86,idle: do not leave mm in idle state Rik van Riel
2018-06-20 22:20   ` kbuild test robot
2018-06-21  0:25     ` Rik van Riel [this message]
2018-06-22 15:36   ` Andy Lutomirski
2018-06-22 15:53     ` Rik van Riel
2018-06-22 16:01       ` Andy Lutomirski
2018-06-22 20:18         ` Rik van Riel
2018-06-22 22:05           ` Andy Lutomirski
2018-06-23  0:55             ` Rik van Riel

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=1529540722.7898.180.camel@surriel.com \
    --to=riel@surriel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=efault@gmx.de \
    --cc=kernel-team@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=luto@kernel.org \
    --cc=mingo@kernel.org \
    --cc=songliubraving@fb.com \
    --cc=tglx@linutronix.de \
    --cc=x86@vger.kernel.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.