From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: linux-next: Tree for Nov 27 (scsi/aha1542)
Date: Tue, 27 Nov 2018 20:14:58 -0800 [thread overview]
Message-ID: <ef9090cf-e86a-7fd0-dfa9-6810eaaf7e65@infradead.org> (raw)
In-Reply-To: <20181127152539.55426063@canb.auug.org.au>
On 11/26/18 8:25 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20181126:
>
on i386:
ERROR: "__udivdi3" [drivers/scsi/aha1542.ko] undefined!
somewhere in aha1542_interrupt() according to objdump.
--
~Randy
next prev parent reply other threads:[~2018-11-28 4:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 4:25 linux-next: Tree for Nov 27 Stephen Rothwell
2018-11-28 3:47 ` linux-next: Tree for Nov 27 (net/ipv4/af_inet.c) Randy Dunlap
2018-11-28 4:30 ` David Ahern
2018-11-28 4:14 ` Randy Dunlap [this message]
2018-11-28 4:38 ` linux-next: Tree for Nov 27 (scsi/aha1542) Stephen Rothwell
2018-11-28 5:41 ` James Bottomley
2018-11-28 6:54 ` Christoph Hellwig
2018-11-28 7:11 ` Randy Dunlap
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=ef9090cf-e86a-7fd0-dfa9-6810eaaf7e65@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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