From: Randy Dunlap <rdunlap@infradead.org>
To: akpm@linux-foundation.org, broonie@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-next@vger.kernel.org, mhocko@suse.cz,
mm-commits@vger.kernel.org, sfr@canb.auug.org.au,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
Boris Brezillon <bbrezillon@kernel.org>,
Arnaud Ebalard <arno@natisbad.org>,
Srujana Challa <schalla@marvell.com>
Subject: Re: mmotm 2021-01-25-21-18 uploaded (octeontx2)
Date: Wed, 27 Jan 2021 12:15:25 -0800 [thread overview]
Message-ID: <fe531e3e-15d7-720d-f2af-2606cf774975@infradead.org> (raw)
In-Reply-To: <20210126051917.rcgrHGfQS%akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 2569 bytes --]
On 1/25/21 9:19 PM, akpm@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2021-01-25-21-18 has been uploaded to
>
> https://www.ozlabs.org/~akpm/mmotm/
>
> mmotm-readme.txt says
>
> README for mm-of-the-moment:
>
> https://www.ozlabs.org/~akpm/mmotm/
>
> This is a snapshot of my -mm patch queue. Uploaded at random hopefully
> more than once a week.
>
> You will need quilt to apply these patches to the latest Linus release (5.x
> or 5.x-rcY). The series file is in broken-out.tar.gz and is duplicated in
> https://ozlabs.org/~akpm/mmotm/series
>
> The file broken-out.tar.gz contains two datestamp files: .DATE and
> .DATE-yyyy-mm-dd-hh-mm-ss. Both contain the string yyyy-mm-dd-hh-mm-ss,
> followed by the base kernel version against which this patch series is to
> be applied.
on x86_64:
WARNING: unmet direct dependencies detected for OCTEONTX2_MBOX
Depends on [n]: NETDEVICES [=n] && ETHERNET [=n] && NET_VENDOR_MARVELL [=n]
Selected by [m]:
- CRYPTO_DEV_OCTEONTX2_CPT [=m] && CRYPTO [=y] && CRYPTO_HW [=y] && (ARM64 || COMPILE_TEST [=y]) && PCI_MSI [=y] && 64BIT [=y] && CRYPTO_LIB_AES [=y]
and build errors:
ERROR: modpost: "otx2_mbox_reset" [drivers/crypto/marvell/octeontx2/octeontx2-cptvf.ko] undefined!
ERROR: modpost: "otx2_mbox_destroy" [drivers/crypto/marvell/octeontx2/octeontx2-cptvf.ko] undefined!
ERROR: modpost: "otx2_mbox_wait_for_rsp" [drivers/crypto/marvell/octeontx2/octeontx2-cptvf.ko] undefined!
ERROR: modpost: "otx2_mbox_msg_send" [drivers/crypto/marvell/octeontx2/octeontx2-cptvf.ko] undefined!
ERROR: modpost: "otx2_mbox_init" [drivers/crypto/marvell/octeontx2/octeontx2-cptvf.ko] undefined!
ERROR: modpost: "otx2_mbox_alloc_msg_rsp" [drivers/crypto/marvell/octeontx2/octeontx2-cptvf.ko] undefined!
ERROR: modpost: "otx2_reply_invalid_msg" [drivers/crypto/marvell/octeontx2/octeontx2-cpt.ko] undefined!
ERROR: modpost: "otx2_mbox_reset" [drivers/crypto/marvell/octeontx2/octeontx2-cpt.ko] undefined!
ERROR: modpost: "otx2_mbox_destroy" [drivers/crypto/marvell/octeontx2/octeontx2-cpt.ko] undefined!
ERROR: modpost: "otx2_mbox_wait_for_rsp" [drivers/crypto/marvell/octeontx2/octeontx2-cpt.ko] undefined!
ERROR: modpost: "otx2_mbox_msg_send" [drivers/crypto/marvell/octeontx2/octeontx2-cpt.ko] undefined!
ERROR: modpost: "otx2_mbox_init" [drivers/crypto/marvell/octeontx2/octeontx2-cpt.ko] undefined!
ERROR: modpost: "otx2_mbox_alloc_msg_rsp" [drivers/crypto/marvell/octeontx2/octeontx2-cpt.ko] undefined!
Full randconfig file is attached.
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
[-- Attachment #2: config-r7419.gz --]
[-- Type: application/gzip, Size: 40476 bytes --]
prev parent reply other threads:[~2021-01-27 20:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 5:19 mmotm 2021-01-25-21-18 uploaded akpm
2021-01-27 19:36 ` mmotm 2021-01-25-21-18 uploaded (drm/i915/Kconfig.debug) Randy Dunlap
2021-01-27 20:15 ` Randy Dunlap [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=fe531e3e-15d7-720d-f2af-2606cf774975@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=arno@natisbad.org \
--cc=bbrezillon@kernel.org \
--cc=broonie@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.org \
--cc=schalla@marvell.com \
--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).