From: "J. Paul Reed" <preed@sigkill.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org
Subject: Re: Fixing userspace crypto in 3.14.x?
Date: Sun, 13 Mar 2016 01:05:54 -0800 [thread overview]
Message-ID: <20160313090554.GA20770@sigkill.com> (raw)
In-Reply-To: <20160313053916.GA18628@kroah.com>
On 12 Mar 2016 at 21:39:16, Greg KH arranged the bits on my disk to say:
> Ok, you are right, and have been very patient, thanks for bringing this
> up again. I've reverted this patch, hopefully that resolves the issue.
I will test 3.14.65 when it ships, and let you know if, it turns out, that
wasn't the commit that broke it.
thanks again,
preed
--
J. Paul Reed PGP: 0xDF8708F8 -- http://www.soberbuildengineer.com
=========================================================================
I've never seen an airplane yet that can read the type ratings on your
pilot's license. -- Chuck Boedecker
next prev parent reply other threads:[~2016-03-13 9:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-13 0:26 Fixing userspace crypto in 3.14.x? J. Paul Reed
2016-03-13 0:45 ` Greg KH
2016-03-13 1:10 ` J. Paul Reed
2016-03-13 3:02 ` Greg KH
2016-03-13 3:55 ` J. Paul Reed
2016-03-13 5:39 ` Greg KH
2016-03-13 9:05 ` J. Paul Reed [this message]
2016-03-24 2:31 ` J. Paul Reed
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=20160313090554.GA20770@sigkill.com \
--to=preed@sigkill.com \
--cc=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
/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).