From: Christoph Hellwig <hch@infradead.org>
To: Mark Brown <broonie@kernel.org>
Cc: Nagalakshmi Nandigama <nagalakshmi.nandigama@avagotech.com>,
Praveen Krishnamoorthy <praveen.krishnamoorthy@avagotech.com>,
Sreekanth Reddy <sreekanth.reddy@avagotech.com>,
Abhijit Mahajan <abhijit.mahajan@avagotech.com>,
"James E.J. Bottomley" <JBottomley@parallels.com>,
kernel-build-reports@lists.linaro.org,
linaro-kernel@lists.linaro.org,
MPT-FusionLinux.pdl@avagotech.com, linux-scsi@vger.kernel.org
Subject: Re: next-20140925 build: 1 failures 106 warnings (next-20140925)
Date: Thu, 25 Sep 2014 08:46:52 -0700 [thread overview]
Message-ID: <20140925154652.GA29864@infradead.org> (raw)
In-Reply-To: <20140925153120.GX27755@sirena.org.uk>
On Thu, Sep 25, 2014 at 04:31:20PM +0100, Mark Brown wrote:
> On Thu, Sep 25, 2014 at 01:13:56PM +0100, Build bot for Mark Brown wrote:
>
> > arm-allmodconfig
> > ERROR: "__aeabi_uldivmod" [drivers/scsi/mpt2sas/mpt2sas.ko] undefined!
>
> Today's ARM allmodconfig fails to build due to a call to a GCC intrinsic
> being emitted from the mpt2sas module - I've not made any effort to
> investigate this myself yet, unfortunately there's been a build error in
> this configuration for arch/arm for the past week or so which means that
> the error may not have been introduced today.
http://git.infradead.org/users/hch/scsi-queue.git/commitdiff/f78f694c34ae6fdc29f5e80abb2dbb894f961772
I just need James to pull the latests scsi-queue tree changes..
next prev parent reply other threads:[~2014-09-25 15:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1XX7vn-0003PS-Vu@cassiel.sirena.org.uk>
2014-09-25 15:31 ` next-20140925 build: 1 failures 106 warnings (next-20140925) Mark Brown
2014-09-25 15:46 ` Christoph Hellwig [this message]
2014-09-26 6:32 ` Sreekanth Reddy
2014-09-28 11:08 ` Mark Brown
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=20140925154652.GA29864@infradead.org \
--to=hch@infradead.org \
--cc=JBottomley@parallels.com \
--cc=MPT-FusionLinux.pdl@avagotech.com \
--cc=abhijit.mahajan@avagotech.com \
--cc=broonie@kernel.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nagalakshmi.nandigama@avagotech.com \
--cc=praveen.krishnamoorthy@avagotech.com \
--cc=sreekanth.reddy@avagotech.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