linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Jens Wiklander <jens.wiklander@linaro.org>
Cc: arm-soc <arm@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] tee driver fix for v4.21
Date: Wed, 12 Dec 2018 13:36:17 -0800	[thread overview]
Message-ID: <20181212213617.mltwlxfcbap4prlj@localhost> (raw)
In-Reply-To: <20181212122800.GA29450@jax.ideon.se>

On Wed, Dec 12, 2018 at 01:28:00PM +0100, Jens Wiklander wrote:
> Hello arm-soc maintainers,
> 
> Please pull this tee driver fix for a possible double list_del() in the
> OP-TEE driver while uninitializing.
> 
> Thanks,
> Jens
> 
> The following changes since commit 40e020c129cfc991e8ab4736d2665351ffd1468d:
> 
>   Linux 4.20-rc6 (2018-12-09 15:31:00 -0800)
> 
> are available in the Git repository at:
> 
>   https://git.linaro.org/people/jens.wiklander/linux-tee.git tags/tee-subsys-fix-for-4.21
> 
> for you to fetch changes up to b2d102bd0146d9eb1fa630ca0cd19a15ef2f74c8:
> 
>   tee: optee: avoid possible double list_del() (2018-12-11 14:38:21 +0100)
> 
> ----------------------------------------------------------------
> Avoid possible double list_del in supplicant comms
> 
> A fix for the OP-TEE driver to avoid possible double list_del during
> tee-supplicant communication while the system is shutting down.

Do you want this for 4.20 or 4.21? Seems like .20 material to me but the tag
name is 4.21. 


-Olof


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2018-12-12 22:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-12 12:28 [GIT PULL] tee driver fix for v4.21 Jens Wiklander
2018-12-12 21:36 ` Olof Johansson [this message]
2018-12-13  7:29   ` Jens Wiklander
2018-12-31 21:06     ` Olof Johansson

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=20181212213617.mltwlxfcbap4prlj@localhost \
    --to=olof@lixom.net \
    --cc=arm@kernel.org \
    --cc=jens.wiklander@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@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).