public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Sumit Garg <sumit.garg@linaro.org>
Cc: stable@vger.kernel.org, jens.wiklander@linaro.org, sudeep.holla@arm.com
Subject: Re: [PATCH backport for 5.4] tee: optee: Fix missing devices unregister during optee_remove
Date: Wed, 20 Oct 2021 14:34:31 +0200	[thread overview]
Message-ID: <YXAM1xA86BWW6jKu@kroah.com> (raw)
In-Reply-To: <20211019094532.470845-1-sumit.garg@linaro.org>

On Tue, Oct 19, 2021 at 03:15:32PM +0530, Sumit Garg wrote:
> upstream commit 7f565d0ead26
> 
> When OP-TEE driver is built as a module, OP-TEE client devices
> registered on TEE bus during probe should be unregistered during
> optee_remove. So implement optee_unregister_devices() accordingly.
> 
> Fixes: c3fa24af9244 ("tee: optee: add TEE bus device enumeration support")
> Reported-by: Sudeep Holla <sudeep.holla@arm.com>
> Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
> Signed-off-by: Jens Wiklander <jens.wiklander@linaro.org>
> [SG: backport to 5.4, dev name s/optee-ta/optee-clnt/]
> Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
> ---
>  drivers/tee/optee/core.c          |  3 +++
>  drivers/tee/optee/device.c        | 22 ++++++++++++++++++++++
>  drivers/tee/optee/optee_private.h |  1 +
>  3 files changed, 26 insertions(+)

Doesn't this also need to go into 5.10 and 5.14?  We can not have people
upgrading and having regressions.

Can you provide backports for those trees too?  I can not take just this
one, sorry.

thanks,

greg k-h

  reply	other threads:[~2021-10-20 12:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-19  9:45 [PATCH backport for 5.4] tee: optee: Fix missing devices unregister during optee_remove Sumit Garg
2021-10-20 12:34 ` Greg KH [this message]
2021-10-20 12:37   ` Greg KH
2021-10-20 12:38     ` Sumit Garg

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=YXAM1xA86BWW6jKu@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jens.wiklander@linaro.org \
    --cc=stable@vger.kernel.org \
    --cc=sudeep.holla@arm.com \
    --cc=sumit.garg@linaro.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