From: Greg KH <gregkh@linuxfoundation.org>
To: Christian Lamparter <chunkeey@gmail.com>
Cc: Hauke Mehrtens <hauke@hauke-m.de>,
herbert@gondor.apana.org.au, davem@davemloft.net,
stable <stable@vger.kernel.org>,
linux-crypto@vger.kernel.org,
Amit Pundir <amit.pundir@linaro.org>
Subject: Re: crypto: crypto4xx - properly set IV after de- and encrypt breaks kernel 4.4
Date: Thu, 20 Jun 2019 16:07:55 +0200 [thread overview]
Message-ID: <20190620140755.GC7117@kroah.com> (raw)
In-Reply-To: <4226536.PGTo7a8ESG@debian64>
On Thu, Jun 20, 2019 at 02:07:27PM +0200, Christian Lamparter wrote:
> On Thursday, June 20, 2019 11:36:50 AM CEST Hauke Mehrtens wrote:
> > Hi,
> >
> > The patch "crypto: crypto4xx - properly set IV after de- and encrypt"
> > causes a compile error on kernel 4.4.
>
> 3.18 as well.
> >
> > When I revert this commit it compiles for me again:
> > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e9a60ab1609a7d975922adad1bf9c46ac6954584
> >
> > I do not have hardware to test if it is really working.
>
> I have a few APM821XX. But please note drivers without
>
> commit b66c685a482117d4e9ee987d252ca673689a5302
> Author: Christian Lamparter <chunkeey@gmail.com>
> Date: Fri Dec 22 21:18:36 2017 +0100
>
> crypto: crypto4xx - support Revision B parts
>
> don't work on those and I do have my doubts that 460EX
> series (and older) would either. I also don't believe that
> the inital driver as it was submitted would have worked.
> >From what I've seen in their SDK, they patched the testmgr
> at the time to either disable tests or provided their own...
> so, might as well revert these patches for 4.4 and 3.18.
Now reverted from both, thanks.
greg k-h
prev parent reply other threads:[~2019-06-20 14:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 9:36 crypto: crypto4xx - properly set IV after de- and encrypt breaks kernel 4.4 Hauke Mehrtens
2019-06-20 12:07 ` Christian Lamparter
2019-06-20 14:07 ` Greg KH [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=20190620140755.GC7117@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=amit.pundir@linaro.org \
--cc=chunkeey@gmail.com \
--cc=davem@davemloft.net \
--cc=hauke@hauke-m.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.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 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.