From: Jens Wiklander <jens.wiklander@linaro.org>
To: op-tee@lists.trustedfirmware.org
Subject: [GIT PULL] Fix TEE system compiler warning fo4r v6.0
Date: Thu, 25 Aug 2022 11:57:05 +0200 [thread overview]
Message-ID: <YwdHcdEUib7obbbW@jade> (raw)
[-- Attachment #1: Type: text/plain, Size: 882 bytes --]
Hello arm-soc maintainers,
Please pull this small patch which fixes a recently introduced compiler
warning the TEE subsystem.
Thanks,
Jens
The following changes since commit 1c23f9e627a7b412978b4e852793c5e3c3efc555:
Linux 6.0-rc2 (2022-08-21 17:32:54 -0700)
are available in the Git repository at:
https://git.linaro.org/people/jens.wiklander/linux-tee.git tags/tee-fix-for-v6.0
for you to fetch changes up to eccd7439709810127563e7e3e49b8b44c7b2791d:
tee: fix compiler warning in tee_shm_register() (2022-08-25 11:40:06 +0200)
----------------------------------------------------------------
Add a missing include in the TEE subsystem
----------------------------------------------------------------
Jens Wiklander (1):
tee: fix compiler warning in tee_shm_register()
drivers/tee/tee_shm.c | 1 +
1 file changed, 1 insertion(+)
reply other threads:[~2022-08-25 9:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=YwdHcdEUib7obbbW@jade \
--to=jens.wiklander@linaro.org \
--cc=op-tee@lists.trustedfirmware.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