From: Arthur Marsh <arthur.marsh@internode.on.net>
To: Tim Chen <tim.c.chen@linux.intel.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
linux-crypto <linux-crypto@vger.kernel.org>
Subject: Re: sd_mod - uknown symbol crc_t10_diff [was Re: unable to finish booting when "crypto: crct10dif - Wrap crc_t10dif function all to use crypto transform framework" applied]
Date: Thu, 12 Sep 2013 00:27:52 +0930 [thread overview]
Message-ID: <523084F0.5000106@internode.on.net> (raw)
In-Reply-To: <523083F5.8050104@internode.on.net>
Oops, that should be crc_t10_dif with one "f".
Arthur.
prev parent reply other threads:[~2013-09-11 14:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51D8420C.7010602@internode.on.net>
2013-07-09 16:00 ` unable to finish booting when "crypto: crct10dif - Wrap crc_t10dif function all to use crypto transform framework" applied Tim Chen
2013-07-09 18:13 ` Arthur Marsh
2013-07-09 21:34 ` Tim Chen
2013-07-10 6:16 ` Herbert Xu
2013-07-11 11:27 ` Arthur Marsh
[not found] ` <523083F5.8050104@internode.on.net>
2013-09-11 14:57 ` Arthur Marsh [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=523084F0.5000106@internode.on.net \
--to=arthur.marsh@internode.on.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=tim.c.chen@linux.intel.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