From: Abdul Haleem <abdhalee@linux.vnet.ibm.com>
To: Arnd Bergmann <arnd@arndb.de>, dan.j.williams@intel.com
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
linux-xfs <linux-xfs@vger.kernel.org>,
sachinp <sachinp@linux.vnet.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: Mainline build brakes on powerpc with error : fs/xfs/xfs_iomap.c:1152: undefined reference to `.put_dax
Date: Thu, 18 May 2017 15:02:24 +0530 [thread overview]
Message-ID: <1495099944.22101.6.camel@abdul> (raw)
In-Reply-To: <CAK8P3a1e+Rgv2emmTgewm-YJ6j2H7xJzM_+Mz8J3OKWCpbsD6g@mail.gmail.com>
On Tue, 2017-05-16 at 13:17 +0200, Arnd Bergmann wrote:
> On Tue, May 16, 2017 at 1:02 PM, Abdul Haleem
> <abdhalee@linux.vnet.ibm.com> wrote:
> > Hi,
> >
> > Today's mainline 4.12-rc1 fails to build for the attached configuration
> > file on Power7 box with below errors.
> >
> > $ make
> > fs/built-in.o: In function `xfs_file_iomap_end':
> > fs/xfs/xfs_iomap.c:1152: undefined reference to `.put_dax'
> > fs/built-in.o: In function `xfs_file_iomap_begin':
> > fs/xfs/xfs_iomap.c:1071: undefined reference to `.dax_get_by_host'
> >
> > Also reproducible on latest linux-next, and the last successful build
> > was at next-20170510.
>
> This should be fixed by https://patchwork.kernel.org/patch/9725515/
>
> Arnd
>
Arnd,
With the given patch, kernel build and boot is fine on ppc.
Thanks Dan, for the patch!
Tested-by : Abdul Haleem <abdhalee@linux.vnet.ibm.com>
--
Regard's
Abdul Haleem
IBM Linux Technology Centre
prev parent reply other threads:[~2017-05-18 9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 11:02 Mainline build brakes on powerpc with error : fs/xfs/xfs_iomap.c:1152: undefined reference to `.put_dax Abdul Haleem
2017-05-16 11:17 ` Arnd Bergmann
2017-05-18 9:32 ` Abdul Haleem [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=1495099944.22101.6.camel@abdul \
--to=abdhalee@linux.vnet.ibm.com \
--cc=arnd@arndb.de \
--cc=dan.j.williams@intel.com \
--cc=darrick.wong@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sachinp@linux.vnet.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).