From: Rusty Russell <rusty@rustcorp.com.au>
To: Tim Chen <tim.c.chen@linux.intel.com>,
Herbert Xu <herbert@gondor.apana.org.au>
Cc: Zhao Hongjiang <zhaohongjiang@huawei.com>,
davem@davemloft.net, Andrew Morton <akpm@linux-foundation.org>,
"gregkh\@linuxfoundation.org" <gregkh@linuxfoundation.org>,
linux-crypto@vger.kernel.org
Subject: Re: [BUG] 3.11 boot failure caused by commit crypto
Date: Tue, 30 Jul 2013 15:26:50 +0930 [thread overview]
Message-ID: <87li4o615p.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1375140048.22432.400.camel@schen9-DESK>
Tim Chen <tim.c.chen@linux.intel.com> writes:
> On Tue, 2013-07-30 at 09:08 +1000, Herbert Xu wrote:
>> On Mon, Jul 29, 2013 at 01:39:06PM -0700, Tim Chen wrote:
>> >
>> > Herbert, what are your thoughts on a proper fix to initrd issue for
>> > crct10dif modules not getting included? Or can we
>> > let the config option for the pclmul version to be either compiled
>> > out or compiled in for now for people who do want to use this?
>>
>> With the MODULES_SOFTDEP patch that Rusty recently merged, all we
>> need to do is to use that in lib/crct10dif module. Once that patch
>> hits mainline I'll take care of the rest.
>
> Great. Thanks.
>
> Tim
Does this imply that you want me to push that to Linus now, and/or CC
stable? Was planning for *next* merge window...
Cheers,
Rusty.
next prev parent reply other threads:[~2013-07-30 6:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 2:28 [BUG] 3.11 boot failure caused by commit crypto Zhao Hongjiang
2013-07-24 7:06 ` Herbert Xu
2013-07-29 20:39 ` Tim Chen
2013-07-29 23:08 ` Herbert Xu
2013-07-29 23:20 ` Tim Chen
2013-07-30 5:56 ` Rusty Russell [this message]
2013-07-30 11:28 ` Herbert Xu
2013-07-31 0:09 ` Rusty Russell
2013-08-01 1:47 ` Herbert Xu
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=87li4o615p.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=tim.c.chen@linux.intel.com \
--cc=zhaohongjiang@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.