From: Greg KH <gregkh@linuxfoundation.org>
To: linux-kernel@vger.kernel.org
Cc: giovanni.cabiddu@intel.com, stable-commits@vger.kernel.org
Subject: Re: Patch "crypto: qat - do not export adf_iov_putmsg()" has been added to the 4.4-stable tree
Date: Mon, 13 Sep 2021 09:50:35 +0200 [thread overview]
Message-ID: <YT8Cy2W0UBLrbTyj@kroah.com> (raw)
In-Reply-To: <20210913032306.946F4600D4@mail.kernel.org>
On Sun, Sep 12, 2021 at 11:23:05PM -0400, Sasha Levin wrote:
> This is a note to let you know that I've just added the patch titled
>
> crypto: qat - do not export adf_iov_putmsg()
>
> to the 4.4-stable tree which can be found at:
> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>
> The filename of the patch is:
> crypto-qat-do-not-export-adf_iov_putmsg.patch
> and it can be found in the queue-4.4 subdirectory.
>
> If you, or anyone else, feels it should not be added to the stable tree,
> please let <stable@vger.kernel.org> know about it.
>
>
>
> commit 5f8033f94420950b5fc4b91dd2154c00fc88d44e
> Author: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
> Date: Thu Aug 12 21:21:28 2021 +0100
>
> crypto: qat - do not export adf_iov_putmsg()
>
> [ Upstream commit 645ae0af1840199086c33e4f841892ebee73f615 ]
>
> The function adf_iov_putmsg() is only used inside the intel_qat module
> therefore should not be exported.
> Remove EXPORT_SYMBOL for the function adf_iov_putmsg().
>
> Signed-off-by: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
> Reviewed-by: Fiona Trahe <fiona.trahe@intel.com>
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
> Signed-off-by: Sasha Levin <sashal@kernel.org>
>
> diff --git a/drivers/crypto/qat/qat_common/adf_pf2vf_msg.c b/drivers/crypto/qat/qat_common/adf_pf2vf_msg.c
> index 711706819b05..f071aba32a28 100644
> --- a/drivers/crypto/qat/qat_common/adf_pf2vf_msg.c
> +++ b/drivers/crypto/qat/qat_common/adf_pf2vf_msg.c
> @@ -254,7 +254,6 @@ int adf_iov_putmsg(struct adf_accel_dev *accel_dev, u32 msg, u8 vf_nr)
>
> return ret;
> }
> -EXPORT_SYMBOL_GPL(adf_iov_putmsg);
>
> void adf_vf2pf_req_hndl(struct adf_accel_vf_info *vf_info)
> {
This breaks the build on the 4.4.y stable queue, so I am dropping it
from there.
thanks,
greg k-h
parent reply other threads:[~2021-09-13 7:50 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20210913032306.946F4600D4@mail.kernel.org>]
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=YT8Cy2W0UBLrbTyj@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=giovanni.cabiddu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable-commits@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