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 Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: linux-next: Tree for Sep 25 (crypto/caam/)
Date: Tue, 25 Sep 2018 08:38:33 -0700 [thread overview]
Message-ID: <f1436714-629e-a6ee-9fbc-525914652064@infradead.org> (raw)
In-Reply-To: <20180925153937.07660ca8@canb.auug.org.au>
On 9/24/18 10:39 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20180924:
>
on i386:
# CONFIG_NET is not set
drivers/crypto/caam/caamalg_qi2.o: In function `dpaa2_caam_fqdan_cb':
caamalg_qi2.c:(.text+0x502): undefined reference to `napi_schedule_prep'
caamalg_qi2.c:(.text+0x50d): undefined reference to `__napi_schedule_irqoff'
drivers/crypto/caam/caamalg_qi2.o: In function `dpaa2_dpseci_poll':
caamalg_qi2.c:(.text+0x9ee): undefined reference to `napi_complete_done'
drivers/crypto/caam/caamalg_qi2.o: In function `dpaa2_caam_probe':
caamalg_qi2.c:(.text+0x68f1): undefined reference to `netif_napi_add'
drivers/crypto/caam/caamalg_qi2.o: In function `dpaa2_caam_remove':
caamalg_qi2.c:(.text.unlikely+0x1ec): undefined reference to `napi_disable'
caamalg_qi2.c:(.text.unlikely+0x1f3): undefined reference to `netif_napi_del'
--
~Randy
next prev parent reply other threads:[~2018-09-25 15:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 5:39 linux-next: Tree for Sep 25 Stephen Rothwell
2018-09-25 15:38 ` Randy Dunlap [this message]
2018-09-25 20:33 ` linux-next: Tree for Sep 25 (sound/soc/codecs/wm8731) 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=f1436714-629e-a6ee-9fbc-525914652064@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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;
as well as URLs for NNTP newsgroup(s).