From: Greg KH <gregkh@linuxfoundation.org>
To: Saeed Mirzamohammadi <saeed.mirzamohammadi@oracle.com>
Cc: stable@vger.kernel.org, Xiu Jianfeng <xiujianfeng@huawei.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Dan Williams <dan.j.williams@intel.com>,
"David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH stable v5.15.y 1/1] crypto: add __init/__exit annotations to init/exit funcs
Date: Wed, 15 Feb 2023 07:55:01 +0100 [thread overview]
Message-ID: <Y+yBxXNjBLuonPKP@kroah.com> (raw)
In-Reply-To: <20230214195300.2432989-2-saeed.mirzamohammadi@oracle.com>
On Tue, Feb 14, 2023 at 11:53:00AM -0800, Saeed Mirzamohammadi wrote:
> From: Xiu Jianfeng <xiujianfeng@huawei.com>
>
> Add missing __init/__exit annotations to init/exit funcs.
>
> Signed-off-by: Xiu Jianfeng <xiujianfeng@huawei.com>
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
> (cherry picked from commit 33837be33367172d66d1f2bd6964cc41448e6e7c)
> Cc: stable@vger.kernel.org # 5.15+
> Signed-off-by: Saeed Mirzamohammadi <saeed.mirzamohammadi@oracle.com>
> ---
> crypto/async_tx/raid6test.c | 4 ++--
> crypto/curve25519-generic.c | 4 ++--
> crypto/dh.c | 4 ++--
> crypto/ecdh.c | 4 ++--
> crypto/ecdsa.c | 4 ++--
> crypto/rsa.c | 4 ++--
> crypto/sm2.c | 4 ++--
> 7 files changed, 14 insertions(+), 14 deletions(-)
What bug/problem does this resolve? Why is this needed in stable
kernels?
next prev parent reply other threads:[~2023-02-15 6:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 19:52 [PATCH stable v5.15.y 0/1] crypto: add __init/__exit annotations to init/exit funcs Saeed Mirzamohammadi
2023-02-14 19:53 ` [PATCH stable v5.15.y 1/1] " Saeed Mirzamohammadi
2023-02-15 6:55 ` Greg KH [this message]
2023-02-15 23:10 ` Saeed Mirzamohammadi
2023-02-16 6:58 ` Greg KH
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=Y+yBxXNjBLuonPKP@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dan.j.williams@intel.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=saeed.mirzamohammadi@oracle.com \
--cc=stable@vger.kernel.org \
--cc=xiujianfeng@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox