From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ondrej Mosnacek <omosnace@redhat.com>
Cc: stable@vger.kernel.org, Herbert Xu <herbert@gondor.apana.org.au>,
linux-crypto@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 4.4.y] crypto: vmx - Fix sleep-in-atomic bugs
Date: Mon, 17 Sep 2018 13:47:15 +0200 [thread overview]
Message-ID: <20180917114715.GG13057@kroah.com> (raw)
In-Reply-To: <20180910074204.10812-1-omosnace@redhat.com>
On Mon, Sep 10, 2018 at 09:42:04AM +0200, Ondrej Mosnacek wrote:
> commit 0522236d4f9c5ab2e79889cb020d1acbe5da416e upstream.
>
> Conflicts:
> drivers/crypto/vmx/
> aes_cbc.c - adapted enable/disable calls to v4.4 state
> aes_xts.c - did not exist yet in v4.4
We don't need these lines here... I'll go hand edit it out...
next prev parent reply other threads:[~2018-09-17 11:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 7:42 [PATCH 4.4.y] crypto: vmx - Fix sleep-in-atomic bugs Ondrej Mosnacek
2018-09-10 7:47 ` Ondrej Mosnacek
2018-09-17 11:47 ` Greg Kroah-Hartman [this message]
2018-09-17 11:47 ` Greg Kroah-Hartman
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=20180917114715.GG13057@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=omosnace@redhat.com \
--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).