From: David Miller <davem@davemloft.net>
To: sheetal.tigadoli@broadcom.com
Cc: zajec5@gmail.com, gregkh@linuxfoundation.org,
michal.simek@xilinx.com, rajan.vaja@xilinx.com,
scott.branden@broadcom.com, ray.jui@broadcom.com,
vikram.prakash@broadcom.com, jens.wiklander@linaro.org,
michael.chan@broadcom.com, vikas.gupta@broadcom.com,
vasundhara-v.volam@broadcom.com, linux-kernel@vger.kernel.org,
tee-dev@lists.linaro.org, bcm-kernel-feedback-list@broadcom.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next V5 0/3] Add OP-TEE based bnxt f/w manager
Date: Thu, 31 Oct 2019 11:01:00 -0700 (PDT) [thread overview]
Message-ID: <20191031.110100.985830325607594650.davem@davemloft.net> (raw)
In-Reply-To: <1572516532-5977-1-git-send-email-sheetal.tigadoli@broadcom.com>
From: Sheetal Tigadoli <sheetal.tigadoli@broadcom.com>
Date: Thu, 31 Oct 2019 15:38:49 +0530
> This patch series adds support for TEE based BNXT firmware
> management module and the driver changes to invoke OP-TEE
> APIs to fastboot firmware and to collect crash dump.
>
> Changes from v4:
> - update Kconfig to reflect dependency on TEE driver
Series applied, thanks.
prev parent reply other threads:[~2019-10-31 18:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 10:08 [PATCH net-next V5 0/3] Add OP-TEE based bnxt f/w manager Sheetal Tigadoli
2019-10-31 10:08 ` [PATCH net-next V5 1/3] firmware: broadcom: add OP-TEE based BNXT " Sheetal Tigadoli
2019-10-31 10:08 ` [PATCH net-next V5 2/3] bnxt_en: Add support to invoke OP-TEE API to reset firmware Sheetal Tigadoli
2019-10-31 17:59 ` Michael Chan
2019-10-31 10:08 ` [PATCH net-next V5 3/3] bnxt_en: Add support to collect crash dump via ethtool Sheetal Tigadoli
2019-10-31 18:01 ` Michael Chan
2019-10-31 18:01 ` David Miller [this message]
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=20191031.110100.985830325607594650.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=gregkh@linuxfoundation.org \
--cc=jens.wiklander@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.chan@broadcom.com \
--cc=michal.simek@xilinx.com \
--cc=netdev@vger.kernel.org \
--cc=rajan.vaja@xilinx.com \
--cc=ray.jui@broadcom.com \
--cc=scott.branden@broadcom.com \
--cc=sheetal.tigadoli@broadcom.com \
--cc=tee-dev@lists.linaro.org \
--cc=vasundhara-v.volam@broadcom.com \
--cc=vikas.gupta@broadcom.com \
--cc=vikram.prakash@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).