From: Dan Williams <dan.j.williams@intel.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Milan Broz <mbroz@redhat.com>,
"Michael S. Tsirkin" <m.s.tsirkin@gmail.com>,
Alasdair G Kergon <agk@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
dm-crypt@saout.de
Subject: Re: 2.6.25-rc[1,2]: failed to setup dm-crypt key mapping
Date: Fri, 07 Mar 2008 20:42:44 -0700 [thread overview]
Message-ID: <1204947764.27096.4.camel@dwillia2-linux.ch.intel.com> (raw)
In-Reply-To: <20080308012438.GA24236@gondor.apana.org.au>
On Fri, 2008-03-07 at 18:24 -0700, Herbert Xu wrote:
> On Fri, Mar 07, 2008 at 11:14:07AM -0700, Dan Williams wrote:
> >
> > I believe this is in mainline as 76fc60a2 "[CRYPTO] skcipher: Move
> > chainiv/seqiv into crypto_blkcipher module". With a iop13xx_defconfig
> > I get:
> >
> > `chainiv_module_exit' referenced in section `.init.text' of
> > crypto/built-in.o: defined in discarded section `.exit.text' of
> > crypto/built-in.o
> > `chainiv_module_exit' referenced in section `__ksymtab_gpl' of
> > crypto/built-in.o: defined in discarded section `.exit.text' of
> > crypto/built-in.o
> > `eseqiv_module_exit' referenced in section `__ksymtab_gpl' of
> > crypto/built-in.o: defined in discarded section `.exit.text' of
> > crypto/built-in.o
> > make: *** [.tmp_vmlinux1] Error 1
>
> Does this help?
>
Yup, and doing the same for eseqiv_module_exit completes the fix.
LD arch/arm/boot/compressed/vmlinux
OBJCOPY arch/arm/boot/zImage
Kernel: arch/arm/boot/zImage is ready
Thanks,
Dan
next prev parent reply other threads:[~2008-03-08 3:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8f53421d0802192343v2267cb66ub579d4503e3b7eb1@mail.gmail.com>
2008-02-20 11:23 ` 2.6.25-rc[1,2]: failed to setup dm-crypt key mapping Milan Broz
2008-02-20 17:24 ` Herbert Xu
2008-02-20 17:47 ` Milan Broz
2008-02-20 17:58 ` Herbert Xu
2008-02-20 20:29 ` Michael S. Tsirkin
2008-02-22 12:34 ` Herbert Xu
2008-02-25 19:03 ` Jan Niehusmann
2008-03-07 18:14 ` Dan Williams
2008-03-08 1:24 ` Herbert Xu
2008-03-08 3:42 ` Dan Williams [this message]
2008-03-08 12:28 ` Herbert Xu
2008-03-07 18:18 ` Tony Luck
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=1204947764.27096.4.camel@dwillia2-linux.ch.intel.com \
--to=dan.j.williams@intel.com \
--cc=agk@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dm-crypt@saout.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=m.s.tsirkin@gmail.com \
--cc=mbroz@redhat.com \
--cc=rjw@sisk.pl \
/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