From: Tyler Hicks <tyhicks@linux.microsoft.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: "Jens Wiklander" <jens.wiklander@linaro.org>,
"Vikas Gupta" <vikas.gupta@broadcom.com>,
"Rafał Miłecki" <zajec5@gmail.com>,
"Allen Pais" <apais@linux.microsoft.com>,
"Sumit Garg" <sumit.garg@linaro.org>,
"Peter Huewe" <peterhuewe@gmx.de>,
"Jarkko Sakkinen" <jarkko@kernel.org>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
"Thirupathaiah Annapureddy" <thiruan@microsoft.com>,
"Pavel Tatashin" <pasha.tatashin@soleen.com>,
"OP-TEE TrustedFirmware" <op-tee@lists.trustedfirmware.org>,
linux-integrity <linux-integrity@vger.kernel.org>,
"BCM Kernel Feedback" <bcm-kernel-feedback-list@broadcom.com>,
linux-mips@vger.kernel.org,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 8/8] firmware: tee_bnxt: Release TEE shm, session, and context during kexec
Date: Tue, 20 Jul 2021 13:15:17 -0500 [thread overview]
Message-ID: <20210720181517.GF3232@sequoia> (raw)
In-Reply-To: <bc3f4bdd-b833-d58c-f7d7-6670bcbd8ef8@gmail.com>
On 2021-07-20 10:57:18, Florian Fainelli wrote:
>
>
> On 7/19/2021 7:32 PM, Florian Fainelli wrote:
> >
> >
> > On 7/19/2021 3:49 AM, Jens Wiklander wrote:
> > > Hi,
> > >
> > > On Fri, Jul 16, 2021 at 4:48 AM Vikas Gupta
> > > <vikas.gupta@broadcom.com> wrote:
> > > >
> > > > Hi Allen/Tyler,
> > > > The patch looks good to me.
> > >
> > > Thanks.
> > >
> > > Rafal, is it OK if I include this patch together with the rest of the
> > > patches in this patch set in a pull request to arm-soc?
> >
> > I can take those patches through the Broadcom ARM SoC pull request,
> > Rafal would that work for you? We seem to have a bit of a maintainer
> > coverage blind spot for that directory.
>
> Applied to drivers/fixes: https://github.com/Broadcom/stblinux/commit/4ecd797b7e16eb7f1b86fbfd7e4a7887b192535b
Thanks, Florian, but note that you won't be able to build that branch
since the commit uses a new function (tee_shm_alloc_kernel_buf()) that's
added earlier in the full series. It seems like it is going to be easier
for this to all go through Jens.
Tyler
> --
> Florian
>
next prev parent reply other threads:[~2021-07-20 18:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210716022332.GC3232@sequoia>
2021-07-16 2:56 ` [PATCH v5 8/8] firmware: tee_bnxt: Release TEE shm, session, and context during kexec Vikas Gupta
[not found] ` <CAHLZf_t5U1bh1H8sULbJz7xrZ-r3Dcmxuw9MMmG2fehS3C72uQ@mail.gmail.com>
2021-07-19 10:49 ` Jens Wiklander
2021-07-20 2:32 ` Florian Fainelli
2021-07-20 17:57 ` Florian Fainelli
2021-07-20 18:15 ` Tyler Hicks [this message]
2021-07-20 18:59 ` Florian Fainelli
2021-06-14 22:33 [PATCH v5 0/8] tee: Improve support for kexec and kdump Tyler Hicks
2021-06-14 22:33 ` [PATCH v5 8/8] firmware: tee_bnxt: Release TEE shm, session, and context during kexec Tyler Hicks
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=20210720181517.GF3232@sequoia \
--to=tyhicks@linux.microsoft.com \
--cc=apais@linux.microsoft.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=jarkko@kernel.org \
--cc=jens.wiklander@linaro.org \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=op-tee@lists.trustedfirmware.org \
--cc=pasha.tatashin@soleen.com \
--cc=peterhuewe@gmx.de \
--cc=sumit.garg@linaro.org \
--cc=thiruan@microsoft.com \
--cc=vikas.gupta@broadcom.com \
--cc=zajec5@gmail.com \
/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).