From: Vijay Khemka <vijaykhemka@fb.com>
To: "Justin . Lee1 @ Dell . com" <Justin.Lee1@Dell.com>,
"joel @ jms . id . au" <joel@jms.id.au>,
"linux-aspeed @ lists . ozlabs . org"
<linux-aspeed@lists.ozlabs.org>,
"openbmc @ lists . ozlabs . org" <openbmc@lists.ozlabs.org>,
Sai Dasari <sdasari@fb.com>,
"netdev @ vger . kernel . org" <netdev@vger.kernel.org>,
"christian @ cmd . nu" <christian@cmd.nu>,
Samuel Mendoza-Jonas <sam@mendozajonas.com>
Subject: Re: [Potential Spoof] Re: [PATCH v2] net/ncsi: Add NCSI OEM command support
Date: Mon, 1 Oct 2018 22:45:06 +0000 [thread overview]
Message-ID: <4B3FCCBC-0A9B-47D0-876D-323D12DFD09B@fb.com> (raw)
On 9/28/18, 6:21 PM, "Linux-aspeed on behalf of Vijay Khemka" <linux-aspeed-bounces+vijaykhemka=fb.com@lists.ozlabs.org on behalf of vijaykhemka@fb.com> wrote:
> On 9/28/18, 6:07 PM, "Vijay Khemka" <vijaykhemka@fb.com> wrote:
> This patch adds OEM commands and response handling. It also defines OEM
> command and response structure as per NCSI specification along with its
> handlers.
>
> ncsi_cmd_handler_oem: This is a generic command request handler for OEM
> commands
> ncsi_rsp_handler_oem: This is a generic response handler for OEM commands
This is a generic patch for OEM command handling, There will be another patch
following this to handle specific OEM commands for each vendor. Currently I have
defined 2 vendor/manufacturer id below in internal.h, more can be added here for
other vendors. I have not defined ncsi_rsp_oem_handler in this patch as they are
NULL, but there will be a defined handlers for each vendor in next patch.
Sam, Joel, Justin, please review this patch. I have 2 more patch coming for Broadcom and Mellanox.
reply other threads:[~2018-10-02 5:25 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=4B3FCCBC-0A9B-47D0-876D-323D12DFD09B@fb.com \
--to=vijaykhemka@fb.com \
--cc=Justin.Lee1@Dell.com \
--cc=christian@cmd.nu \
--cc=joel@jms.id.au \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=sam@mendozajonas.com \
--cc=sdasari@fb.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