public inbox for soc@kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jens Wiklander <jens.wiklander@linaro.org>
Cc: arm@kernel.org, soc@kernel.org, linux-kernel@vger.kernel.org,
	 op-tee@lists.trustedfirmware.org
Subject: Re: [GIT PULL] TEE shared memory fix for 7.0
Date: Tue, 17 Mar 2026 09:51:46 +0100	[thread overview]
Message-ID: <20260317-illustrious-finicky-frog-90a86c@quoll> (raw)
In-Reply-To: <20260316074150.GA2474723@rayden>

On Mon, Mar 16, 2026 at 08:41:50AM +0100, Jens Wiklander wrote:
> Hello arm-soc maintainers,
> 
> Please pull this patch removing the refcounting of kernel pages within
> the TEE shared memory helper. 
> 
> Thanks,
> Jens
> 
> The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
> 
>   Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/jenswi/linux-tee.git tags/tee-fix-for-v7.0
> 
> for you to fetch changes up to 08d9a4580f71120be3c5b221af32dca00a48ceb0:
> 
>   tee: shm: Remove refcounting of kernel pages (2026-03-03 09:03:04 +0100)
> 
> ----------------------------------------------------------------
> TEE shared memory update for 7.0
> 
> Remove refcounting of kernel pages in register_shm_helper() to support
> slab allocations.

That's a supposed fix for a year old commit, not current RC, and the
commit msg does not explain what is the bug being fixed here. Looks like
it is doing improvement, not a fix. Can you provide here more
explanation of the actual bug being fixed to justify this going to
current RC fixes?

> 

Best regards,
Krzysztof


  reply	other threads:[~2026-03-17  8:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-16  7:41 [GIT PULL] TEE shared memory fix for 7.0 Jens Wiklander
2026-03-17  8:51 ` Krzysztof Kozlowski [this message]
2026-03-17 12:21   ` Jens Wiklander
2026-03-17 12:53     ` Marco Felsch
2026-03-18 12:39       ` Arnd Bergmann
2026-03-23 12:11         ` Sumit Garg
2026-03-18 13:10 ` patchwork-bot+linux-soc

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=20260317-illustrious-finicky-frog-90a86c@quoll \
    --to=krzk@kernel.org \
    --cc=arm@kernel.org \
    --cc=jens.wiklander@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=op-tee@lists.trustedfirmware.org \
    --cc=soc@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