From: Joonsoo Kim <js1304@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kbuild test robot <fengguang.wu@intel.com>,
Linux Memory Management List <linux-mm@kvack.org>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: [PATCH] mm/page_ref: fix build failure for xtensa
Date: Tue, 1 Mar 2016 22:49:35 +0900 [thread overview]
Message-ID: <CAAmzW4PKHg+XfeRb4TN1qQbyJXCzm244iVNEwSwT+Qa33+pH7g@mail.gmail.com> (raw)
In-Reply-To: <1456839793-31276-1-git-send-email-iamjoonsoo.kim@lge.com>
2016-03-01 22:43 GMT+09:00 <js1304@gmail.com>:
> From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
>
> This patch includes struct page definition to fix build failure on xtensa.
>
> Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>
> ---
> mm/debug_page_ref.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/mm/debug_page_ref.c b/mm/debug_page_ref.c
> index 87e60e8..1aef3d5 100644
> --- a/mm/debug_page_ref.c
> +++ b/mm/debug_page_ref.c
> @@ -1,3 +1,4 @@
> +#include <linux/mm_types.h>
> #include <linux/tracepoint.h>
>
> #define CREATE_TRACE_POINTS
Seems like I used wrong message-id for in-reply-to.
Andrew, please fold this patch into
mm-page_ref-add-tracepoint-to-track-down-page-reference-manipulation.
Thanks.
--
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-03-01 13:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 13:06 [linux-next:master 8024/8887] include/trace/events/page_ref.h:47:18: warning: 'struct page' declared inside parameter list kbuild test robot
2016-03-01 13:43 ` [PATCH] mm/page_ref: fix build failure for xtensa js1304
2016-03-01 13:49 ` Joonsoo Kim [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=CAAmzW4PKHg+XfeRb4TN1qQbyJXCzm244iVNEwSwT+Qa33+pH7g@mail.gmail.com \
--to=js1304@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=iamjoonsoo.kim@lge.com \
--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