All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Wiklander <jens.wiklander@linaro.org>
To: arm@kernel.org, soc@kernel.org
Subject: Re: [GIT PULL] TEE SHM vmalloc for v5.19
Date: Tue, 3 May 2022 21:28:50 +0200	[thread overview]
Message-ID: <CAHUa44FCGjEp3_Y05Jj7NSWHeN3Y8QSOXV+fu5BV4tKKMLQTGw@mail.gmail.com> (raw)
In-Reply-To: <20220503192418.GA3285658@jade>

Hi,

Please ignore the previous mail, I'll resend the pull request with the
mailing lists included.

Thanks,
Jens

On Tue, May 3, 2022 at 9:24 PM Jens Wiklander <jens.wiklander@linaro.org> wrote:
>
> Hello arm-soc maintainers,
>
> Please pull this patch which enables tee_shm_register_kernel_buf() to
> accept vmalloc()ed buffers.
>
> Thanks,
> Jens
>
> The following changes since commit 3123109284176b1532874591f7c81f3837bbdc17:
>
>   Linux 5.18-rc1 (2022-04-03 14:08:21 -0700)
>
> are available in the Git repository at:
>
>   https://git.linaro.org/people/jens.wiklander/linux-tee.git tags/tee-shm-vmalloc-for-v5.19
>
> for you to fetch changes up to 3e47235eaee09488c7e467b9aaccb7c93c862c6b:
>
>   tee: make tee_shm_register_kernel_buf vmalloc supported (2022-04-05 08:04:16 +0200)
>
> ----------------------------------------------------------------
> TEE accept vmalloc()ed buffers for tee_shm_register_kernel_buf()
>
> ----------------------------------------------------------------
> Phil Chang (1):
>       tee: make tee_shm_register_kernel_buf vmalloc supported
>
>  drivers/tee/optee/call.c |  2 +-
>  drivers/tee/tee_shm.c    | 35 +++++++++++++++++++++++++----------
>  2 files changed, 26 insertions(+), 11 deletions(-)

  reply	other threads:[~2022-05-03 19:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-03 19:24 [GIT PULL] TEE SHM vmalloc for v5.19 Jens Wiklander
2022-05-03 19:28 ` Jens Wiklander [this message]
2022-05-03 19:29 Jens Wiklander
2022-05-05 19:31 ` 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=CAHUa44FCGjEp3_Y05Jj7NSWHeN3Y8QSOXV+fu5BV4tKKMLQTGw@mail.gmail.com \
    --to=jens.wiklander@linaro.org \
    --cc=arm@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.