From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Paul Gortmaker <paul.gortmaker@windriver•com>
Cc: linux-kernel@vger•kernel.org, linux-next@vger•kernel.org,
"Jérôme Glisse" <jglisse@redhat•com>,
"Evgeny Baskakov" <ebaskakov@nvidia•com>,
"John Hubbard" <jhubbard@nvidia•com>,
"Mark Hairgrove" <mhairgrove@nvidia•com>,
"Sherry Cheung" <SCheung@nvidia•com>,
"Subhash Gutti" <sgutti@nvidia•com>,
"Andrew Morton" <akpm@linux-foundation•org>
Subject: Re: [PATCH 4/4] mm/hmm: exclude 64 bit arch that explicitly fail to work.
Date: Thu, 13 Apr 2017 13:27:01 +1000 [thread overview]
Message-ID: <20170413132701.633a22a9@canb.auug.org.au> (raw)
In-Reply-To: <20170413003014.4052-5-paul.gortmaker@windriver.com>
Hi Paul,
On Wed, 12 Apr 2017 20:30:14 -0400 Paul Gortmaker <paul.gortmaker@windriver•com> wrote:
>
> Since ia64 and ppc64 don't set CONFIG_64BIT, they were already
> excluded by the original dependency.
My powerpc ppc64_defconfig builds have CONFIG_64BIT set ...
$ grep CONFIG_64BIT ~/next/powerpc_ppc64_defconfig/.config
CONFIG_64BIT=y
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2017-04-13 3:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 0:30 [PATCH akpm/next 0/4] Fix various issues in new hmm driver Paul Gortmaker
2017-04-13 0:30 ` [PATCH 1/4] mm/hmm: make it explicitly non-modular Paul Gortmaker
2017-04-13 0:30 ` [PATCH 2/4] mm/hmm: fix warnings and SECTION_SIZE definition overlap Paul Gortmaker
2017-04-14 0:27 ` kbuild test robot
2017-04-13 0:30 ` [PATCH 3/4] mm/hmm: fix Kconfig to have valid usage of "select" Paul Gortmaker
2017-04-13 0:30 ` [PATCH 4/4] mm/hmm: exclude 64 bit arch that explicitly fail to work Paul Gortmaker
2017-04-13 3:27 ` Stephen Rothwell [this message]
2017-04-13 3:56 ` Paul Gortmaker
2017-04-13 5:12 ` Michael Ellerman
2017-04-13 12:03 ` Paul Gortmaker
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=20170413132701.633a22a9@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=SCheung@nvidia$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=ebaskakov@nvidia$(echo .)com \
--cc=jglisse@redhat$(echo .)com \
--cc=jhubbard@nvidia$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mhairgrove@nvidia$(echo .)com \
--cc=paul.gortmaker@windriver$(echo .)com \
--cc=sgutti@nvidia$(echo .)com \
/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