From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Andrew Morton <akpm@linux-foundation•org>, Greg KH <greg@kroah•com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Viresh Kumar <viresh.kumar@linaro•org>,
Mel Gorman <mgorman@techsingularity•net>
Subject: linux-next: manual merge of the akpm-current tree with the driver-core tree
Date: Wed, 7 Oct 2015 15:36:56 +1100 [thread overview]
Message-ID: <20151007153656.3948e6ce@canb.auug.org.au> (raw)
Hi Andrew,
Today's linux-next merge of the akpm-current tree got conflicts in:
mm/failslab.c
mm/page_alloc.c
between commit:
621a5f7ad9cd ("debugfs: Pass bool pointer to debugfs_create_bool()")
from the driver-core tree and commit:
67c145d9ff18 ("mm, page_alloc: rename __GFP_WAIT to __GFP_RECLAIM")
from the akpm-current tree.
I fixed it up (see below) and can carry the fix as necessary (no action
is required).
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
diff --cc mm/failslab.c
index 98fb490311eb,35c876c82b9d..000000000000
--- a/mm/failslab.c
+++ b/mm/failslab.c
@@@ -3,12 -3,12 +3,12 @@@
static struct {
struct fault_attr attr;
- bool ignore_gfp_wait;
- u32 ignore_gfp_reclaim;
- int cache_filter;
++ bool ignore_gfp_reclaim;
+ bool cache_filter;
} failslab = {
.attr = FAULT_ATTR_INITIALIZER,
- .ignore_gfp_wait = true,
- .ignore_gfp_reclaim = 1,
- .cache_filter = 0,
++ .ignore_gfp_reclaim = true,
+ .cache_filter = false,
};
bool should_failslab(size_t size, gfp_t gfpflags, unsigned long cache_flags)
diff --cc mm/page_alloc.c
index 805bbad2e24e,c73913648357..000000000000
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@@ -2159,13 -2277,13 +2277,13 @@@ failed
static struct {
struct fault_attr attr;
- u32 ignore_gfp_highmem;
- u32 ignore_gfp_reclaim;
+ bool ignore_gfp_highmem;
- bool ignore_gfp_wait;
++ bool ignore_gfp_reclaim;
u32 min_order;
} fail_page_alloc = {
.attr = FAULT_ATTR_INITIALIZER,
- .ignore_gfp_wait = true,
- .ignore_gfp_reclaim = 1,
- .ignore_gfp_highmem = 1,
++ .ignore_gfp_reclaim = true,
+ .ignore_gfp_highmem = true,
.min_order = 1,
};
next reply other threads:[~2015-10-07 4:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 4:36 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-11-10 8:55 linux-next: manual merge of the akpm-current tree with the driver-core tree Stephen Rothwell
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=20151007153656.3948e6ce@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=greg@kroah$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mgorman@techsingularity$(echo .)net \
--cc=viresh.kumar@linaro$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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