From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dan Williams <dan.j.williams@intel.com>
Cc: akpm@linux-foundation.org, linux-nvdimm@lists.01.org, linux-mm@kvack.org
Subject: Re: [-mm PATCH] list, perf: fix list_force_poison() build regression
Date: Mon, 4 Jan 2016 18:47:24 +1100 [thread overview]
Message-ID: <20160104184724.444b879b@canb.auug.org.au> (raw)
In-Reply-To: <20160101032348.26352.75121.stgit@dwillia2-desk3.amr.corp.intel.com>
Hi Dan,
On Thu, 31 Dec 2015 19:24:21 -0800 Dan Williams <dan.j.williams@intel.com> wrote:
>
> In file included from
> /home/sfr/next/next/tools/include/linux/list.h:5:0,
> from arch/../util/map.h:6,
> from arch/../util/event.h:8,
> from arch/../util/debug.h:7,
> from arch/common.c:4:
> include/linux/list.h: In function 'list_force_poison':
> include/linux/list.h:123:56: error: unused parameter 'entry' [-Werror=unused-parameter]
> static inline void list_force_poison(struct list_head *entry)
>
> perf does not like the empty definition of list_force_poison. For
> simplicity just switch to list_del in the non-debug case.
>
> Fixes "mm, dax, pmem: introduce {get|put}_dev_pagemap() for dax-gup" in
> -next.
>
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
> ---
> include/linux/list.h | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/include/linux/list.h b/include/linux/list.h
> index d870ba3315f8..ebf5f358e8c3 100644
> --- a/include/linux/list.h
> +++ b/include/linux/list.h
> @@ -120,9 +120,8 @@ extern void list_del(struct list_head *entry);
> */
> extern void list_force_poison(struct list_head *entry);
> #else
> -static inline void list_force_poison(struct list_head *entry)
> -{
> -}
> +/* fallback to the less strict LIST_POISON* definitions */
> +#define list_force_poison list_del
> #endif
>
> /**
I applied this to linux-next today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
--
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>
prev parent reply other threads:[~2016-01-04 7:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 3:24 Dan Williams
2016-01-04 7:47 ` Stephen Rothwell [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=20160104184724.444b879b@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.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