From: Julia Lawall <julia.lawall@lip6.fr>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild@01.org, cl@linux-foundation.org,
akpm@linux-foundation.org, linux-mm@kvack.org
Subject: Re: [next:master 9660/12021] mm/vmstat.c:1343:2-5: WARNING: Use BUG_ON
Date: Sat, 9 Aug 2014 13:31:39 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.02.1408091329530.2016@localhost6.localdomain6> (raw)
In-Reply-To: <53e5eeb3.j/1hw4T//eDPmwb+%fengguang.wu@intel.com>
I suspect that using BUG_ON here is not a good idea, because the tested
called function looks pretty important. But I have forwarded it on in
case someone thinks otherwise.
julia
On Sat, 9 Aug 2014, kbuild test robot wrote:
> TO: Christoph Lameter <cl@linux-foundation.org>
> CC: Andrew Morton <akpm@linux-foundation.org>
> CC: Linux Memory Management List <linux-mm@kvack.org>
>
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 6a062ecb62b37d6d36fa2e56052982565b0f5aac
> commit: f9054025fb65d0802098f18b153e4d720acd126e [9660/12021] on demand vmstat: Do not open code alloc_cpumask_var
> :::::: branch date: 27 hours ago
> :::::: commit date: 9 days ago
>
> >> mm/vmstat.c:1343:2-5: WARNING: Use BUG_ON
>
> Please consider folding the attached diff :-)
>
> ---
> 0-DAY kernel build testing backend Open Source Technology Center
> http://lists.01.org/mailman/listinfo/kbuild Intel Corporation
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next parent reply other threads:[~2014-08-09 11:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53e5eeb3.j/1hw4T//eDPmwb+%fengguang.wu@intel.com>
2014-08-09 11:31 ` Julia Lawall [this message]
2014-08-11 17:17 ` Christoph Lameter
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=alpine.DEB.2.02.1408091329530.2016@localhost6.localdomain6 \
--to=julia.lawall@lip6.fr \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild@01.org \
--cc=linux-mm@kvack.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