From: Dan Carpenter <dan.carpenter@oracle.com>
To: "Peng, Tao" <tao.peng@emc.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
Andreas Dilger <andreas.dilger@intel.com>
Subject: Re: [PATCH] staging/lustre: fix build errors
Date: Wed, 5 Jun 2013 14:07:21 +0300 [thread overview]
Message-ID: <20130605110721.GV28112@mwanda> (raw)
In-Reply-To: <1882637210201641A747464075FFC6490E580820@MX101CL02.corp.emc.com>
On Wed, Jun 05, 2013 at 10:36:20AM +0000, Peng, Tao wrote:
> > > Stephen, please see if this fixes your build failure. I have tested it locally but only on X86
> > architecture, with CONFIG_CPUMASK_OFFSTACK on and CONFIG_MODULES/CONFIG_MODULE_UNLOAD off.
> >
> > I have tried this with an x86_64 allmodconfig build and now I get just
> > this build problem:
> >
> > drivers/built-in.o: In function `crc32_pclmul_le_16':
> > (.text+0x28b9310): multiple definition of `crc32_pclmul_le_16'
> > arch/x86/built-in.o:(.text+0xe70d0): first defined here
> >
> We should really remove the crypto implementations inside Lustre
> code. I have a patch to do that and Andreas is helping review it.
> Once done, I will send it out.
Hopefully, it will be ready for tomorrow's linux-next? x86_64
allmodconfig is one of the most common ways to build a kernel.
regards,
dan carpenter
prev parent reply other threads:[~2013-06-05 11:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 8:45 [PATCH] staging/lustre: fix build errors Peng, Tao
2013-06-04 13:59 ` Greg Kroah-Hartman
2013-06-05 10:33 ` Peng, Tao
2013-06-05 0:42 ` Stephen Rothwell
2013-06-05 10:36 ` Peng, Tao
2013-06-05 11:07 ` Dan Carpenter [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=20130605110721.GV28112@mwanda \
--to=dan.carpenter@oracle.com \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tao.peng@emc.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